Those who follow the semiconductor market closely and don't have a horse in the race would beg to disagree with you on all points, especially your assessment of Qualcomm's FRAND practices:
.
...it was pretty obvious that Apple was in the wrong, allegedly caught red handed, and dug the hole deeper with their petty and vindictive reactions. Qualcomm claims to have multiple emails where Apple gave sensitive trade secrets to a competitor, then refused to allow Qualcomm to exercise their contractual audit rights. While there may be some more evidence not presented publicly, it sure looks like Apple was in the wrong.
Some former Google products haven't been killed, per se, but have been dumbed-down so badly that just killing them might have been a more merciful end.
Perhaps here is a good place to mention that you could learn more about real-world security auditing and code hardening by reading the LibreSSL developer's comment log here, billed as "Tearing apart OpenSSL, one arcane VMS hack at a time."
.
It's also one of the funniest developer-centric things I've ever read - no holds barred for these guys in their contempt of the code they're ripping to shreds. Win/win.
So would clients built using the SSL libraries from the (stripped-down, un-borked) version of SSL that the OpenBSD team recently did - LibreSSL - vulnerable as well?
A vital detail that those outside the city (and many within it) don't know - and of course won't get from the inflammatory OMG! NANNY STATE! headline/summary - is that the City of Seattle doesn't have a local landfill. Hasn't for many years; there's no nearby space. Instead, all garbage is loaded onto train cars - hundreds of them a day - and sent by rail to a landfill in rural Oregon, about 250 miles away. That was the cheapest alternative for the city, even though it involves paying twice (once to transport it, and again to the landfill operator). But it's still expensive.
.
Given that it's in the best interest of the City _and_ its ratepayers to reduce the amount of landfillable waste (aka number of train cars) in favor of more economic alternatives; specifically, recycling and composting, both of which are able to be handled within a few dozen miles of the city, at much lower cost than the landfill trains. The alternative is to have even more and longer trains and higher rates for garbage for everyone.
.
Kind of the opposite of a nanny state; this is pure and simple economics. If the spectre of a few $1 fines for the few residents who can't be bothered to separate their greasy pizza boxes into another bin makes everyone's garbage rates lower, then I'm all for it.
Submitter and article author is a "technology consultant". For him, there's no such thing as bad publicity. Even a thoroughly discredited submission polishes his resume as an Expert To Be Reckoned With.
More importantly, the above-referenced Times blog post points out that the gender imbalance in Seattle is nowhere near as bad as other cities that are tech hubs, like San Jose. Among the 50 largest metro areas in the US, Seattle apparently ranks at only 15th for predominance of males.
.
Noting, too: the original Reifman article makes the truly odd presumption that because Amazon's _current_ workforce is 75% male, that all new hires will necessarily follow this same 3-to-1 male-to-female gender ratio - something I very much doubt. A company growing as fast and expanding into new, diverse areas like Amazon is, is likely to see a greatly more gender-balanced workforce than it had in its early tech-dominated early days. Maybe the new hires will not be 1:1 male:female - but certainly not the 3:1 of the past.
The Seattle Times has already debunked this, pointing out that the author(*) of that original article coflated two data sets that used completely different methodologies for the "number of single men" metric and so cannot be compared. Not that that will make any difference; I sense this will have the same life of its own as the "chances of a woman getting married after 40 are worse than that of her getting killed by a terrorist" meme that went around a decade or so ago, because it provides a convenient external explanation for a wholly internal failure.
.
/tsg/
(*) Said author of the original debunked article also has the same user name as the submitter here - such a coincidence! I also note his last Slashdot submission was the also-debunked "OMG! Skydiver catches meteor falling on camera!" thing that was proven false a few days later. The Force is not strong with this one, fellow Jedi...
Dense doesn't matter for the physics of the heat, of course. But it makes the cup more expensive to ship and to heavy to use. That's my point about gallium.
All good, except; gallium is hella expensive. And very very dense, therefore very heavy.
My money is on good old-fashioned paraffin wax, which (at least in the bulk candle variety that I bought in my hippie candle-making days) melts at exactly 140F.
Cheap and food-grade (it coats many candy items) and pretty light.
It's easy to opine on a topic you know little about with a bromide like, "change is hard for a lot of people". There, POOF! You've successfully dismissed anyone who has a complaint against the change - including those cogent technical reasons for thinking that Yahoo has in this case effed up royally and radically diminished the functionality of an old (but reliable and working) interface. Now they're all nearly put in some "change is hard" Luddite basket. Way to go, Captain. Rhetoric!
.
Tell you what. Let's go ahead and have you *moderate and run* (not just play with as an end user) a Yahoo group with 27,000 members in your spare time (as I do and have for many years). You get a week to do it with those "ancient" tools and interface, and then another week to do with with the badly broken, slow, ill-conceived, feature-poor, absurdly buggy new interface. After that week - if you can even get through it - come back and tell me that "Neo" is working just fine, thank you very much.
We won't even get started on your false dichotomy - that because some features might have been desired (eg inline attachments, which my users would never want or need) that it was necessary to completely revamp the entire interface and throw out about half the existing functionality to provide them.
One interesting feature of the table is the resulting position of iron(Fe) - it serves as the single, pivotal point that "links" the two halves of the table and spiral together.
And, of course, iron is at the bottom of the binding energy curve - it can't be fissioned or fusioned to provide net energy output.
My physics education is too far in the distant past to discern if these two things are just a coincidence - or significant feature resulting from the inherent structure of the table.
Wish I had mod points to toss at you for this. Too many here - perhaps understandably - have no idea of the steps necessary to imagine, design, test, troubleshoot/re-engineer, certify, build, and ship a Real Working Product. If they knew even a fraction of what has to happen before something shows up at Newegg, they might have more understanding of why what you're trying to accomplish is so cool and potentially game-changing.
.
Kudos to you and your crew for getting even this far on a shoestring.
Harlan Ellison: ""Gene Wolfe is engaged in the holy chore of writing every other author under the table. He is no less than one of the finest, most original writers in the world today. His work is singular, hypnotizing, startlingly above comparison."
In the very limited (3) cases that I've had to try and revive a client's dead desktop drive, replacing the PCB board from an identical model - usually purchased cheaply, used or new, online - has always worked.
The other advantage of this approach is that if the first drive becomes revivable, even a time, you now have a second same-capacity drive to transfer the data to (using intermediate storage media if in fact it was the PCB that was the problem and you can only get one drive working at a time).
If it doesn't work, you're no worse off and still have a replacement drive to load data from your (hopefully recent) backups.
And if anyone knows how to take what should be a simple, straightforward, technical discussion and turn it into a MS vs Google flame war, it will be Slashdot commenters.
Slashdot Mirror
.
Read Demerjian's whole piece here for a more complete picture:
https://www.semiaccurate.com/2...
Some former Google products haven't been killed, per se, but have been dumbed-down so badly that just killing them might have been a more merciful end.
(Yes, I'm looking at you, the poor maimed shell of the thing formerly known as Google Finance: http://sneakyfalcon.com/the-ne... ).
Wouldn't it more accurately be described as an A-hole?
Yea science!
"Life is a comedy to those who think – and a tragedy to those who feel."
My thought exactly; you beat me to it. http://en.wikipedia.org/wiki/F...
.
It's also one of the funniest developer-centric things I've ever read - no holds barred for these guys in their contempt of the code they're ripping to shreds. Win/win.
So would clients built using the SSL libraries from the (stripped-down, un-borked) version of SSL that the OpenBSD team recently did - LibreSSL - vulnerable as well?
A vital detail that those outside the city (and many within it) don't know - and of course won't get from the inflammatory OMG! NANNY STATE! headline/summary - is that the City of Seattle doesn't have a local landfill. Hasn't for many years; there's no nearby space. Instead, all garbage is loaded onto train cars - hundreds of them a day - and sent by rail to a landfill in rural Oregon, about 250 miles away. That was the cheapest alternative for the city, even though it involves paying twice (once to transport it, and again to the landfill operator). But it's still expensive.
.
Given that it's in the best interest of the City _and_ its ratepayers to reduce the amount of landfillable waste (aka number of train cars) in favor of more economic alternatives; specifically, recycling and composting, both of which are able to be handled within a few dozen miles of the city, at much lower cost than the landfill trains. The alternative is to have even more and longer trains and higher rates for garbage for everyone.
.
Kind of the opposite of a nanny state; this is pure and simple economics. If the spectre of a few $1 fines for the few residents who can't be bothered to separate their greasy pizza boxes into another bin makes everyone's garbage rates lower, then I'm all for it.
Submitter and article author is a "technology consultant". For him, there's no such thing as bad publicity. Even a thoroughly discredited submission polishes his resume as an Expert To Be Reckoned With.
.
Noting, too: the original Reifman article makes the truly odd presumption that because Amazon's _current_ workforce is 75% male, that all new hires will necessarily follow this same 3-to-1 male-to-female gender ratio - something I very much doubt. A company growing as fast and expanding into new, diverse areas like Amazon is, is likely to see a greatly more gender-balanced workforce than it had in its early tech-dominated early days. Maybe the new hires will not be 1:1 male:female - but certainly not the 3:1 of the past.
.
(*) Said author of the original debunked article also has the same user name as the submitter here - such a coincidence! I also note his last Slashdot submission was the also-debunked "OMG! Skydiver catches meteor falling on camera!" thing that was proven false a few days later. The Force is not strong with this one, fellow Jedi...
A1: Successive approximations.
A2: A random number generator
.
Hey, folks, I can keep this up all day.
http://www.netjeff.com/humor/item.cgi?file=PentiumJokes
Dense doesn't matter for the physics of the heat, of course. But it makes the cup more expensive to ship and to heavy to use. That's my point about gallium.
All good, except; gallium is hella expensive. And very very dense, therefore very heavy.
My money is on good old-fashioned paraffin wax, which (at least in the bulk candle variety that I bought in my hippie candle-making days) melts at exactly 140F.
Cheap and food-grade (it coats many candy items) and pretty light.
.
Tell you what. Let's go ahead and have you *moderate and run* (not just play with as an end user) a Yahoo group with 27,000 members in your spare time (as I do and have for many years). You get a week to do it with those "ancient" tools and interface, and then another week to do with with the badly broken, slow, ill-conceived, feature-poor, absurdly buggy new interface. After that week - if you can even get through it - come back and tell me that "Neo" is working just fine, thank you very much.
We won't even get started on your false dichotomy - that because some features might have been desired (eg inline attachments, which my users would never want or need) that it was necessary to completely revamp the entire interface and throw out about half the existing functionality to provide them.
And, of course, iron is at the bottom of the binding energy curve - it can't be fissioned or fusioned to provide net energy output.
My physics education is too far in the distant past to discern if these two things are just a coincidence - or significant feature resulting from the inherent structure of the table.
Wish I had mod points. Excellent, fair, detailed analysis. You must be new here. :)
.
Kudos to you and your crew for getting even this far on a shoestring.
1.6 MPa = 232 psi (pounds/sq in). High, sure, but within the level you can contain in a soda pop bottle.
Would mod you up if I had points. And add:
Harlan Ellison: ""Gene Wolfe is engaged in the holy chore of writing every other author under the table. He is no less than one of the finest, most original writers in the world today. His work is singular, hypnotizing, startlingly above comparison."
In the very limited (3) cases that I've had to try and revive a client's dead desktop drive, replacing the PCB board from an identical model - usually purchased cheaply, used or new, online - has always worked.
The other advantage of this approach is that if the first drive becomes revivable, even a time, you now have a second same-capacity drive to transfer the data to (using intermediate storage media if in fact it was the PCB that was the problem and you can only get one drive working at a time).
If it doesn't work, you're no worse off and still have a replacement drive to load data from your (hopefully recent) backups.
And if anyone knows how to take what should be a simple, straightforward, technical discussion and turn it into a MS vs Google flame war, it will be Slashdot commenters.
I live in Seattle, you insensitive clod!
(where many residents were still using their furnaces as of last week, and today's the first sunny and warmish-day in what seems like a month)