That's not the new Microsoft, that's the Microsoft of the last decade.
Also consider that in most markets, Windows Phone is closer in phone marketshare to iOS than iOS is to Android. That's not saying a lot. But WP is definitely at the #3 spot, and the way this market is... if they can find that itch to scratch, things could change within the course of two or three years.
Which is like bragging about Pluto because it's closer to the Sun than to Proxima Centauri.
Third place in the mobile market is a dubious distinction, at best. In reality, Windows phones are irrelevant, but only slightly less irrelevant than, say, BlackBerry.
Also, why do we care what a former biologist, now sci/tech article writer for the WSJ has to say about technology-related education? Is there some connection that I'm missing?
Wall Street dreams of coding to become yet another minimum-wage unskilled job. It probably will, simply because coding isn't all that difficult, just tedious, and as computers continue getting everywhere programming will ultimately become like literacy is now.
Thanks for this. My experience with the refurb vendors has been fair to terrible. I wonder if I should just replace the caps on a leaky refurb toner I got. Brother makes good machines and sells their carts for a king's ransom. I was literally contemplating $50 more for a new Brother color laser than for a set of toner carts for my existing Brother color laser. The refurbs run 25% of the cost, but I'd rather refill them myself now that I know it's possible.
As to the OP - don't spend a gallon of gasoline to bring a toner cart in for recycling - just toss in the trash if that's your only option (for a brand without a mail-back program). Economics is hard, but recycling without considering economics is stupid.
I don't like what you're saying, but it's true. For this reason I disable ipv6 wherever I care about security (vmlinuz ipv6.disabled=1), because I can't trust the existing implementations and I'm pretty sure there will be data leakage if I don't (this story doesn't help assuage my concerns). Therefore, I'm not engaged in filing bug reports very much, because I mostly have to avoid it. Quite a Catch-22.
Also my ISP doesn't offer it and most endpoints don't offer it, so it just adds latency for Internet operations. There are clearly incentives missing or the situation would be better. The recent move to monetize IPv4 space transfers might finally be the impetus needed for network operators to move their internal nets to IPv6, but look at Android 5 not even supporting DHCPv6 (which administrators seem to want) and you can see how far we have to go - whether Google or the admins wind up backing down, there are still fundamental philosophical disagreements about how v6 should be disabled and no amount of shouting "but I'm right" will solve it. That's in 2015 with at least a lead time of five years for everybody to get on the same page, *after* there is agreement. And even if monetization of IPv4 does start to work, the BGP community has had its head in the sand for two decades and really can't handle it.
IPv6 is necessarily more complex than IPv4 since it shifts the complexity of kludges into services (the tech schools aren't even teaching it so only alpha nerds even understand the stack) and fundamentally the transition plan was "we'll make a spec and then everybody will support it for altruistic reasons") which is such a monumental failure in understanding human action that it's socially embarrassing to be associated with the spec. The IPv6 transition will be a warning to future generations about how not to advance technology in society.
Yet we still need it.
It will display a warning and let you continue
No, it won't - and that's the whole problem. It prompted me to write this piece on re-enabling SSLv3 on Firefox which is probably the most heavily-trafficked post I've done on that blog.
Most of these devices will support HTTP and HTTPS. The posture of the browser developers is to blow up HTTPS support on SSLv3 everywhere, regardless of the risk profile.
There are very few people who are going to get $1100 to replace a PDU because the current one only supports SSLv3. As it currently stands, those people have to re-enable SSLv3 for the whole Internet on their browsers to admin their local devices. Pretty soon they will have to stop updating their web browsers entirely.
There are only two possible real world outcomes:
1) people will re-enable HTTP administration and start sending their passwords cleartext on their LANs
2) the very people in companies who do security work will be running outdated browsers, on purpose, to connect to their gear.
3) a million dollars will appear overnight in a company's budget to replace gear for highly theoretical risks
simply is not an option that exists concurrent with reality.
If the browser engineers had handled the situation the same way as self-signed certs, or even made a more complex UI to specifically whitelist certain hostnames or subnets, then we could have made a reasonable transition. But that would have been hard work with real analysis required, and why do that when flipping a switch and boldly posturing is more crypto-macho?
The very same people who jeered corporate people for staying on IE6 are creating exactly the same situation in regards to SSLv3. They may understand a narrow aspect of cryptography very well, but they completely fail to understand the security of complex systems. They are hurting the security and privacy we're working so hard to achieve. Jeers indeed.
you've also never had a mini-gun pointed at him by private "security" personal
There are private security personnel with miniguns? Are they accepting applications? I don't actually want the job, I just want to go through training and shoot the guns.
Or be a better netizen by running your own and forwarding to your ISP's.
The whole reason OpenDNS even exists is because ISP's proved they cannot be trusted to run an honest DNS. And let's not pretend that DNSSEC is universally deployed.
Most people here can setup up a 99 cent VPS with an openvpn endpoint running a recursive resolver, limited to the openvpn net. That fits in the smallest slice of RAM available in 2015 and will work fine.
Most other people cannot, though. Google's DNS is honest, if you don't care about tracking - but most people care more about free stuff than privacy.
Link to Original Source
I'm not talking about the old episodes. I'm talking about resurrecting the show as a made for Netflix series.
At $2M/episode * 20 episodes/year = $40M / year. For $20/month that would take less than 170,000 fans to keep the show running, not counting any income from DVD sales, merchandising, licensing, etc. I bet there are that many fans who would do that without a problem.
The GPL is "viral" in that if you use even a smattering of GPLed code, you are required to release ALL of your code as GPL as well.
Not true. Go back and re-read the GPL. You are required to release your code under a license that places no more restrictions on it than the GPL. You must also license the combined work under the GPL. It is, however, completely fine to take a few files of GPL'd code, combine them with some BSDL'd code files (as long as those files are not a derived work of the GPL'd code) and ship the resulting program under the GPL. If someone else takes only the BSDL'd files for use in another project then they are not bound by the GPL.
There are two ways in which the GPL is 'viral'. The first is that you cannot change the license of something that you do not own, so any derived works retain the copyright and license of the original. The second is that the GPL is a distribution license and, if you wish to retain the right to distribute it, then you must not distribute it in a way that does not pass on the freedoms listed in the license (meaning that the combined work must grant all of the permissions as the GPL'd parts).