To me it seems both are at fault; the corporations who lobbied for weaker regulation, and the people in the government who saw that regulation through.
It's tough to point fingers when there's so many people who screwed up. But they all deserve the blame.
Free or not, at some point you MUST have a standard, or you will not have interoperability. What Google is doing here is no different than what Microsoft has done for years.
Now I'm not saying Java ME is good. In fact, it's awful. But an awful standard is still better than none.
The real problem is that Google created their own version of Java ME. Instead of sticking with the existing standard, they came up with their own. And that's bad for everyone.
I'd also be concerned about the toxicity of these batteries. Are they 100% recyclable? Will they be safely disposed of, even if Tesla goes out of business? Will they leak?
I think it's a matter of degree. No developer would complain as long as the code is internally consistent, well-planned, and reasonably bug free.
The thing is, in the real world this almost never happens due to time constraints and too-many-cooks-syndrome.
Worse yet, there are developers with fancy degrees and good jobs who have absolutely no idea what they're doing. Most of us have met one or two such people, and a few of us have had to work with them.
So I don't think it's fair to say that developers always bitch about other people's code; just when it's well deserved. Perhaps if you feel that people always bitch about your code, there's a reason for this and you should take the criticism seriously.
This is a MASSIVE mistake that sci-fi (aka syfy) writers make all the time when talking about computer power. Just because you have a lot, and you will have a lot more later, doesn't mean you have enough to compute everything.
A malicious hacker would have a field day with such a system. Causing computers to fail is one thing, but causing massive traffic jams takes hacking to a whole new level.
Slashdot Mirror
I would ask for $4 cash instead of his stupid card.
Sounds good to me. You wouldn't be able to get a "ransom note" but I guess that's an acceptable limitation.
Unless you do the indexing client-side, and upload an index that's somehow encrypted...
I'm not saying I know how to do this, but it seems possible.
Would a "floppy phone" be more resistant to drops? Clumsy minds want to know.
What's the reason for this?
To me it seems both are at fault; the corporations who lobbied for weaker regulation, and the people in the government who saw that regulation through.
It's tough to point fingers when there's so many people who screwed up. But they all deserve the blame.
It would be extremely trivial to convert something written for Microsoft's broken standards too.
The point is that as a developer, that just means more wasted time on something that's out of my control.
Free or not, at some point you MUST have a standard, or you will not have interoperability. What Google is doing here is no different than what Microsoft has done for years.
Now I'm not saying Java ME is good. In fact, it's awful. But an awful standard is still better than none.
The real problem is that Google created their own version of Java ME. Instead of sticking with the existing standard, they came up with their own. And that's bad for everyone.
So you want to listen to music while you send text messages and talk on the phone? That sounds like a car accident waiting to happen.
1. Tesla
2. Space-X
Need I say more?
If so, then consider the fact that he attempted to fire everyone at PayPal, switch to Windows servers, and rename it to X.com.
If GM has to fire their CEO, Elon Munk should be fired from Tesla. The guy is not management material.
I'd also be concerned about the toxicity of these batteries. Are they 100% recyclable? Will they be safely disposed of, even if Tesla goes out of business? Will they leak?
Sounds like they're making this difficult on purpose.
Wait, so they're PLANNING to come up with a plan?
If that's all it is, this is a non-story. Government agencies come up with plans all the time. Plans != action.
And how, exactly, are we supposed to comment on this plan? For that matter, what IS this plan?
Can someone translate it into English for the rest of us?
I think it's a matter of degree. No developer would complain as long as the code is internally consistent, well-planned, and reasonably bug free.
The thing is, in the real world this almost never happens due to time constraints and too-many-cooks-syndrome.
Worse yet, there are developers with fancy degrees and good jobs who have absolutely no idea what they're doing. Most of us have met one or two such people, and a few of us have had to work with them.
So I don't think it's fair to say that developers always bitch about other people's code; just when it's well deserved. Perhaps if you feel that people always bitch about your code, there's a reason for this and you should take the criticism seriously.
Just as a reminder, now would be a good time to support the EFF with a donation so they can continue this case.
I think have a great idea as to how to solve this.
But unfortunately I'm still waiting for the CFL bulb above my head to light up.
But Groovy is NEW! And new is better! Just ask any developer!
Are you serious? There are plenty of samples of digitized vaginal tissue on the internet already. Many require credit cards, however.
Exponentially increasing != infinite
This is a MASSIVE mistake that sci-fi (aka syfy) writers make all the time when talking about computer power. Just because you have a lot, and you will have a lot more later, doesn't mean you have enough to compute everything.
A malicious hacker would have a field day with such a system. Causing computers to fail is one thing, but causing massive traffic jams takes hacking to a whole new level.
While I also agree that Dwight is a poor example, sometimes the outsider does have to be an asshole.
The only way I've found to break through an echo chamber is by being enough of a jerk that everyone gets jolted out of their little world for a while.
I mean, let's say a bus is coming towards you. If you're in this thing, you're toast. But if you just WALK, you can always jump out of the way.