piggity

A large part of the issue with pricing on Google App Engine (which is the one that still stings for many people) - was that they were building on a relatively proprietary platform.

The advantage of Docker based compute engines is that your lock-in is a lot lower - providers have to compete on price and features without locking customers in.

Where I work, we're always balancing using new AWS features against how hard it would be to migrate out to another provider or take our solutions on-premises.

There are small things - e.g. you can't do weekly / fortnightly billing.

Once I discovered that I stopped investigating BT for our primary subscription engine. We just hold the card tokens and use BT to charge the card.

It's not ideal, but it does give us more flexibility.

Shouldn't it be the service's responsibility to determine what you are rating as a median score and then recalibrate your scores to their drivers?

i.e. If I always rate 3, but sometimes rate 1; then that might be similar to someone always rating 5 but sometimes rating 1-3.

Except if your target customer isn't a chemist.

I recently went on holidays and was merrily tethered away on 4G to Telstra. Hit the cap limit on my plan - 3GB - called Telstra to get a datapack add-on - "I'm sorry, but you are on the highest plan, we can't add on any more data".

Basically I would have had to sign onto a completely new contract to get more data for the 5 days to end of month. Ridiculous.

Double opt-in is optional at Mailchimp.

Customers can add emails directly and check a box saying "yes this customer gave me permission".

Aweber uses double opt-in and there is no way around it. But that is a double edged sword when you've got a business to run.

I guess the main issue is that the timeline of events has gone like this:

Snowden/Guardian: NSA is doing X Govt/NSA: We are not doing X Snowden/Guardian: Here are some slide/proof Govt/NSA: Ok we are doing X, but it's for your own good.

Rinse and repeat each fortnight.

So each denial means less and less, and tips believability towards Snowden even where the proof is inconclusive in some cases.

I wonder if the developers get a real handle on the platform and squeezing the most out of it by the time it gets to EOL.

Could be that the active user base of mixpanel has dropped slightly while people are offline to upgrade. Would depend on exactly how their metrics are being gathered.

None-the-less I find it amazing that ~20% of their sample base is already upgraded.

I was using LaTeX => PDF generation, but because I don't do it all the time I found it cumbersome and confusing at times.

Prawn seems to have come a long way since I used it last - and has addressed all the limitations that pushed me towards LaTeX in the first place.

Definitely worth looking at Prawn again in my opinion.

SQL Server Standard is $2K per core - with > 4 cores per socket, things flip around a bit.

I'm not a SQL licensing guru; so perhaps I'm confused as well...

Interesting idea, it looks like you scan the Gemfile.lock (or equivalent) at "deploy" time.

My preference would be to upload that Gemfile.lock to a location, and then it could be scanned as and when new vulnerabilities were detected.