You realize, of course, that systemd bears many similarities to launchd on MacOS X, which " essentially a replacement for init, rc, init.d script, rc.d script, SystemStarter, inetd / xinetd, crond / atd, [and] watchdogd"?
Processors aren't the bottleneck; I/O bandwidth is. The "weeds of 'structured' crap" is the difference between a log query running in milliseconds or hours when you're generating terabytes of log data every day.
Dell, who knows what is going on with that.
Leveraged buyout, narrowly averted proxy fight, some shake up of C-level executives, and a workforce reduction of a few thousand.
You might point out that the Video Player Tutorial on the VIERA Connect Developer portal uses jQuery.
RDP has supported remote applications since 2007: http://msdn.microsoft.com/en-u...
1) How many of the people who reflexivly project hate at Java have solid, defensible reasons for doing so? Do you think people form opinions based on evidence and thoughtful consideration?
2) Examples, please.
3) Well C is not a long-lived programming language, then. COBOL, FORTRAN and LISP have been going strong since the 1950's!
3.1) Plenty. Most of the applications on my phone runs Java (Android). My cable box (OCAP). My Blu-ray player (BD-J). Several of the applications I administer or use professionally (IntelliJ, Confluence, Jira, Zimbra, JMeter).
Just because you don't see it doesn't mean you don't use it. And even if you don't use doesn't mean other people don't use it. Java is an incredible pervasive language in the embedded and server space.
3.3) With a twelve year history, multiple implementations and no hint of a successor, this strikes me as needless fear-mongering. Microsoft is proprietary, not fickle. Most of their standards have excellent longevity and they have far longer support cycles for their products than most of the Unix world.
As for performance, you're full of it.
I, for one, welcome our new MCP overlord.
I suspect it is about establishing precedent and combating the idea that EV owners are entitled to "free" power, not about recovering costs in this specific incident.
That's because Democrats wanted people to believe default was a credible threat. It wasn't. No one who knew what they were talking about thought it was, hence the stability of interest rates.
Really, it's the sort of thing that you don't realize you want until you have it, then you are annoyed if you don't have it.
Even under the best conditions, half a second is a bit of an exaggeration, and you're often not under the best of conditions. The cable slipped behind the desk, or you realize that you forgot to plug your phone in after you turned off the light or took off your glasses, or you're driving and don't want to be the asshole who causes an accident because you were fiddling with a cablet instead of keeping your eyes on the road, or your cable is getting dodgy and you keep forgetting to order a new one.
And then there is the annoyance of having your phone go dead because you were too tired to bother flipping the light back on, or never did hit a red light long enough to plug your phone in, or you jostled your phone and it stopped charging.
Is it a need? Certainly not. But it is damned handy.
Big businesses get discounts because they sort their mail, prepare them for automated processing and sometimes transport them to postal facilities. In other words, they pay less because they cost less to service. You could pay the same price if you printed your mail with IMpb barcodes, pre-sorted it and sent it in batches of five hundred or more.
Commecial first class and bulk mail services provide the volume necessary to keep postal rates relatively low and routes open. Increase their rates, volume will drop, and everybody's rates go up.
The raw number isn't very meaningful. There are over 250 million passenger vehicles registered in the United States. That comes to one fire per 1641 vehicles. There are something like 12 thousand Teslas, but also only three fires, which comes to one fire per 4000 vehicles.
So with those numbers, they still seem better off than combustion driven vehicles. However, fleet size isn't the only variable. The majority of Teslas are less than a year old, while overall only 13.5% of passenger vehicles are under two years old, and 60.6% are at least seven years old. Teslas are also a luxury vehicle with a base price of $69,900 (before tax credits) and allegedly stringent manufacturing standards, compared to the overall market with an average new sale price of $24,764 and varying quality. And finally, maintenance needs to be taken into consideration. Not only are Teslas newer and almost certainly under warranty, the average owner is relatively wealthy and presumably can afford proper maintenance.
But even that is not necessarily the right set of stats to look at. The three Tesla fires occurred after an accident, so it may be more informative to look at the liklihood of accidents to result in fire. According to the NFPA, only 4% of automobile fires were the result of a collision or roll-over; most were caused by a mechanical or electrical failure. There were about 5.4 million accidents in 2010, so at 4% of 152300 accident it comes out to approximately one fire per 900 accidents. There are no hard statistics on precisely how many accidents there are for Tesla specifically, but it would have to be a significantly high number to have a lower fire to accident ratio. And that isn't even taking into account the relative severity of accidents into account.
Of course the real problem is that there simply isn't enough data available. Three times in as many months could be a fluke. Or it could be a pattern.
There is a reason why other distributions - even ones that had switched to Upstart - adopted systemd.
There is a reason why other distributions - and toolkit developers - opted against supporting Mir.
And it has nothing to do with the tea party.