Yes, ActiveDirectory time is synced via the NTP protocol.

ActiveDirectory is a collection of protocols, most of which are based on public standards, NTP, LDAP, Kerberos, ect. Plenty of Microsoft Proprietary piled on top too.

You can point any NTP client at an active directory server and sync from it, just like you can use it for a kerberos realm out of the box, and with Services for Unix installed on your AD server, the schema is extended to support the various Unix attributes required to use nss_ldap and pull full user account info from it.

Windows machines not on a domain will also be happy to sync from a normal NTP server like pool.ntp.org as well, though they use time.windows.com by default.

So you're comparing a Arduino that has an AVR chip, an ARM chip, onboard ethernet and onboard wifi ... with a board thats little more than a break out for an AVR chip and nothing else?

Perhaps if you knew anything about what you were buying, you might have a clue as to why the prices are so different. A Nano and a Yun are radically different devices.

You've essentially just compared an Yugo to a freight train, to use a car analogy.

NTP doesn't just 'return a string of numbers'.

But either way, the article isn't about NTP the protocol, its about one shitty implementation of NTP that I don't think anyone even uses anymore. Windows and OS X certainly don't.

The summary and headline are equivalent to saying 'Netscape is going out of business, HTTP in danger of disappearing'

If he were to drop dead right this instant ... no one that matters would notice beyond his family.

No, it doesn't.

It is observed differently.

Keeping the observations in sync is easy, you base your ticks so they synchronize with ticks of a stationary object in free space. So if you happen to be near a black hole, your clock has to 'tick' much much faster to stay 'in sync' with the pacemaker. Its trivial to synchronize clocks since time is an arbitrary measurement.

Heh, so you don't understand at all how much of a threat Tesla can be to Porsche then, eh? The roadster has some serious clout. Performance wise, ignoring battery life, its a serious contender worthy of debating. Luxury feel? It beats Porsche.

I say this as a Porsche fan who isn't particularly a fan of electric cars. If they get batteries down to 5 minute charge cycles so I can charge in roughly the same time as a fill up, Tesla will probably sell me my next car.

XKEYCODE can be found in a very large OSS software package and was there before the NSA even imagined using the letters for themselves.

... Unless it was put there on purpose, to mislead you into thinking ... it was the NSA.

Seriously, this takes 0 work to make it appear to be the NSA, a 5 minute script could do this to anything, based on the minute level of detail you seem to think is sufficient.

Yes, 1,000 games is a good thing. Sadly, 985 of them suck ass, which makes this a meaningless statistic.

This is not a Linux problem mind you (nor is anything in this post related to Linux, so cool down fanboys), its a Steam problem. Or just problem in general when you lower the barrier to entry for creating something that can be sold. The Apple AppStore suffers from this same problem as well.

I'm all for making it easier for quality craftsmen to get into the trade, but for every 1 quality craftsmen, you get 2500 that shouldn't be doing it.

Steam Early Access only compounds the problem because you end up being able to purchase a lot more really shitty games that are no where near ready for any sort of public viewing.

So great, 1000 games, woohoo ... Not going to get you any switchers due to shear level of crap quality. Steam on OS X is worse still because it doesn't fucking run on case sensitive file systems! WHAT THE FUCK ... You can do it for Linux but not OS X ... AGAIN ... W T F

Which is more than enough to check your email and send word docs around, which is what 99.999% of the population does.

So basically, you don't understand C, so its bad? Is that what you're saying? I'm asking because none of your examples are even mildly difficult concepts.

You seem to have difficulty accepting the syntax for function pointers for one obvious one.

You also don't seem to understand that a pointer and a reference are the same thing, and the array thing your referring to, is also your misunderstanding, its also passing a pointer ... because you don't pass an array ON THE STACK, you pass a reference/pointer to the array.

Your comment about argument mismatches being a problem is easy to solve, don't use a retarded compiler, done. Now the compiler doesn't let you fuck it up. If you make a Java, C++, pascal, or .NET compiler retarded and let it ignore obviously bad code, it'll fuck up too.

Everything in your post is just shear ignorance of the language and its syntax. You didn't even post anything about the actual difficult parts of C. You just made yourself look ... simple and uneducated, not C look bad.

I have 2 generic servers in my closet that use Thunderbolt to talk to big ass arrays of disks. Nothing Apple related about them.

And USB 3 does not do everything I use Thunderbolt for on my Mac, including ferry USB3 over the same wire as video. I come home (or go to the office) and plug in my laptop with single cable and instantly my displays, USB3 devices, audio and networking all work ... without eating a ridiculous amount of CPU power as required by USB.

Dear god, do not drop Thunderbolt support based on the silly musings of a bunch of people buying the cheapest crap hardware they can possibly buy and then being pissy they don't have the same functionality. Fortunately Apple doesn't generally listen to a bunch of whiners on slashdot.

If you read the article, you'll find that the article is in fact NOT about anything like 1984. Its about properly mounting EXISTING CCTV camera's so they are useful. As in, mount them in such a way to get images of the faces of the people breaking into your house, not just shots of the top of their head which are useless to everyone.

The problem is that you think slashdot articles aren't sensationalist crap, when in fact they are by default and only become useful after people actually pay attention to the story rather than the nut job lying summary.

Chrome is by definition, spyware.

It does everything in its power to relay information about your activities back to Google, right down to what you click and when, if you allow it.

Most of these 'features' require you to opt-in, but some just happen right out of the box.

If you don't realize that the entire existence of Chrome and Chromium is to get information about you, you're an idiot with your head in the sand.

Chrome decided to use a recent feature THAT THE CHROME DEVS SUBMITTED TO THE KERNEL ... and isn't in any distribution that matters ... nor will it be for some time to come.

The issue is that unless your running a dev/unstable branch, you aren't going to have this kernel feature and you're not going to have it in stable/LTS versions ever ...

The application dropped support for production kernels ... because it wants a patch that isn't yet in production kernels.

Googles foot ... they just shot a hole in it, fuck'em.

He dislikes Chrome BECAUSE it IS SPYWARE in the strictest sense of the word. It does everything it can to relay your habits back to Google's servers. Some of that you can turn off, some of it you can't, but that doesn't change the fact that it is spyware.

I'm off the opinion Google can fork-off simply because they were able to survive without TSYNC and make it 'safe' but suddenly they can't and they refuse to deal with older kernels. Fork Google, this ridiculous bullshit of constantly having to update just because they can't be bothered to do real software development life cycles for user software. Fork'em right in the ear.

I don't use firefox because they want to update 10 times a month, I don't use Chrome now for the same sort of reasons. Chrome managed to make it not noticeable longer than firefox since the Chrome UI doesn't change daily like Firefox but none the less, too many problems have resulted due to Chrome constant releases that its no longer supported in my organization.