The new year rolled in at 1262304000, Unix time that is. It’s a little hard to imagine that Unix is now more than 1.2 billion seconds old. Seems only yesterday that I was trying my first pipes and ...
The link What Every Programmer Should Know about Time was recently posted on DZone and was a highly popular link. It references the original Emil Mikulic post Time and What Programmers Should Know ...
[danjovic] came up with a nifty entry for our 2025 One-Hertz Challenge that lands somewhere between the categories of Ridiculous and Clockwork. It’s a clock that few hackers, if any, could read on ...
Picture this: it’s January 19th, 2038, at exactly 03:14:07 UTC. Somewhere in a data center, a Unix system quietly ticks over its internal clock counter one more time. But instead of moving forward to ...
I've been away from doing anything extensive in MySQL for almost 3 years now, having been using MS SQL Server almost exclusively. But I'm helping a friend redesign the DB for his site (PHP/MySQL) and ...
Hosted on MSN
The Unix Epochalypse might be sooner than you think
A stark warning about the upcoming Epochalypse, also known as the "Year 2038 problem," has come from the past, as National Museum Of Computing system restorers have discovered an unsetting issue while ...
When I work on real-time embedded systems and I want to do some quick measurements, I often use a logic analyzer to get a feeling for the time required to execute a function or a worker thread/process ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results