Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
Note: You can take 10% off all Slashdot Deals with coupon code "slashdot10off." ×

Comment No, obviously (Score 5, Funny) 188

... unless of course you're terrified of computers and networks, view them as tantamount to witchcraft, don't understand them, and hate and fear anyone who does. Then of course, by all means, grab your torch and pitchfork. The rest of the loonies will be waiting in the town square at midnight.

Comment Re:It can't. (Score 1) 93

But based on what we know about the basic building blocks of life as we know it there's nothing to suggest they would have to originate from a planet that is habitable, nor that they would even all have to come from the same place to get combined somewhere that is habitable in the same way they were combined here on Earth.

Comment Re:Idiocy. (Score 2) 392

He probably doesn't want that type of responsibility. I'd do it in a heartbeat though, and at bargain rates, but I assume that if the real thing holding back their willingness/ability to use Linux right was the lack of just one competent sysadmin willing to spend a few weeks on training staff how to do things in Linux that they take for granted having already learned in Windows then they would have hired such a person long, long ago - before the Linux deployment. No, whatever the real reasons, that is clearly just an excuse. This whole orchestration probably has something to do with forcing the government's hand on IT spending, and may have been actually the plan all along before the initial switch to Linux. The fact that the claims are absurd and googleably false and sound more like first-week helpdesk interns' forced opinions about Linux without any training or accountability than the analysis of actually experienced IT staff is the proof something more is going on here we're not being told about.

Comment Re:Nature of open source (Score 1) 157

... answer is a resounding "no".

Here's the point where we differ. You actually think this statement has been proven to be anything other than completely farcical, despite failing to show why. You purport to naively assume this to be the case, but its provably factually inaccurate based on numerous prior incidents. Microsoft is NO friend of interoperability, despite the fact they haven't managed to completely quash it in all aspects of their software interactions with foreign systems. In your gleeful fervor to try to show off your sophomoric understanding of tech terminology and attempt to sound intelligent and invalidate my entire argument based on one subjective choice of wording, you've clearly missed the point of my entire argument, which is that Microsoft *certainly* would sabotage NTP, and its probable that this one old man is the only thing cultivating the industry-wide support for NTP that has so far held them back from doing so. And you can bet that his desk chair won't even be cold before they're trying to figure out how to stuff banner ads into the protocol so you have to watch a 30 second clip about erectile dysfunction medication before your clock will sync up to the network time.

Frankly I've satisfied myself that you're a paid shill, so this conversation is over.

Comment Re:Nature of open source (Score 1) 157

So you think because you disagree with my use of the word "strategies" where maybe I should have typed "services," "products," or "protocols" invalidates the entire rest of my statement?

I'd love to see you justify your apparently hyper-naive assumption of how having a mix of entirely separate OS and hardware compatibility issues to contend with would have "nothing to do with" the task of getting network time to properly sync up in the hypothetical world where NTP wasn't already the de-facto industry stanard but Microsoft's non-cooperation strategy still permeates everything.

Comment Re:Nature of open source (Score 5, Insightful) 157

I got news for you; if NTP was non-free, it never would have been used outside of the lab where it was created. There would be 1000 competing network time sync strategies, Microsoft would blithely tell the whole world theirs is the best and universally compatible, while not actually being universally compatible with anything other than third-party malware, and it would be damned-near impossible for anyone without a Master's and 20 years of industry experience to succeed at establishing time synchronization across networks of machines supplied by a heterogeneous mix of OS and hardware vendors. You really want to take NTP and throw it in the same playpen where file-sharing and web-markup language standards got mangled? Really?

Variables don't; constants aren't.

Working...