Comment Re:Surprise, surprise... (Score 1) 739
The end does not justify the means.
If you were going to go that route, you shouldn't have lead off by arguing from consequences to begin with.
The end does not justify the means.
If you were going to go that route, you shouldn't have lead off by arguing from consequences to begin with.
Application support always says to turn off everything that might possibly interfere with their precious application. They would have you shut down the operating system if they didn't need it. Application support lives in a fairy land where the only thing they have to worry about is their application. They don't have to fix anything if the application isn't broken. They have no interest in anything else. A good vendor will program their application to work with the system standards. Most ISVs are not good vendors.
As a system or network admin, you have to protect the application from the rest of the network and protect the rest of the network from the application and protect everything from the users and the Internet. Part of doing that is firewalling the crap out of your core network, and if you can't do that you should be looking at adding more VLANs and controlling traffic that way.
The possibility of a resonance cascade scenario is extremely unlikely!
Over at Dice
But we are at Dice, sir:
[Querying whois.publicinterestregistry.net]
[whois.publicinterestregistry.net]
Domain Name:SLASHDOT.ORG
Domain ID: D2289308-LROR
Creation Date: 1997-10-05T04:00:00Z
Updated Date: 2014-03-14T22:12:11Z
Registry Expiry Date: 2015-10-04T04:00:00Z
Sponsoring Registrar:Tucows Inc. (R11-LROR)
Sponsoring Registrar IANA ID: 69
WHOIS Server:
Referral URL:
Domain Status: clientTransferProhibited
Domain Status: clientUpdateProhibited
Registrant ID:tuE8gFbzWFO9qSj2
Registrant Name:Host Master
Registrant Organization:Dice Holdings, Inc.
Registrant Street: 1040 Avenue of the Americas
Registrant City:New York
Registrant State/Province:NY
Registrant Postal Code:10018
Registrant Country:US
Registrant Phone:+1.8557527436
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email:hostmaster@slashdotmedia.com
Pros: Today's article has more content than the usual Dice front page linkage. Great article if you're not a programmer but feel stymied by the wide assortment of languages out there. Although instead of hemming and hawing before making your first project you're better off listening to Winston Churchill and sticking your feet in the mud: "The maxim 'Nothing avails but perfection' may be spelt shorter -- 'Paralysis."
Cons: It barely scratches the surface of an incredibly deep topic with unlimited facets. And when one is considering investing potential technical debt into a technology, this probably wouldn't even suffice as an introduction let alone table of contents. Words spent on anecdotes ("In 2004, a coworker of mine referred to it as a 'toy language.'" like, lol no way bro!) could have been better spent on things like Lambdas in Java 8. Most interesting on the list is Erlang? Seems to be more of a random addition that could just as easily been Scala, Ruby, Groovy, Clojure, Dart -- whatever the cool hip thing it is we're playing with today but doesn't seem to quite pan out on a massive scale
If you'd actually read the linked mailing list post (or even just read the quotes of it in the summary) you'd see that none of the abusive comments are aimed at people, they're aimed at the code. He calls the code a bunch of mean, nasty, insulting things, but he doesn't say anything about the people who worked or released that code. I think the distinction is important here. It's not abuse if there's nobody to be abused.
Secondarily: if you read the rest of the thread, he goes on to work with everyone very productively on tracking down the exact nature of the underlying bugs, posts deep analyses of the code generation differences, proposes a patch for his own kernel to work around this GCC bug, and goes and files the upstream Bugzilla report with the GCC team himself. On the whole I'd say this is pretty responsible and cooperative behavior.
What are you doing bringing objective facts into a Slashdot debate, I mean SWJdot?
It sounds like this transformer had its center tap grounded and was the path to ground on one side of a ground loop as the geomagnetic field moved under pressure from a CME, inducing a common-mode current in the long-distance power line. A gas pipeline in an area of poor ground conductivity in Russia was also destroyed, it is said, resulting in 500 deaths.
One can protect against this phenomenon by use of common-mode breakers and perhaps even overheat breakers. The system will not stay up but nor will it be destroyed. This is a high-current rather than high-voltage phenomenon and thus the various methods used to dissipate lightning currents might not be effective.
In March 1989 much of Quebec lost power for the same thing.
They lost power because the common-mode breakers tripped, not because their system was actually damaged.
Sure. Here's a transcript of the earnings call. (You may need to register to read it.)
Nadella does say, early on in his prepared comments, that, "We will streamline the next version of Windows from three operating systems into one single converged operating system for screens of all sizes."
Later during the Q&A session, however, he was asked about how this "one version for all devices" would change the number of Windows SKUs that are available, and he said this:
Yes. My statement Heather was more to do with just even the engineering approach. The reality is that we actually did not have one Windows; we had multiple Windows operating systems inside of Microsoft. We had one for phone, one for tablets and PCs, one for Xbox, one for even embedded. So we had many, many of these efforts. So now we have one team with the layered architecture that enables us to in fact one for developers bring that collective opportunity with one store, one commerce system, one discoverability mechanism. It also allows us to scale the UI across all screen sizes; it allows us to create this notion of universal Windows apps and being coherent there.
So that’s what more I was referencing and our SKU strategy will remain by segment, we will have multiple SKUs for enterprises, we will have for OEM, we will have for end-users. And so we will – be disclosing and talking about our SKUs as we get further along, but this my statement was more to do with how we are bringing teams together to approach Windows as one ecosystem very differently than we ourselves have done in the past.
Lots of hedging in there. You don't need a single, converged OS to give developers "one store, one commerce system, one discoverability system." Those are all ancillary functions. A "team with the layered architecture" doesn't sound like every version of Windows is going to share the same layers. And clearly nothing about Windows is going to be simplified from the customer's perspective; there will still be six or eight SKUs, with each offering different benefits.
Rather, I take Nadella's comments to mean he's streamlining the OS engineering group so that the people working on each Windows platform work in tandem with the others and they all have similar goals, milestones, etc (good).
I also take it to mean that Microsoft will offer developers who are building so-called Modern apps a common set of APIs that will be available on the various form factors, so they eventually should only have to write their apps once and they will run on every kind of device. That sounds OK, but it's only going to be true for Windows Store apps -- and to achieve that, you don't need every device to be running an identical OS.
In other words, no Holy Grail here, but Microsoft is streamlining and rationalizing its OS engineering efforts, which makes good sense at this juncture.
They're not talking about the interface. They're talking about the underlying nuts-and-bolts stuff.
No, they're really more talking about the interface. The underlying nuts and bolts are already pretty much the same, in that Windows, Windows RT, and Windows Phone all share the same NT kernel. But above that there is plenty that's different from platform to platform. What Nadella wants to do is unify the development model and allow developers to create apps with UIs that react and readjust depending on the screen size of the device they're running on, much like how modern websites can support multiple screen sizes. All this talk about "one version of Windows" stems from a single, oversimplified comment Nadella made on the earnings call. When asked about it later, he completely backtracked and said there would not be any such thing.
I would hope this unification means that there will be suffice emulation built into windows that it will pick the kernel/libs/drivers required by the CPU arch, and userland apps can run in emulation (even if slowly) if they are compiled for the wrong proc. This would be a unified windows, that allows x86 and 64 bit apps run on ARM and vice versa (although the other direction is likely not as useful).
Unfortunately for you, the actual article says the exact opposite of the summary (so what else is new on
8 Catfish = 1 Octo-puss
