POSIX specifies leap seconds aren't included. POSIX also states that times are UTC. But it SPECIFICALLY says that leap seconds are not included. It doesn't say UT1. It says UTC, no leap seconds. And that's why man with one watch doesn't know what time it is.
Linux mostly follows POSIX but has the ability to include leap seconds if you want them. IIRC, NTP includes leap seconds (Which occasionally breaks both NTP and various OS kernels.)
One thing Google has never studied is whether or not there's a market for an ad-supported dildo. Increasingly, everything else they do is about equally as appealing.
Except no one seems to know the difference, and it's literally impossible to know an accurate time in a system involving more than one component. Accidentally make the adjustment twice and you're in as bad shape as if you hadn't made it in the first place. I E-mailed a developer about a piece of a spec that didn't specify and asked him if the time was GMT or UTC. His response was "What's the difference?" Not something you want to here from someone who maintains astronomical software. Other parts of the spec said "UTC" but they meant UTC in the POSIX sense of the word, without leap-seconds. Which isn't really UTC, now, is it?
There are better ways to achieve the same goal. Just publish the second-offset and make your adjustment explicitly when you have to. Then when someone comes along who has to maintain your system, they'll actually be able to tell.
As an aside, part of the leap-second resolution should involve finding the member of the POSIX committee responsible for that part of the POSIX spec and punching them in the forehead:-/
It'd just be an option when you compile the kernel. "NSA Backdoor: Enable this to install a back door in your kernel which the NSA can use to spy on you. [on][off]"
1) Install WIFI nodes covering the entire USA
2) Sell wireless SIP phones that connect to a massive VOIP server.
3) Profit.
Even if you only had service within city limits, you'd already be much more reliable than any cellular carrier I've ever tried. My android phone can run a SIP client and I've been kicking around the idea of just dropping the cellular contract and rolling my own solution with an asterisk server on a cloud service and a local wifi provider.
That's not what newspapers were about. Giving a eulogy while the subject is still coughing up blood is a bit unorthodox, but here we go! Newspapers were low-budget operations that spent as little as possible on everything while putting ad revenue in the pockets of their owners. Next to the restaurant industry, they were the least forward-looking group of people I've ever seen. They are actually very similar to the restaurant industry in a lot of ways; labor violations abound, they never spend money on anything they don't absolutely have to and they never, ever, EVER plan for the future. Saying that a Newspaper should have developed the media application of the future is about as ludicrous as saying that McDonald's should genetically engineer the bull of the future, except that McDonald's is actually more likely to do that.
There will still be reporters and the news sites that managed to adapt enough to survive in the Internet era, but I don't think there will be print papers for that much longer. I suspect Google will be the largest employer of reporters in the future, and that they'll somehow figure out how to outsource local news reporting. Google had the kind of vision to build the media platform of the future. Newspapers didn't.
You know you don't need to use that window manager, right? Just rip that shit out and install IceWM or Enlightenment or something. Configure them to launch the programs you use on a regular basis (Terminal, EMACS, Web Browser, IRC!) and you're set!
From what I can tell, Citrix is just a tool you use to see if your CIO is a dumbass and needs to be fired. (Hint: If he says you need to install it, the answer is "yes".) I'd be happy to retract this statement if anyone can point me to an actually usable installation of Citrix.
Well if they're monitoring all that shit, maybe you should just complain to THEM when Paypal freezes your account! "Hey guys, you have my entire payment history! Tell those guys to cough up my cash!"
Yup, pretty sure I'm going to end up in a dark room somewhere with *cough* Freedom cables hooked up to my testicles.
I'd rather drop $10 in an online tip jar of a band in Japan or Kenya than give it to some parasitical US music studio that will take the lion's share of the money for itself and use it to pursue a piracy jihad against its users if its profits don't make their numbers for the quarter. Sure a lot of those garage bands are complete crap, but at least they're doing it for the love of music. And even if their delivery is imperfect, sometimes their artistic vision more than makes up for their musical talents. So go ahead and kill the "professional music business." I'm sure we'll all have fun dancing on its grave, to music it would never have been able to imagine.
You guys ever think of scouring github for programmers? You can see their code in advance and contacting someone directly vs having some headhunter google their resume off the internet and shotgun it at you might save you a few grand. You might even find a guy or two who knows something about oo.
A while back I jokingly told a fellow skydiver I refused to fall slower than the top speed in my car. Average terminal velocity is 120 mph. Falling at 200mph would be kind of a bitch. I might be able to fall faster than the Ferrari if you pushed it out the back of the plane, though (Actually, that'd make an awesome Red Bull commercial...)
Like that scene from Airplane, they should just give you a gun if you don't have one when you check in at the gate. That'd make the whole process a lot easier...
Everyone's jumping on the lambda train! Choo Choo! You know what that means! Two years from now all code will be written with nothing but lambdas. All those programmers out there with a new hammer, looking for a nail and all. Don't get me wrong, I just posted up a bit of nitfy sorcery with the new C++11 ones that would have been a lot harder without them. I'm just not looking forward to maintaining any code written in the next couple years. If we actually did design reviews here, I'd have to demand that any usage of them be justified (Kind of like singletons a couple of years ago blah.)
Hah! My process thingy uses fork and network socket I/O, monitors the state of its child process and tells you how it died! It does everything you ever wanted a process thingy to do on windows! Good luck getting it to compile there! Heh heh heh.
Oh, hmm. I don't think I've actually written the process thingy up as a library yet. I probably should. It's a bit nicer than system(). Then all those bad programmers out there could do process_thingy("rm/tmp/some_file").wait() instead of system("rm/tmp/some_file"). That's a HUGE improvement. I'll add that to my to-do list for the weekend. Funnily enough I wanted exactly such a library a couple of jobs ago, but they were using Java for their application, and it's impossible to do this in Java without JNI. And my position is if you're using JNI in your java program, you've already defeated the reason you used java in the first place (Write once, run anywhere.) So you may as well use C for the entire project.
I DID write my socket thingy as a library though, and posted it as a repo on github. You just implement a class that takes its owner, a file descriptor and a sockaddr_in pointer as constructor parameters and overload operator() to do work against the the file descriptor. Mostly it's an academic exercise, but I'll be leveraging it to do some neat things in the coming weeks. It uses pthreads and network socket I/O. Good luck getting that to compile on windows (Maybe you can with cygwin *shrug*.) I don't actually compile any code up there though. It's mostly just up there to illustrate how to do something. Maybe one of these days when I've done enough libraries like that, I'll write a book.
Oh, yeah, and I don't do windows. I think that's what I was going to say right out the gate. Sorry about that. My bad.
Slashdot Mirror
Linux mostly follows POSIX but has the ability to include leap seconds if you want them. IIRC, NTP includes leap seconds (Which occasionally breaks both NTP and various OS kernels.)
One thing Google has never studied is whether or not there's a market for an ad-supported dildo. Increasingly, everything else they do is about equally as appealing.
Someone at Slaaaaate wants to have sex with a Robooooot!
NO DOWNSIDES, I SAID!
Just remember kids, if you REALLY work at it, one day you too could suck as much as that guy and get paid $25 million for it! It's the American Dream!
There are better ways to achieve the same goal. Just publish the second-offset and make your adjustment explicitly when you have to. Then when someone comes along who has to maintain your system, they'll actually be able to tell.
As an aside, part of the leap-second resolution should involve finding the member of the POSIX committee responsible for that part of the POSIX spec and punching them in the forehead :-/
It'd just be an option when you compile the kernel. "NSA Backdoor: Enable this to install a back door in your kernel which the NSA can use to spy on you. [on][off]"
2) Sell wireless SIP phones that connect to a massive VOIP server.
3) Profit.
Even if you only had service within city limits, you'd already be much more reliable than any cellular carrier I've ever tried. My android phone can run a SIP client and I've been kicking around the idea of just dropping the cellular contract and rolling my own solution with an asterisk server on a cloud service and a local wifi provider.
There will still be reporters and the news sites that managed to adapt enough to survive in the Internet era, but I don't think there will be print papers for that much longer. I suspect Google will be the largest employer of reporters in the future, and that they'll somehow figure out how to outsource local news reporting. Google had the kind of vision to build the media platform of the future. Newspapers didn't.
Couldn't they just solve this problem with some sort of "laser"?
You know you don't need to use that window manager, right? Just rip that shit out and install IceWM or Enlightenment or something. Configure them to launch the programs you use on a regular basis (Terminal, EMACS, Web Browser, IRC!) and you're set!
From what I can tell, Citrix is just a tool you use to see if your CIO is a dumbass and needs to be fired. (Hint: If he says you need to install it, the answer is "yes".) I'd be happy to retract this statement if anyone can point me to an actually usable installation of Citrix.
This is like a fight to the death between Justin Bieber and Miley Cyrus. No matter who loses, I win! *gets popcorn*
Schlake? Is that you?
They were... probably spying on the wrong internets at the time...
Yup, pretty sure I'm going to end up in a dark room somewhere with *cough* Freedom cables hooked up to my testicles.
I'm sure they'll bring this post up when they have me in a dark room with jumper cables hooked up to my testicles."Not so funny now, is it, bitch?"
I'd rather drop $10 in an online tip jar of a band in Japan or Kenya than give it to some parasitical US music studio that will take the lion's share of the money for itself and use it to pursue a piracy jihad against its users if its profits don't make their numbers for the quarter. Sure a lot of those garage bands are complete crap, but at least they're doing it for the love of music. And even if their delivery is imperfect, sometimes their artistic vision more than makes up for their musical talents. So go ahead and kill the "professional music business." I'm sure we'll all have fun dancing on its grave, to music it would never have been able to imagine.
Just introduce a random delay between 1 and 5 minutes for every trade that takes place. Problem solved. You're welcome. :-P
But you do need competent ones. Does your HR know the first thing about what makes a programmer "good", much less a "rock star"?
You guys ever think of scouring github for programmers? You can see their code in advance and contacting someone directly vs having some headhunter google their resume off the internet and shotgun it at you might save you a few grand. You might even find a guy or two who knows something about oo.
A while back I jokingly told a fellow skydiver I refused to fall slower than the top speed in my car. Average terminal velocity is 120 mph. Falling at 200mph would be kind of a bitch. I might be able to fall faster than the Ferrari if you pushed it out the back of the plane, though (Actually, that'd make an awesome Red Bull commercial...)
Like that scene from Airplane, they should just give you a gun if you don't have one when you check in at the gate. That'd make the whole process a lot easier...
Everyone's jumping on the lambda train! Choo Choo! You know what that means! Two years from now all code will be written with nothing but lambdas. All those programmers out there with a new hammer, looking for a nail and all. Don't get me wrong, I just posted up a bit of nitfy sorcery with the new C++11 ones that would have been a lot harder without them. I'm just not looking forward to maintaining any code written in the next couple years. If we actually did design reviews here, I'd have to demand that any usage of them be justified (Kind of like singletons a couple of years ago blah.)
Oh, hmm. I don't think I've actually written the process thingy up as a library yet. I probably should. It's a bit nicer than system(). Then all those bad programmers out there could do process_thingy("rm /tmp/some_file").wait() instead of system("rm /tmp/some_file"). That's a HUGE improvement. I'll add that to my to-do list for the weekend. Funnily enough I wanted exactly such a library a couple of jobs ago, but they were using Java for their application, and it's impossible to do this in Java without JNI. And my position is if you're using JNI in your java program, you've already defeated the reason you used java in the first place (Write once, run anywhere.) So you may as well use C for the entire project.
I DID write my socket thingy as a library though, and posted it as a repo on github. You just implement a class that takes its owner, a file descriptor and a sockaddr_in pointer as constructor parameters and overload operator() to do work against the the file descriptor. Mostly it's an academic exercise, but I'll be leveraging it to do some neat things in the coming weeks. It uses pthreads and network socket I/O. Good luck getting that to compile on windows (Maybe you can with cygwin *shrug*.) I don't actually compile any code up there though. It's mostly just up there to illustrate how to do something. Maybe one of these days when I've done enough libraries like that, I'll write a book.
Oh, yeah, and I don't do windows. I think that's what I was going to say right out the gate. Sorry about that. My bad.