Google didn't reimplement the API. Apache did with Apache Harmony. Or rather, IBM did most of it and contributed the code to Apache.
And the reason Apache Harmony existed was as a credible "plan B" if Sun / Oracle started being dicks about open sourcing Java or excluding Apache from technology compatibility testing. When the OpenJDK became a thing, IBM switched to that, and Harmony basically fell by the wayside. But the implemented APIs found its way into Android.
And it wasn't the only implementation of the java.* APIs either. GNU Classpath was another one. And Kaffe had an implementation (albeit of an older Java). And in commercial-land there is Skelmir's CEE-J which was another impl that's still going. I had experience using CEE-J for set top box development and it was a delight especially since the "official" alternative was J2ME which sucked balls. But of course none of these efforts would have been worth suing for billions.
Google's "crime" was implementing an API (something which happens customarily all the time in computing) and having enough money to be worth suing. Fortunately they didn't take kindly to the shakedown and fought it out. Whatever you think of Google, this outcome is beneficial for everyone.
If I buy a physical book, music or video I can use it how I see fit subject to copyright. I can lend it to somebody, donate it, sell it, keep it, burn it. I don't care if the bookstore goes out of business, or if I'm in America and I bought the book in Japan. It just works. If I buy a digital book, music or video I can't because I haven't bought a digital book, music or video. I've bought a software licence. A licence that limits how I may play the item, restricts if I can transfer it and could even be revoked or nullified if the platform dies. The licence might incur sales tax that media does not, e.g. UK charges VAT on software (like the licence) but not books.
I don't see why this should be so. Digital media should have the same rights under copyright law as physical media. Encrypt the media and issue an token that holds the key and represents who owns it. Use a block chain to transfer and track ownership. Whoever owns a token owns the media, can decrypt it and has the rights to transfer the token permanently or temporarily to someone else. It shouldn't be hard to enforce and more to the point it imbues digital content with most of the same properties as physical media. I can give my token to somebody else and set the return date. The block chain can enforce and track this. Readers and devices can be certified to enforce it too.
Or use your fingers. Assuming you're using the PC that needs the entropy then every time you type or move the mouse you're basically stirring the pool. On a Linux PC, you can add sources of entropy to the/dev/random including noise but anything you like. I assume anyone *that* paranoid about randomness certainly wouldn't be asking Tor to provide them with some random numbers.
RHEL is for companies who are risk averse. They don't need the latest features, or want an OS which is constantly changing in unpredictable ways. They want something which is reliable, stable, supported and does what they bought it for in the first place. If a 2.6 kernel is good for that purpose then what's the problem?
I don't see any reason to believe this technology will replace display technology as we know it. E-ink displays have never been fast and there is nothing to suppose this display will ever be any faster than mono displays. It's simply inherent to the way the technology works which is like some glorified etch-a-sketch, shaking the particles to reset them and then electrically setting them in some state.
The comparison to LCD is particularly off. I don't know what your Nokia phone's display is, but even the earliest passive colour LCD in a laptop would have looked better than this display and would have been responsive enough to use, albeit a bit washed and blurry with motion.
There are far more promising technologies for passive displays which consume little or no power. Bistable displays, interferometric modulation (mirasol), transflective LCD, electrowetting etc. All would have faster refresh rates than e-ink. Amazon even bought out a electro wetting tech called Liquavista so perhaps they intend to roll with that. Even OLED displays consume power only for the pixels which are on which is why some new phones like the Samsung Galaxy S7 even default to show an always-on clock.
HPFS was doomed by the OS it run underneath. As a filesystem it was rather good considering it was created over 25 years ago and expected to run on 286 PCs.
Node.js is obviously bound by the CPU and other constraints. The point is that if a database query takes a second to return the entire thread isn't blocked until the result comes back. In JS, the query goes off with a promise and the promise is executed when the result is returned. In the meantime the thread can be serving other requests, also from events and handlers. It's not a magic bullet by any means and writing asynchronous code can be painful and nasty. But to return to my original point if someone has PHP working, the fact that Node.js might be more efficient is not a good reason in itself to migrate unless scaling is a problem. And for most setups it wouldn't be.
It shouldn't because it's a form of ad hominem attack. It's one thing to criticize his analysis and say it sucks for stated reasons A, B and C. It's another to imply it sucks because he used to work for Microsoft.
The sample image looks simultaneously oversaturated and washed out. The article seems to suggest its basically CMYK but without the K - the black component that should contrast and depth. So black is just CMY mixed together and looking like muddy brown.
I don't see people who want colour in an e-reader wanting this. They want to read magazines, graphic novels, comics, perhaps even web content. They expect those things to be rendered faithfully in the reader, not the way this thing appears to render them.
Maybe the tech is fine for store displays where garish saturated logos are eye catching and useful. I don't see e-readers getting it the tech in this form. Maybe they need to reverse what they did with E Ink Triton and put the black over the colour E-ink using a grayscale LCD layer.
Node.js is event based and heavily asynchronous. A single process can serve multiple incoming requests via handlers which in turn asynchronously run a database query and leave IO unblocked while it's happening. It might take 1s for the query to complete but the process isn't blocked while it happens and can be serving other requests in the meantime. It means it can scale concurrently with the load. It also has cluster APIs and other functionality if desired.
Most PHP instances run as N spawned subprocesses where it can handle N concurrent requests and no more. Execution is synchronous so if each subprocess is blocking on some query then the website is too.
So that's the benefit. But as I said I don't see it being a justification to move unless someone had scaling issues. And even if someone had scaling issues, they could always just set N to some higher number. I doubt it's a big deal for most sites.
That doesn't mean PHP is a good language. It's awful language but migrating code to something else without a good reason is rarely a good idea in itself.
Node.js isn't a bad environment, but I can't see much reason to move from some other web hosting technology. I suppose if the computer was maxed out with concurrent processes to serve content then perhaps the event based Node.js model might be beneficial. But if not, then it's moving for moving's sake.
Aside from its benefits, Node.js has some substantial dangers. The whole npm model of no locking by default and fuzzy matching is a security disaster in the making.
I left out Windows 10 Phone because it's not Windows 10 that was being referred to. Besides, it is possible to have opinions which are not a straight binary yes or no about one platform or another you know.
Windows 10 is working out fine thanks and it demonstrates that yes, a single OS can support both tablet and desktop. As for Chrome OS / Android, the effort put into Chrome OS would have been better used to make Android fit for the desktop - apps that can reside in windows, proper keyboard / mouse support, printing etc. Not a huge amount actually.
It'd be better if ChromeOS was killed off and the thing *was* Android. e.g. if Google bought out Remix OS out and just made it the official desktop Android. There was little reason ever to support two operating systems in the first place and even less now.
I've never gotten the reason for a lethal injection or some of the more exotic forms of execution. Strapping someone to a gurney and fiddling around for 20 minutes trying to find the veins to inject drugs and then watching for another 30 as they thrash around because it was botched is supposed to be "humane".
If a state was being "humane" it wouldn't execute people in the first place. And that being so it should just drop the pretense and shoot them. Shoot them in the heart and they'll rapidly lose consciousness and die. It's quick, it's effective, it's cheap. And it could be done in a way that doesn't require a human firing squad if that's a concern.
Er no. What I mean is the Model S thinks it is maintaining a distance of D from the trailer vehicle in front when it could be D - 2m because it can't see the overhang. Or the vehicle only recognizes an emergency 2 meters closer than it would for other vehicles. And that difference could mean the difference between life and death.
Auto pilot might assume it's 2 meters further away from the vehicle in front than it actually is. A discrepacy that could mean the difference between your head being separated from its shoulders by the trailer and not. Seems important to know.
The trailer bed was up high with significant overhang of the rear axle while the car sensors are down low - that's how it tucked up under the trailer and damaged the windshield. News footage with pictures. [ksl.com]
If that's the case then it sounds like nobody trust Tesla's self drive feature at all. Bad enough that it hits a trailer at low speed. Even worse if it happened at 70mph.
Announcing to the world you've found a city when you haven't certainly qualifies as "insisting the facts fit".
What did the stars look like during Mayan times? What evidence do we have that they worshiped, venerated or otherwise cared about a certain constellation? How do known cities even align onto this constellation - accurately, or with wild ass fudging? How many cities did they have before they started on this plan or were they living in small settlements? Do the existing cities become the anchor points for this alignment or did they ignore them? And if they ignored them then how did they superimpose the stars onto the earth and in which scale and direction? And how did they avoid building cities on the sides of mountains or in the middle of swamps or miles away from resources (quarries, water, arable land etc.)? And how did they measure distances and direction? How did they survey the land? In what order were these cities founded or did this happen over centuries? Why is there is no record for any of this?
So no, it's not about being unorthodox but starting with an evidence-free assumption and attempting to massage the facts to fit it. Garbage in garbage out. It's the sort of nonsense that some pseudo archeologist like Graham Hancock might come up with. It's not how science should work, orthodox or not.
Peachy printer backers, don't fret. I'll be launching a Kickstarter soon for a printer which can print an entire house. Back me for $100 and I'll post an approximate sketch of the house. Back me for $500 and I'll send you photocopies of the plans. Back me for $1000 (top tier Rube Level) and I'll send you a postcard from the country it's located in. Act now!
Netflix certainly doesn't have ads to the extent of most channels. But you don't escape it entirely. It is always plugging their own shows (complete with automatic trailers these days) on the service AND on tv/radio/web. It's funny how often I'm recommended to watch some shows regardless of what my viewing history might say to the contrary. And the children's section is heavily laced with ads albeit in the form of TV shows - LEGO, Barbie etc. I wonder if Netflix even paid for these shows or if the toy manufacturers gave them for free or even paid to host them. And product placement does happen in their original series.
So yes they have ads but not a huge amount. I wouldn't put it past Netflix to start throwing in affiliate links or buy it now promotions or "this show was brought to you by" or some other form of cross-marketing with certain forms of content.
They're not doing it all at once. And besides power generation is going to be a blend of technologies and any spikes will smooth out as the system scales. And if it came to it and there was an excess or the excess was used during different parts of the day, it could be stored by various means - pumping water to the top of towers, flywheels, molten sodium, compressed air, hydrogen creation etc.
Slashdot Mirror
And the reason Apache Harmony existed was as a credible "plan B" if Sun / Oracle started being dicks about open sourcing Java or excluding Apache from technology compatibility testing. When the OpenJDK became a thing, IBM switched to that, and Harmony basically fell by the wayside. But the implemented APIs found its way into Android.
And it wasn't the only implementation of the java.* APIs either. GNU Classpath was another one. And Kaffe had an implementation (albeit of an older Java). And in commercial-land there is Skelmir's CEE-J which was another impl that's still going. I had experience using CEE-J for set top box development and it was a delight especially since the "official" alternative was J2ME which sucked balls. But of course none of these efforts would have been worth suing for billions.
Google's "crime" was implementing an API (something which happens customarily all the time in computing) and having enough money to be worth suing. Fortunately they didn't take kindly to the shakedown and fought it out. Whatever you think of Google, this outcome is beneficial for everyone.
I don't see why this should be so. Digital media should have the same rights under copyright law as physical media. Encrypt the media and issue an token that holds the key and represents who owns it. Use a block chain to transfer and track ownership. Whoever owns a token owns the media, can decrypt it and has the rights to transfer the token permanently or temporarily to someone else. It shouldn't be hard to enforce and more to the point it imbues digital content with most of the same properties as physical media. I can give my token to somebody else and set the return date. The block chain can enforce and track this. Readers and devices can be certified to enforce it too.
Such as?
Or use your fingers. Assuming you're using the PC that needs the entropy then every time you type or move the mouse you're basically stirring the pool. On a Linux PC, you can add sources of entropy to the /dev/random including noise but anything you like. I assume anyone *that* paranoid about randomness certainly wouldn't be asking Tor to provide them with some random numbers.
RHEL is for companies who are risk averse. They don't need the latest features, or want an OS which is constantly changing in unpredictable ways. They want something which is reliable, stable, supported and does what they bought it for in the first place. If a 2.6 kernel is good for that purpose then what's the problem?
The quality of products from Microsoft is generally fine. And it's still an ad hominem attack.
The comparison to LCD is particularly off. I don't know what your Nokia phone's display is, but even the earliest passive colour LCD in a laptop would have looked better than this display and would have been responsive enough to use, albeit a bit washed and blurry with motion.
There are far more promising technologies for passive displays which consume little or no power. Bistable displays, interferometric modulation (mirasol), transflective LCD, electrowetting etc. All would have faster refresh rates than e-ink. Amazon even bought out a electro wetting tech called Liquavista so perhaps they intend to roll with that. Even OLED displays consume power only for the pixels which are on which is why some new phones like the Samsung Galaxy S7 even default to show an always-on clock.
HPFS was doomed by the OS it run underneath. As a filesystem it was rather good considering it was created over 25 years ago and expected to run on 286 PCs.
Node.js is obviously bound by the CPU and other constraints. The point is that if a database query takes a second to return the entire thread isn't blocked until the result comes back. In JS, the query goes off with a promise and the promise is executed when the result is returned. In the meantime the thread can be serving other requests, also from events and handlers. It's not a magic bullet by any means and writing asynchronous code can be painful and nasty. But to return to my original point if someone has PHP working, the fact that Node.js might be more efficient is not a good reason in itself to migrate unless scaling is a problem. And for most setups it wouldn't be.
That hurts.
It shouldn't because it's a form of ad hominem attack. It's one thing to criticize his analysis and say it sucks for stated reasons A, B and C. It's another to imply it sucks because he used to work for Microsoft.
I don't see people who want colour in an e-reader wanting this. They want to read magazines, graphic novels, comics, perhaps even web content. They expect those things to be rendered faithfully in the reader, not the way this thing appears to render them.
Maybe the tech is fine for store displays where garish saturated logos are eye catching and useful. I don't see e-readers getting it the tech in this form. Maybe they need to reverse what they did with E Ink Triton and put the black over the colour E-ink using a grayscale LCD layer.
Most PHP instances run as N spawned subprocesses where it can handle N concurrent requests and no more. Execution is synchronous so if each subprocess is blocking on some query then the website is too.
So that's the benefit. But as I said I don't see it being a justification to move unless someone had scaling issues. And even if someone had scaling issues, they could always just set N to some higher number. I doubt it's a big deal for most sites.
That doesn't mean PHP is a good language. It's awful language but migrating code to something else without a good reason is rarely a good idea in itself.
Aside from its benefits, Node.js has some substantial dangers. The whole npm model of no locking by default and fuzzy matching is a security disaster in the making.
I left out Windows 10 Phone because it's not Windows 10 that was being referred to. Besides, it is possible to have opinions which are not a straight binary yes or no about one platform or another you know.
Windows 10 is working out fine thanks and it demonstrates that yes, a single OS can support both tablet and desktop. As for Chrome OS / Android, the effort put into Chrome OS would have been better used to make Android fit for the desktop - apps that can reside in windows, proper keyboard / mouse support, printing etc. Not a huge amount actually.
It'd be better if ChromeOS was killed off and the thing *was* Android. e.g. if Google bought out Remix OS out and just made it the official desktop Android. There was little reason ever to support two operating systems in the first place and even less now.
If a state was being "humane" it wouldn't execute people in the first place. And that being so it should just drop the pretense and shoot them. Shoot them in the heart and they'll rapidly lose consciousness and die. It's quick, it's effective, it's cheap. And it could be done in a way that doesn't require a human firing squad if that's a concern.
The 140 character limit does not matter.
I think it matters since it forces people to succinctly make a point.
Er no. What I mean is the Model S thinks it is maintaining a distance of D from the trailer vehicle in front when it could be D - 2m because it can't see the overhang. Or the vehicle only recognizes an emergency 2 meters closer than it would for other vehicles. And that difference could mean the difference between life and death.
Auto pilot might assume it's 2 meters further away from the vehicle in front than it actually is. A discrepacy that could mean the difference between your head being separated from its shoulders by the trailer and not. Seems important to know.
The trailer bed was up high with significant overhang of the rear axle while the car sensors are down low - that's how it tucked up under the trailer and damaged the windshield. News footage with pictures. [ksl.com]
If that's the case then it sounds like nobody trust Tesla's self drive feature at all. Bad enough that it hits a trailer at low speed. Even worse if it happened at 70mph.
What did the stars look like during Mayan times? What evidence do we have that they worshiped, venerated or otherwise cared about a certain constellation? How do known cities even align onto this constellation - accurately, or with wild ass fudging? How many cities did they have before they started on this plan or were they living in small settlements? Do the existing cities become the anchor points for this alignment or did they ignore them? And if they ignored them then how did they superimpose the stars onto the earth and in which scale and direction? And how did they avoid building cities on the sides of mountains or in the middle of swamps or miles away from resources (quarries, water, arable land etc.)? And how did they measure distances and direction? How did they survey the land? In what order were these cities founded or did this happen over centuries? Why is there is no record for any of this?
So no, it's not about being unorthodox but starting with an evidence-free assumption and attempting to massage the facts to fit it. Garbage in garbage out. It's the sort of nonsense that some pseudo archeologist like Graham Hancock might come up with. It's not how science should work, orthodox or not.
Peachy printer backers, don't fret. I'll be launching a Kickstarter soon for a printer which can print an entire house. Back me for $100 and I'll post an approximate sketch of the house. Back me for $500 and I'll send you photocopies of the plans. Back me for $1000 (top tier Rube Level) and I'll send you a postcard from the country it's located in. Act now!
So yes they have ads but not a huge amount. I wouldn't put it past Netflix to start throwing in affiliate links or buy it now promotions or "this show was brought to you by" or some other form of cross-marketing with certain forms of content.
They're not doing it all at once. And besides power generation is going to be a blend of technologies and any spikes will smooth out as the system scales. And if it came to it and there was an excess or the excess was used during different parts of the day, it could be stored by various means - pumping water to the top of towers, flywheels, molten sodium, compressed air, hydrogen creation etc.