Are you from Germany or do you have your Browser set to German?
The first time I visited the site I got redirected to https://blog.lastpass.com/de/2015/06/lastpass-security-notic... (notice the "de" in the domain), which has the German words.
The second time I visited the site I didn't get redirected to the German site and didn't see the English words.
Maybe some weird automatic translation bug.
Here are the AWS alternatives I could find when I was searching for them 2 months ago. They are both hosted in Germany and operated by German companies.
I haven't played with them yet, so I can't say if they are any good.
EC2 alternative: http://jiffybox.de Not as feature rich as EC2, but they do have an api to launch, stop, and resize instances.
What I don't get is why the F1 officials haven't learned more out of that tragic accident. Sure the cars are much safer than they were when Senna died, but why do they have to at more and more races in city centers? Sure, I can understand that they want to keep Monaco for historic reason, but there isn't a good reason to have races in the city centers of Valencia, Singapore, and soon New Jersey.
Driving that close to walls at the speeds they do, will sooner or later lead to another tragic accident.
I'm trying to choose a framework right now and TodoMVC is really helping in doing so.
I have one question though:
Would you mind if I ported your apps over to CoffeeScript? I prefer CoffeeScript over JavaScript, but haven't done that much work in CoffeeScript. I think porting the apps would be a great learning experience and would help others too. Of course I would put it up on Github.
Red Bull's marketing is impeccable. They started out with all the actionsport athletes and moved upstream to more mainstream, and I guess, more expensive sports (two Formula 1 teams, more soccer teams than I can count), while still doing these crazy things. From Parcours in Santorini, to Air Races all over the world. Seems like every crazy sporting event is sponsored by Red Bull.
I think these have allowed them to be still seen as "hip" and not just selling sugar water like Coca Cola.
He talked about it a little bit in the video mentioned in the post. He thinks about "open sourcing"(his words) or patenting the idea and giving the patent to someone who has the financial resources to build it. I guess because of that he hasn't gone into much detail but here is a list of things about the Hyperloop I remembered:
-from downtown LA to downtown SF in 30 Minutes
-cheaper than airplane ticket
-solar panels on the top to make it self sustaining
-energy would be saved without batteries to run at night
-under no influence of the weather
-safe
(-Sarah Lacy made a reference to a TV show/movie with a tube as transportation system, and Elon said it was kind of like that [can't remember the title])
I have just browsed through the blog of the project manager at http://tagebuch.miniatur-wunderland.de (it's in German).
Until now the only thing I could find regarding the programming are the following numbers[1]:
The control software has 145.000 lines of code[I guess for the whole model, not just the airport]
Just the airport control software has 70,000 lines of code.
He has added 200,000 numbers just for the configuration.
An EBS node in a EBS cluster is connected to two networks. One is used for the traffic to and from the EBS volumes(Primary network), the other is used to replicate the EBS volume on a EBS node to a different EBS node(Secondary network).
Amazon wanted to upgrade the capacity of the primary network. Their standard step doing this is to shift the traffic to a redundant router. This step was executed incorrectly. This resulted in the traffic not being routed to the primary network but instead to the secondary network which has less capacity.
All this traffic satured the secondary network and resulted in the EBS volumes becoming "stuck".
When the traffic got routed the right way all the EBS volumes were trying to remirror. Part of the remirroring process is that the EBS volumes search the cluster for free space to remirror to.
The EBS cluster couldn't handle this load and new capacity was needed for the EBS cluster.
Amazon offers a 10 day credit equal to 100% of their usage of EBS Volumes, EC2 Instances and RDS database instances.
This credit will be automatically applied to the next bill.
You could use the tag system.
The questions would be at ama.stackexchange.com/questions/tagged/Joel+Spolsky. The person who posted the question just had to accept the answer of the person who he had asked.
I wonder who the "competitor" is that bought delicious.
The first one that comes to mind is Digg, since Kevin Rose said he would like to buy it and Yahoo contacted Digg if they would by it[1]. The second one that comes to my mind is StumbleUpon, especially two days after raising a Series B of $17 Million[2].
I agree that it would much more even if your load is consistent and heavy, but if it gets too heavy you run in a lot of problems with EC2.
If you max out one instance, you would need to add another instance and as a result of that you would need a third instance as a load balancer.
So if we take the numbers from the example I gave above and assume your instance maxes out add 100k requests and you get 110k request your cost would go from $72 to $216 ($72 for the load balancer and 2* $72 for the web/application server). That is 3x more but only an increase in traffic by 10% Of course the same math applies to your database server.
GAE pricing scales linear no matter how big you are and you never have to worry about maxing it out. Of course you have some trade off's because of that, but that is what the article was about.
I guess it's a question how you define heavy traffic. I've read somewhere that Zynga runs 10,000 EC2, at that scale adding another instance wouldn't have a huge impact, but I think if you have less than 15-20 instances (which is still huge) you're cheaper off with GAE.
(Even though it sounds like I'm affiliated to GAE I'm not, I'm going to use EC2 because of the trade off's mention in the original article)
You only pay for CPU if you really use it and not for "standby".
So if you have 100k requests in one month and each request takes 0.1 seconds you only have 10.000 seconds(or 166.66 hours or 2.7 hours) so you only pay $0.27 for that month.
EC2 would bill you for 720 hours(30 days *24 hours). At a rate of $0.10 you would pay $72 instead of the $0.27.
(For this example I'm not taking the free quota into account)