Nope, I wasn't invited. It just happened to be one of the first to register after they opened up for registration. The funny thing, is that I didn't hurry through the registration form either, and I was surfing from across the Atlantic using a slow dial-up connection I was using those days. I had just dialed out using my 14400 BPS modem, and when I visited Slashdot which was my usual first stop, I just happened to see that they had started accepting registrations.
I once had to port some code from Win32 to Irix. The only catch was that the only available Irix box was located half way around the world, and was only reachable through a crippled telnet link with about two seconds latency, that went down roughly every five minutes. To make things worse, the Irix installation was pretty messed up, and leaving even vi unusable as a text editor.
So, what I was left with was porting the code one sed command at a time. Got the job done, but I'm not eager to do that again.
For C++, the best coding guidelines I've ever read is the proposed Boost
C++ Coding Guidelines. (The link points to an
old version in the boost CVS tree. To get an updated version you'd need to join the Boost Yahoo group and get it from the "Files" section of the group.
What I like about the guidelines is the well thought out rationales presented and its adherance to current C++ standards. After reading them, I wanted to follow the guidelines because I agreed with the rationale, rather than simply because the document said so.
Not exactly what your looking for, but the movie
Freedom
Downtime might be worth a look. It was created by the 2600 Magazine people, the same folks that were sued for hosting and linking to the DeCSS code as part of a news story they ran on their website.
It doesn't deal with the DeCSS case specifically, but covers the good old topics such as mighty state and corporate entities that repress of information, and harshly penalizes harmless people who figure stuff out.
When I use various calendar program, it often irks me that the calendar program needs to be
running for the alerts to be displayed.
It would be nice to have a calendar program that would use cron (which is a daemon to execute scheduled commands) as a backend for triggering scheduled alerts. The concept could be expanded further by making the calendar program useful as a nice graphical application for scheduling system administration tasks.
Well, I've got a couple of accounts under 1k. I could sell you one for $500. Interested?
Not interested...:-)
Seriously, I have no idea how I managed to grab #17, that time I by chance logged on using a 14.000 baud modem, connecting from across the atlantic.
I wasn't even trying to fill out the registration form quickly. I remember that form clearly. In those days it asked for a name instead of a nick. You can still see that a lot of people with low user ids use their real name instead of a nick.
Slashdot Mirror
Nope, I wasn't invited. It just happened to be one of the first to register after they opened up for registration. The funny thing, is that I didn't hurry through the registration form either, and I was surfing from across the Atlantic using a slow dial-up connection I was using those days. I had just dialed out using my 14400 BPS modem, and when I visited Slashdot which was my usual first stop, I just happened to see that they had started accepting registrations.
Wow, impressive.
I once had to port some code from Win32 to Irix. The only catch was that the only available Irix box was located half way around the world, and was only reachable through a crippled telnet link with about two seconds latency, that went down roughly every five minutes. To make things worse, the Irix installation was pretty messed up, and leaving even vi unusable as a text editor.
So, what I was left with was porting the code one sed command at a time. Got the job done, but I'm not eager to do that again.
What I like about the guidelines is the well thought out rationales presented and its adherance to current C++ standards. After reading them, I wanted to follow the guidelines because I agreed with the rationale, rather than simply because the document said so.
Not exactly what your looking for, but the movie Freedom Downtime might be worth a look. It was created by the 2600 Magazine people, the same folks that were sued for hosting and linking to the DeCSS code as part of a news story they ran on their website.
It doesn't deal with the DeCSS case specifically, but covers the good old topics such as mighty state and corporate entities that repress of information, and harshly penalizes harmless people who figure stuff out.
When I use various calendar program, it often irks me that the calendar program needs to be running for the alerts to be displayed.
It would be nice to have a calendar program that would use cron (which is a daemon to execute scheduled commands) as a backend for triggering scheduled alerts. The concept could be expanded further by making the calendar program useful as a nice graphical application for scheduling system administration tasks.
Not interested... :-)
Seriously, I have no idea how I managed to grab #17, that time I by chance logged on using a 14.000 baud modem, connecting from across the atlantic.
I wasn't even trying to fill out the registration form quickly. I remember that form clearly. In those days it asked for a name instead of a nick. You can still see that a lot of people with low user ids use their real name instead of a nick.
(And no, I'm not selling mine.)