Horses need to be fed, watered, cleaned-up after, and groomed. They sometimes get sick with a huge variety of different ailments, which need to be cured in lots of different ways --- you can't just swap in a new part. They have personalities and moods. They grow, get old and die. Outsourcing all that is not really practical because most of it happens where they're stabled; if you outsource that then it's comparable to a taxi, not a personally owned car.
Some gadgetry gives much better cost-benefit than others. ABS braking seems like a high payoff. General-purpose OS running an entertainment system connected to the CAN bus, not so much.
Baiting schools into overreacting to security threats isn't that hard. There have been numerous cases involving toy guns, and even kids pointing their fingers like guns (and who hasn't done that?). Do you really think it's a good idea to support families who bait schools into overreacting in search of a payout? Not only does that mean transferring money out of already-strapped school systems, but it makes the lives of school administrators just that much harder.
It turns out that you do not need to connect a fridge to the Internet for it to do its job well. Internet connection might make certain activities slightly more convenient... at the cost of an increase in hidden complexity that you'll pay for down the line, e.g. when your fridge is recruited to a botnet.
A horse is actually far more complicated and difficult to maintain than a car, so that analogy fails. Cramming cars with needless gadgetry is indeed making them dangerously complex and we're going to pay for that later.
Many CIOs will dive head-first into IoT, get a lot of good PR, stock prices will rise and they'll be rewarded. Then their companies will discover the IoT security nightmare, get lots of bad PR, stock prices will sink and the CIOs will blame it on someone else. Result: happy CIOs and IoT vendors and an absolute disaster for everybody else.
"slaughter of civilians on a scale that makes ISIS look like a bunch of schoolboy puppy-stranglers"... almost entirely by competing local militias, not the CIA as you implied.
Courts can evaluate whether a belief is sincerely held. This happens frequently, e.g. in perjury cases. So the DMV could require the applicant to swear that the belief is sincerely held, and then in cases (like this one) where it obviously isn't, they can take the person to court to make an example of them.
You can apply for an ESTA (visa waiver) on the Web. It's not the greatest Web site ever but it's been there for years and works well enough. So they've got at least one successful project under their belts.
It seems very risky to me to have contractors set up a very complex system (i.e. any software system) and then move on. They will not be able to write down all the information you need to maintain it properly.
Of course this happens all the time already, but that doesn't make it healthy.
That's their measure of "standards compliance". Unfortunately it's rather bogus. It includes non-standard stuff like WebSQL, which is not a standard at all and was only ever implemented in Webkit (which Blink inherited). Also, it's just checking for the presence of features and doesn't do any testing how well those features work. So it incentivizes browser to provide a bare-minimum buggy implementation of every feature under the sun, which isn't actually good for the Web.
We have to live in the real world where a significant percentage of users have some kind of malware or quasi-malware (e.g. Ask toolbar or anti-virus software) installed.
> Nobody wants to store and provide videos in two formats.
No, there is an opening for another format with significantly better compression. Youtube serves H.264 and VP9. Netflix serves H.264 and wants to support another format (hence they're in AOM).
We (Mozilla) have Daala, which is the only video codec around that is competitive and based on technology radically different from H.264/H.265. That's an important contribution.
We have Daala, which (unlike VP8/9 and Thor) is radically different technology to H.264/H.265. That's very valuable because it steers away from the patent minefield. Also, our codec developers are among the best.
These companies aren't going to drop support for Apple's devices. They're going to serve both H.264 and the new free codec --- to support old not-upgraded devices, as well as Apple devices. So if Apple doesn't join the party, the main impact will be that iPhones need twice as much bandwidth as Android phones to play video.
This announcement is terrific news for free codecs. We've been fighting for this at Mozilla for a long time and now it looks like we have a good chance of winning.
I'm mid-40s, my wife's a little older, our two kids are in their teens. No apparent loss of interest in sex from either of us. There was a period of reduced interest, but we got through it.
Two differences from your story: 1) my wife doesn't work right now (hopefully soon). 2) We're Christians, and regular sex is a commitment (1 Corinthians 7).
C++14 is good in many ways. We have adopted many modern C++ features in Firefox, like closures. (STL features are unfortunately limited due to the crappy STL situation on Android.) However, it just doesn't provide any of the safety guarantees of Rust. You *can* write safe code in C++, but it's always very easy to accidentally write unsafe code that corrupts memory.
The Rust compiler is slow, but that's being worked on. The actual generated code is good. Servo benchmarks show it crushing Webkit, Blink and Gecko (even on single-core) --- mostly due to better algorithms, but it wouldn't win if Rust was a performance problem.
"2100 open Github issues" is a meaningless statistic. Compared to what? Zero issues would just mean it's a dead project.
Slashdot Mirror
Simpler approach: drop him in the middle of a minefield with his device, and wish him luck.
"500 years burning alive anyone who practiced science"?
I assume this is a troll, or just a bad joke.
Horses need to be fed, watered, cleaned-up after, and groomed. They sometimes get sick with a huge variety of different ailments, which need to be cured in lots of different ways --- you can't just swap in a new part. They have personalities and moods. They grow, get old and die. Outsourcing all that is not really practical because most of it happens where they're stabled; if you outsource that then it's comparable to a taxi, not a personally owned car.
Some gadgetry gives much better cost-benefit than others. ABS braking seems like a high payoff. General-purpose OS running an entertainment system connected to the CAN bus, not so much.
Baiting schools into overreacting to security threats isn't that hard. There have been numerous cases involving toy guns, and even kids pointing their fingers like guns (and who hasn't done that?). Do you really think it's a good idea to support families who bait schools into overreacting in search of a payout? Not only does that mean transferring money out of already-strapped school systems, but it makes the lives of school administrators just that much harder.
It turns out that you do not need to connect a fridge to the Internet for it to do its job well. Internet connection might make certain activities slightly more convenient ... at the cost of an increase in hidden complexity that you'll pay for down the line, e.g. when your fridge is recruited to a botnet.
A horse is actually far more complicated and difficult to maintain than a car, so that analogy fails. Cramming cars with needless gadgetry is indeed making them dangerously complex and we're going to pay for that later.
Many CIOs will dive head-first into IoT, get a lot of good PR, stock prices will rise and they'll be rewarded. Then their companies will discover the IoT security nightmare, get lots of bad PR, stock prices will sink and the CIOs will blame it on someone else. Result: happy CIOs and IoT vendors and an absolute disaster for everybody else.
"slaughter of civilians on a scale that makes ISIS look like a bunch of schoolboy puppy-stranglers" ... almost entirely by competing local militias, not the CIA as you implied.
Courts can evaluate whether a belief is sincerely held. This happens frequently, e.g. in perjury cases. So the DMV could require the applicant to swear that the belief is sincerely held, and then in cases (like this one) where it obviously isn't, they can take the person to court to make an example of them.
You can apply for an ESTA (visa waiver) on the Web. It's not the greatest Web site ever but it's been there for years and works well enough. So they've got at least one successful project under their belts.
It seems very risky to me to have contractors set up a very complex system (i.e. any software system) and then move on. They will not be able to write down all the information you need to maintain it properly.
Of course this happens all the time already, but that doesn't make it healthy.
Entirely agree, except it's even worse because the "finally secured" part never actually happens.
That's their measure of "standards compliance". Unfortunately it's rather bogus. It includes non-standard stuff like WebSQL, which is not a standard at all and was only ever implemented in Webkit (which Blink inherited). Also, it's just checking for the presence of features and doesn't do any testing how well those features work. So it incentivizes browser to provide a bare-minimum buggy implementation of every feature under the sun, which isn't actually good for the Web.
We are relatively lean and mean compared to other browsers, but that doesn't mean "no memory issues", of course. So enough with the straw men.
Please file a bug and include the contents of an about:memory report.
We have to live in the real world where a significant percentage of users have some kind of malware or quasi-malware (e.g. Ask toolbar or anti-virus software) installed.
Well, apart from the fact that we spent years fixing leaks and usually have the best memory usage of any browser.
"Pushed by Google"? Last I heard, Google was for WebRTC over ORTC.
I think you're getting your bogeymen confused. GMO opponents tend to be the bogeypeople on the left.
Corbyn and McDonnell are on this list:
http://www.parliament.uk/edm/2...
> Nobody wants to store and provide videos in two formats.
No, there is an opening for another format with significantly better compression. Youtube serves H.264 and VP9. Netflix serves H.264 and wants to support another format (hence they're in AOM).
We (Mozilla) have Daala, which is the only video codec around that is competitive and based on technology radically different from H.264/H.265. That's an important contribution.
We have Daala, which (unlike VP8/9 and Thor) is radically different technology to H.264/H.265. That's very valuable because it steers away from the patent minefield. Also, our codec developers are among the best.
These companies aren't going to drop support for Apple's devices. They're going to serve both H.264 and the new free codec --- to support old not-upgraded devices, as well as Apple devices. So if Apple doesn't join the party, the main impact will be that iPhones need twice as much bandwidth as Android phones to play video.
This announcement is terrific news for free codecs. We've been fighting for this at Mozilla for a long time and now it looks like we have a good chance of winning.
I'm mid-40s, my wife's a little older, our two kids are in their teens. No apparent loss of interest in sex from either of us. There was a period of reduced interest, but we got through it.
Two differences from your story: 1) my wife doesn't work right now (hopefully soon). 2) We're Christians, and regular sex is a commitment (1 Corinthians 7).
C++14 is good in many ways. We have adopted many modern C++ features in Firefox, like closures. (STL features are unfortunately limited due to the crappy STL situation on Android.) However, it just doesn't provide any of the safety guarantees of Rust. You *can* write safe code in C++, but it's always very easy to accidentally write unsafe code that corrupts memory.
The Rust compiler is slow, but that's being worked on. The actual generated code is good. Servo benchmarks show it crushing Webkit, Blink and Gecko (even on single-core) --- mostly due to better algorithms, but it wouldn't win if Rust was a performance problem.
"2100 open Github issues" is a meaningless statistic. Compared to what? Zero issues would just mean it's a dead project.