mniejiki

Except you were talking about startups originally, don't change the scenario when someone points out flaws. Startups don't have the power or money to enforce a monopoly.

More than that, you're ignoring the reality of a merger which would be a lot of corporate politics ending up with most of the originals founders getting kicked out. The handful who played the game the best will end up getting the whole pie.

Wow, did a rasberry pi sleep with your mother or something?

And who says that embedded hardware must run off a battery? You're sure one to talk about stupidity.

You can get COBRA so it's not that you won't have insurance but rather that you will pay for it yourself. And have 18 months to find a longer term option if you can. It's what I did although I am single without kids so my rate was significantly lower.

Of course that is exactly what your employer paid on your behalf before. So you're basically complaining that other people will now no longer be subsidizing your medical costs. A private system won't help you much. A public one will but merely because people who pay taxes will now be subsidizing you.

In addition to the money back that was mentioned, in the US credit cards provide consumer protection. If you pay $500 for something and it's never deliver you can get a charge back from the cc company. Good chance you'll get your money back with minimal hassle. If you use a debit card or equivalent there is a lot less protection and it's a lot harder to get your money back. These are asfaik legally mandated things so it's not a question of CC being nicer as much as them being legally forced to be nicer than debit cards.

If you're able to actually control your spending a CC is very much superior to anything else in the US.

I've never had any issues with ec2 instances mysteriously restarting and I've dealt with a lot of them (personal and business). In fact I don't think I've ever seen amazon restart instances or mess with them in any way without warning.

Sounds like you're got a configuration problem somewhere (os on you instances, software you're running, etc.) on your end and are blaming amazon for it when they had nothing to do with it.

Now, potentially the instance is on bad hardware (start/stop if you've got no ephemeral storage which will put you on new hardware) but that can happen even if you're running your own hardware. However, you've done so little investigation that blaming amazon is downright bad IT (is this how you deal with other bugs, blame the first thing you can think off and rant about it?).

>this describes but one example of an edge case that could be elegantly handled by informing the node that it must go down and come up again a while later, after which its swapped-out guts with the potential to cause issue might be more easily resolved.

Huh? They manually and explicitly stopped their own instance and then started it up again. Given that you don't pay for stopped instances it's sort of obvious that they don't really exist but are recreated upon being started again. What does amazon have to do with this?

To me, it's not an edge case so much as missing the meaning of "stopping" and "starting" an instance on ec2.

Point being, that's only if you stop the instance. Since VMs can be migrated live on some vm ecosystems, "changing underneath" is very misleading in this case since it strongly implies a live migration.

If you stop your ec2 instance then you are effectively creating a whole new vm instance when you start it. That's not exactly a secret or something unexpected. It's why ephemeral storage is wiped clean and why you can only retain data via ebs (which is not local storage).

If you restart an instance (rather than start/stop) then you stay on the same hardware.

Also, what you seem to not get is that this isn't a zero sum game.

Google translate doesn't cater to the same people as traditional translators. Google translate basically sucks, it can't compete with a half competent translator. It can however compete with a random friend who knows a hundred words in a language, it can compete with spending 6 hours digging through dictionaries, it can compete with asking people on forums for translations and so on. And it has done more than that.

It has increased the market for translations, things that no one would have ever wanted to translate before can now be translated. Things that would have forever been locked away in one language can now be read, barely, by everyone. This is something that human translators without the net could never achieve. The costs and latency were just too high to use them.

That is what technology does in a nutshell, it takes something that used to belong to the elite and brings it to the masses.

>So why are they not simply buying the rights of the translations they are using?

Why do you think they haven't done that? Or rather they paid the entity that owns the rights who at some point in the past paid those translators. Generally speaking the translators gave up their rights in exchange for money long ago.

Specifically google uses, for example, UN documents which translators were paid to translate and which are publicly usable.

If I write some code for a company, get paid for that code and then the company sells that code why should I get paid again?

Or do you think google is the first automated translation service? This has been done successfully for 30+ years commercially and academically. Nothing different just because it's on the web and not on some guys PC.

>How many jobs were lost when we found out washing hands before surgery is a good idea?

Actually, I'm sure there were all sort of quack solutions to infections and whole industries making them which went out of business as a result of doctor's realizing washing hands did the trick.

Edit: Not to mention the loss of jobs for morticians (in the short term), makers of amputation implements (and other tools to deal with all those infections), nurses specializing in dealing with infections, traditional healers (as doctors were now an even better choice) and so on. Lowering infections would have impacted every single person and industry that was built around the previous high-infection status quo.

Until you lose users because implementing that plugin infrastructure slows down your program or prevents certain features from being written easily (either directly due to trade offs in having the infrastructure implemented or indirectly in not wanting to break compatibility with older plugins).

Also as Apple showed, a nice polished product sells and that final polish matters. It's a lot more difficult to do that when you need to deal with an unknown quality like plugins.

>The way I understand that: If you don't pay the people who do the work, and people who make a collage out of their work get paid, you'll end up with much fewer new translations being undertaken.

That's silly. Those previous translations don't magically go away, they still exist. And new translations exist as well except they're now being done by a machine or by a much smaller number of human translator (see below for why this doesn't do any harm).

Having a million people translate "I like cats" into French doesn't give you a million translations. It gives you one translation repeated a million times. That's 999,999 redundant translations. Nothing novel or amazing about those 999,999 translations.

What is the difference between a machine doing those million translations and humans doing identical translations?

Of course, there are novel translations and those would require human input but that's a minority. If the machine can do 99% of translations but requires humans for the additional 1% why is it better to have humans translate 100% rather than just that 1%. You end up with the exact same quality and quantity of translations in both cases.

>You take money from the people who do the work and give it to those who made a collage from it, and the total amount is much less.

The machine is lowering the cost of translations and thus may increase the amount spent on translations. The people who made translations got paid already.

>And I disagree. If I can buy a bun for 20 cents, or someone could rob the baker and give it to me for 5 cents, I'd rather have the bun for 20 cents, because that means more delicious bun tomorrow, and the day after that.

Except that's not the situation. The situation is that someone took the bun, figured out how to make one from it and then started selling their own buns for 5 cents each. You can have that exact same bun forever from the new seller.

Of course, one day you may want a new bun and, you'd argue, that there are no bakers left. But that's silly and utterly simplistic. Once there's not enough bakers with buns to copy that doesn't mean that new recipes will cease to exist but rather than an an alternative will be found. So the new seller will have simply hired some bakers to create a new recipes. Some bakers will continue to have jobs except that instead of wasting all their time on the repetitive tasks of baking they'll instead spend it on innovative tasks of making new recipes (or improving existing ones). You end up with the same diversity and quality of buns now and in the future but at a lower price.

Of course, many bakers will lose their jobs but that's the consequence of all technology and progress. Light bulbs meant that many candle makers lost their jobs. Frankly I prefer light bulbs to candles.

In their place many new jobs will have opened up via the money which people used to spend on buns or candles. That's in addition to all the jobs needed to keep the new bun or light bulb making infrastructure running.

edit: Actually, the "perfect" machine translation would be superior to the average human translation for that 99% since it'd be based on the best human translation for every single piece of text. Needless to say machines are far from there yet but that also means human translators have little to fear job wise for now.

Amusingly, the next hot thing in web translation probably isn't machines. It's humans. Using mechanical turk. So thanks to the web there may soon be more human translators employed than ever before. That's on top of the machines which, to be frank, rather suck at any translation that really matters.