pyritschard's comments

pyritschard | 11 years ago

nice, duplicity also works out quite well for this use case.

pyritschard | 11 years ago

I mentioned https://exoscale.ch in another reply, we're doing more than VPS and have been out and serving customers for a while now !

pyritschard | 11 years ago

If you're looking for a provider already out of beta, I'd encourage you to check-out https://exoscale.ch (disclaimer: I'm the CTO there).

We have object-storage, a heroku compatible PaaS and our cloudstack based IaaS. We also contribute a ton of dOSS things whether in existing projects (riemann, collectd, graphite) or home grown projects such as http://pithos.io

If you're keen to try out, you can register with the WELOVEHN coupon which will get you started with a few more credits than the usual CHF20, we also do special prices for startups, available here: https://www.exoscale.ch/pricing-target/

pyritschard | 11 years ago

paper.li is almost fully clojure. exoscale.ch runs critical infrastructure on clojure.

walmart labs has been mentioned, the climate corporation (recently bought by monsanto) is another well-known one.

Here in Switzerland I can count 4 others smaller companies and at least a very big telco.

If you start counting every company relying on riemann for production monitoring that adds quite a few :-)

pyritschard | 11 years ago

Hi,

pyr from exoscale here. we operate a service that is similar to DO and linode, and are really proud of our uptime, our efficient support and the simplicity of our console - we want to be the best cloud platforms for people build SaaS applications.

I'm obviously biased, but I think we're definitely worth trying out :-)

pyritschard | 11 years ago

This applies to "communications provider" which right now means telcos. Infrastructure providers such as exoscale of course do no such thing.

pyritschard | 11 years ago

``Angular modules can be declared in various ways, either stored in a variable or using the getter syntax. Use the getter syntax at all times.''

It would have been nice to know the reasoning behind this. It does make minification marginally easier (but later on in the document, the DI notation is not used for $routeProvider which prevents minification from hapening anyhow), apart from that I fail to see any advantage to that approach.

pyritschard | 12 years ago

In the article, it has nothing to do with what is commonly referred to as DI in the Java world.

It's just a rather a simple mechanism to provide an extension mechanism for a daemon.

page 2