$49 only gets you the Edison module, which is useless by itself. You also need a base board of some kind. The Edison module with the Arduino-compatible base board shown in the photos will set you back $99. Still a pretty good price. 3x more expensive than a Raspberry Pi, but it is a lot more capable.
I'd get more excited about a 64-bit ARM embedded board, but those aren't available yet, other than a $6000 development board from ARM.
Not all of the code on GitHub is open source, but the majority is -- handy, when that means an account is free as in beer, too.
I'm not privy to any details of GitHub's finances or business model, but most likely it's a good thing that there are non-open-source projects using GitHub, because that's probably what's paying for the free open source use. I've recommended to several clients developing proprietary software the use of GitHub rather than running their own in-house repositories, because the interface is easier for them to use and they don't need as much in-house expertise to manage things. Because Git is distributed, they could of course do both, or easily transition away from GitHub later, and that's a selling point.
Link to Original Source
Doctor Who Media (DWM) was a site created in 2010 and during the ensuing four and a half years it amassed around 25,000 dedicated members.
A source close to the site told TF that since nothing like it existed officially, DWM’s core focus was to provide a central location and community for everything in the “Whoniverse”, from reconstructions of missing episodes to the latest episodes, and whatever lay between.
But yesterday, following a visit by representatives from the BBC and Federation Against Copyright Theft, the site’s operator took the decision to shut down the site for good."
Link to Original Source
Somehow I fondly remember VMS running on HP hardware back in the 90s. A local university had a dialup guest account. It was fun. Going back to the DOS prompt after a finished session always made me hurt and long for something better than DOS.
"Somehow" is that you're hallucinating. VMS didn't run on any HP hardware until 2002. Prior to that it only ran on DEC and Compaq hardware.
nearly 30% of Americans either aren't digitally literate or don't trust the Internet
For that to be true, over 70% of Americans must be BOTH digitally literate AND trust the Internet, which is impossible since anyone who trusts the Internet is not digitally literate.
IPv6 addresses are so long that you can't remember them long enough to read the address from one machine and type it into another.
Which is not a problem because normal people don't have to read the IP address from one machine and type it into another. They use DNS and DHCP, which were specifically intended to eliminate the overwhelming majority of instances of dealing with IP addresses directly.
I've been a networking software engineer for most of my career, so I do have to deal directly with IP address (v4 and v6) routinely, and I don't complain about it. My mother is not a networking software engineer or IT person, so she's had to do that exactly ZERO times in the 15+ years that she's used the Internet.
But, it seems unworkable from a human perspective. No I haven't thought of a better solution. I'm just saying that this is a significant usability problem and a barrier to adoption.
It's not a usability problem, because people shouldn't be directly dealing with IP addresses. If people are directly dealing with IP addresses, that is the usability problem which needs fixing, and not the length of the address.
XFS is prone to data corruption when improperly shut down.
Really? Ugh. I thought most modern file systems were consciously designed to avoid that sort of problem.
They're adding "slow lanes", and moving services that don't pay up into the slow lanes.
The whole thing is nothing but greed. The ISPs at both ends are already being paid for the bandwidth, but the ISP at the consumer end wants to be paid for it twice, once by the consumer and once by Netflix.
Would you argue that if a Microsoft (or other vendor) SSL implementation was used by most of the world's web servers, this would have been less likely to happen? As far as I know, there's no reason to think that any other implementation, open or closed, would be any more immune to such problems. There is little or no evidence that closed source software is generally more reliable, or that substantial effort is made to audit it.
If you're arguing that it's bad that such a high percentage of the world's web servers use the same software, I might agree, but that is completely orthogonal to whether that software is open or closed.