Smrchy

Now if only MS would sit down and create a useable NodeJS client for MS-SQL.

The lack of a good clients outside the Windows world is what makes me move away from this otherwise great product.

I agree 100%. Without time tracking Basecamp Next is useless to us too. Migrating Classic to Next and losing our tracked time is no option. We mainly use To-Do lists and time tracking. Time tracking as it only is available in the 49$/month price plan was the single reason we upgraded.

I'm a bit disappointed now as i was looking forward to Basecamp Next.

I am wondering where and how you terminate the HTTPS connections for websockets. Can you share some details on that?

Why is there a 1MB reply limit on BatchGets and obviously no limit on Gets? Did anybody find limits on a single item?

Wish i could read the blog post. I am quite a happy Jekyll user.

And while Jekyll still has some downsides it is superior when it comes to handling a load spike from a HN post.

So what's the solution? Lie when asked for the birthday?

Even if most of my apps would increase by 10x they would still be cheaper than running a single AWS instance for them. Not even taking into account the easy of management and automatic redundancy that GAE offers.

I love using GAE and got 8 apps running currently. At first the new pricing model shocked me. But please take a 2nd look. Sure it's more expensive than the old model. But you can set the maximum number of idle instances in your Application Settings page. Just set it down so no more that X instances get spun up:

> The Idle Instances slider allows you to control the number of idle instances available to your application at any given time. Idle Instances are pre-loaded with your application code, so when a new Instance is needed, it can serve traffic immediately. You will not be charged for instances over the specified maximum. A smaller number of idle Instances means your application costs less to run, but may encounter more startup latency during load spikes.

There is another setting for latency:

> The Pending Latency slider controls how long requests spend in the pending queue before being served by an Instance. If the minimum pending latency is high App Engine will allow requests to wait rather than start new Instances to process them. This can reduce the number of instance hours your application uses, but can result in more user-visible latency.

So if you are fine with a little higher latency for your app then you can reduce your bill by a great deal. If you want all that GAE can offer with max. instances available and lowest latency you gotta pay - as you would when you run n instances at another cloud provider.

We are AdSense premium partners and have seen our revenues nearly cut in half while our page views remained constant. I can safely say this is due to the fact that a lot of our visitors use ad block plugins. I can't blame them - some ad formats are annoying enough to justify ad blockers. Unfortunately Google does not offer a way for us to receive ads on the server level and integrate them into the page content, bypassing the ad blockers - like Google does it on his own properties.

This is not the link to the article. It shows a "Skip Ad" and then goes to the homepage.

I wish the Khan Academy and everybody who is working for this awesome idea and good cause all the best. It is these people that make me feel so proud of mankind.

Getting the chance to work on such a project makes money and career fade far into the background. All the Good this project is doing for the world makes it worth it. And all without the need to charge for the service or display ads.

Congrats John on this excellent choice for a chance to make a change.

100% agree on that. I had a DSL contract with them in Germany and moved to another town where i had internet via cable included. They insisted that i have to keep paying for another 18 months with no way to cancel the contract early.

I paid and will avoid 1and1 for the rest of my life.

This is great news indeed.

Can anyone from Amazon say something about plans and/or an ETA for a South American region for all those people in Brazil, Argentina, Chile etc.?

Wonder what this means for companies like http://jumpbox.com/ We used Jumpbox in the in the past to setup some quick examples for testing.

One would be that you can access Redis servers with apps that don't have good / mature Redis clients - like Adobe Coldfusion. Even though you still have to cope with the buggy JSON support in Coldfusion then. But better than no Redis at all i guess.

The main pro for storing data in the cloud. Let's say on Amazon S3 is that you also get a web server that is able to serve those same files (public or secure). Even if you need them served to millions of users. You don't have to care about scaling this thing. Good luck doing this with a NAS.

I don't know about others, but i guess most of my contacts, customers and yet to become customers appreciate it if i start an email to them with a friendly "Hello" and end with a formal "Regards".

When i call someone on the phone i will also continue to say "Hello" and "Bye" instead of just starting to talk and hang up when i'm done.

Considering that most password are shorter than 14 characters, everyone implementing hashed passwords without a random salt could just store them as plain text. The rainbow table for the most common passwords (names, cities, pet names etc.) would fit in less than 1GB and would probably yield a very high success rate. There's no need to use complex passwords to prove that hashes without proper salting are bound to fail.