I won't be buying it... in a "candybar" form instead of the more popular "flip phone" style
So how do people carry their flip phones? I went from a Nokia 3360 to a Moto V771 and it was always whacking into something when I had it on a belt clip, and always looked big and stupid when I carried it in a pocket. The hinge finally broke when I had it in my jeans and my daughter jumped on my lap, so I replaced it with a Nokia 3120. The Nokia is smaller, lighter and doesn't snag on random bits of furniture when I walk by. Maybe I just got a fat one, but I'm not likely to go back to a flip phone. Maybe one of these, though...
Re:Nice to have on the bookshelf...for a few of us
on
The New C Standard
·
· Score: 1, Funny
I imagine you'd have to cons up some sort of dual-port disk controller. Should be transparent to the TiVo, so no s/w changes.
Re:Yes, we were clustering when y'all were in napp
on
DECnet Isn't Dead
·
· Score: 1
The dual-processor 780 was the 782. Asymmetric multi-processing (only one CPU could do I/O, I believe). ISTR that the 785 was a 780 implemented entirely with CMOS parts (instead of the TTL used in the 780 and 750). I'm pretty fuzzy on the details of both of these, I haven't worked on a VAX since '94 or thereabouts. Still have my old architecture handbook and green card around somewhere, and my VMS 5.5 internals book.
Actually, the keyer is the device that actually generates the dots and dashes if you're using an iambic key (to keep the length and spacing even), and it can indeed be a single IC. FWIW, the current requirement is 5wpm for a General class license*, with no additional speed requirement for the higher class. There's talk that the FCC may drop the Morse code requirement (many other countries have), but probably not for awhile yet.
* Current licensing classes are Technician (access to allocated frequencies from 6M on up), General (access to most HF) and Amateur Extra (access to all allocated frequencies).
This is known as the "mammalian reflex", I believe. Basically, your body pumps the last of the oxygenated blood to the brain before the heart shuts down. When the person is revived, the brain immediately has a supply of oxygen-rich blood available. This effect apparently is much more pronounced in children than in older people, and AFAIK really only works in cold water.
Not quite -- I did a gig for these guys and they were building out new routes as quickly as they could (which, considering that they had to secure right-of-way and probably file environmental impact statements, wasn't nearly as fast as they would have liked). Believe it or not, the commercial rail industry is doing pretty well. In fact, one of their biggest problems is scheduling -- they're scrambling to build out their facilities and obtain more rolling stock. Intermodal (hauling semi-trailers) traffic is a big part of it, and given the price of diesel now, it's just going to get bigger.
Let's not forget that the hard disk has a buffer to isolate the latency, and likely uses prefetching to keep it full. I'd be interested in knowing if anything like that would help the thumb drive. Honestly, I rather doubt it, but I'm still curious as to what improvements could be made. Cycling through interleaved banks, some sort of simple data compression?
Actually, the core of OS X is Mach, which was developed at CMU starting in 1985. The Unix "personality" that runs on top of the microkernel is based on FreeBSD, which was itself based on 4.4BSD-Lite, which was released around 1993. Windows XP is based on NT, which was first released in 1992.
If you've ever worked with a real commercial OS (e.g. VMS), you'll roll your eyes whenever anyone mentions "security" and "Windows" without including the phrase "lack of"...
Location, probably. I was RIFfed when I was working in Oregon (Portland), and finding work as a Java developer back then (early 2002) was nearly impossible. Meanwhile, my cow-orkers back in Philadelphia were all re-employed within six weeks (and most within two). Now I'm living in the Midwest, and while I don't imagine I'll ever make the same salary I was making back East (pre-Dot Bomb), things are getting much better. I'm even getting cold calls from recruiters who have old copies of my resume, which hasn't happened for awhile.
Not true for unemployment. I was working for a company in Pennsylvania when I moved to Oregon. Six months later I got RIFfed and collected PA unemployment for five months, all over the phone. I set up direct deposit when I registered, and weekly filing was done via an IVR system. The only time I even spoke to a real person was during the initial call, and they just took the information I gave them, presumably verified it, and started issuing me checks.
Interestingly enough, I'm currently working on a project where we're rewriting the unemployment system in one of the flatter states. You can bet I'll be bringing up this article in our next staff meeting, and we'll see if our design needs to be changed (figures, something like this comes up two weeks after design reviews are over!)
How many n00bz actually believe this? It'd be pretty trivial to have a shutdown timer enable at system startup, then have the kernel call some non-Darwin code to disable the timer or change the interrupt vector to disable the shutdown. Replace this code with a vanilla Darwin and presto, machine shuts down 30secs after startup. Or you could have to do some challenge/response handshake with an onboard controller before you got to runlevel S. Lots of stuff that would be expensive to figure out and emulate, and with virtually everyone connected to the internet, who's to say they couldn't update the configuration occasionally?
That might be a solution if you've got the source. One of the more terrifying things learned during the great Y2K scare was that there exist a large number of legacy system that have been patched by directly modifying the binaries. Such systems have no source code anymore, and are not decompilable. Also, let's not forget that much of this code was probably written "oddly" to get another 2% worth of performance out of the original architecture; to do the job properly you'd have to rewrite the fiddly bits in a more standard fashion, then verify that you haven't: a) introduced any new bugs, and b) fixed any bugs the program was depending on. The second may be a non-issue in most cases, but the first is still a non-trivial exercise.
This sounds like the stuff that Tera was working on with their MTA back in the 90s (see this or for more techincal details here). Basically, a processor that could handle up to 128 threads at a time, with almost zero-latency switching among threads. These processors could be easily interconnected to scale up to whatever the customer (e.g., Sandia, Los Alamos, LLL) wanted. From perusing Cray's website, though, I don't see any current machines that appear to be using that architecture, so I assume it didn't play out somehow.
I doubt this will really be an issue, since the system will have to have some kind of unique identifier for each file, so there's no reason why you couldn't get at it.
The way I see it, you'll still organize your work in some sort of hierarchy (folder, directories, whatever), but you'll be able to attach additional information to it. I.e., I'll have my Java project in a standard development hierarchy, but I'll also be able to tag it as "Work" or "Personal", and if it's work-related I'll be able to additionally identify it by project, or by client. I also think that files should inherit any meta-data set for the hierarchy, so that if I have a (folder/directory/...) identified as "World Domination", then all the items within it should also be so identified. Then, if I decide that world domination requires lemon merangue pie instead of cream puffs, I can move my cream puff recipe and it will no longer show up as part of that group.
C#, Gtk+/Gnome, Linux Kernel, and X.org looks a lot more attractive to me
Hmmm, seems to me monolithic kernels were invented in the 60s, and wasn't Project Athena (X-windows) developed in the early 80s? I've heard Objective-C described as "Java without the cruft" and I've heard C# described as "Java with different syntax";) Oh, and Display PostScript (not 'Display PDF') was based on Sun's NeWS system, which came out in 1989, so DPS itself was developed during the 90s.
I think the technologies you deride were ahead of their time, and the technologies you espouse are popular due to their simplicity, not their elegance.
I believe that in the early days the need to optimize IO led to designs that made no allowance for transient filesystems.
When Unix was created, there really weren't transient file systems. You had *removable* disks, but changing a disk pack wasn't as simple as yanking a dongle, you had to take the drive offline and spin it down and wait for the heads to retract before you could unmount it. Tapes and the like were handled differently (you did remember that 'tar' stands for Tape ARchiver, didn't you?), they weren't mounted as file systems, just used as block devices. The chance that a drive would suddenly disappear with no warning and just as suddenly reappear was pretty remote.
Slashdot Mirror
I won't be buying it ... in a "candybar" form instead of the more popular "flip phone" style
So how do people carry their flip phones? I went from a Nokia 3360 to a Moto V771 and it was always whacking into something when I had it on a belt clip, and always looked big and stupid when I carried it in a pocket. The hinge finally broke when I had it in my jeans and my daughter jumped on my lap, so I replaced it with a Nokia 3120. The Nokia is smaller, lighter and doesn't snag on random bits of furniture when I walk by. Maybe I just got a fat one, but I'm not likely to go back to a flip phone. Maybe one of these, though...
where is the Karma Reset button
Around here that's known as a "trigger"...
I imagine you'd have to cons up some sort of dual-port disk controller. Should be transparent to the TiVo, so no s/w changes.
The dual-processor 780 was the 782. Asymmetric multi-processing (only one CPU could do I/O, I believe). ISTR that the 785 was a 780 implemented entirely with CMOS parts (instead of the TTL used in the 780 and 750). I'm pretty fuzzy on the details of both of these, I haven't worked on a VAX since '94 or thereabouts. Still have my old architecture handbook and green card around somewhere, and my VMS 5.5 internals book.
I doubt anyone is more "unparalleled" than Lockheed-Martin. The military-industrial complex just wouldn't be the same without them!
Actually, the keyer is the device that actually generates the dots and dashes if you're using an iambic key (to keep the length and spacing even), and it can indeed be a single IC. FWIW, the current requirement is 5wpm for a General class license*, with no additional speed requirement for the higher class. There's talk that the FCC may drop the Morse code requirement (many other countries have), but probably not for awhile yet.
* Current licensing classes are Technician (access to allocated frequencies from 6M on up), General (access to most HF) and Amateur Extra (access to all allocated frequencies).
This is known as the "mammalian reflex", I believe. Basically, your body pumps the last of the oxygenated blood to the brain before the heart shuts down. When the person is revived, the brain immediately has a supply of oxygen-rich blood available. This effect apparently is much more pronounced in children than in older people, and AFAIK really only works in cold water.
rails are still disappearing
Not quite -- I did a gig for these guys and they were building out new routes as quickly as they could (which, considering that they had to secure right-of-way and probably file environmental impact statements, wasn't nearly as fast as they would have liked). Believe it or not, the commercial rail industry is doing pretty well. In fact, one of their biggest problems is scheduling -- they're scrambling to build out their facilities and obtain more rolling stock. Intermodal (hauling semi-trailers) traffic is a big part of it, and given the price of diesel now, it's just going to get bigger.
That may be true for the TGV, but apparently not for the ICE train. When you derail at 200kph, things get grim.
BTW, we call them "trucks" in English, but I kind of like "wagons"....
Let's not forget that the hard disk has a buffer to isolate the latency, and likely uses prefetching to keep it full. I'd be interested in knowing if anything like that would help the thumb drive. Honestly, I rather doubt it, but I'm still curious as to what improvements could be made. Cycling through interleaved banks, some sort of simple data compression?
Actually, the core of OS X is Mach, which was developed at CMU starting in 1985. The Unix "personality" that runs on top of the microkernel is based on FreeBSD, which was itself based on 4.4BSD-Lite, which was released around 1993. Windows XP is based on NT, which was first released in 1992.
If you've ever worked with a real commercial OS (e.g. VMS), you'll roll your eyes whenever anyone mentions "security" and "Windows" without including the phrase "lack of"...
Your beer is so much heavier, you can only drink four or five. Over here, five pints of chilly piss^W^WCoors Light is just a warm-up!
Location, probably. I was RIFfed when I was working in Oregon (Portland), and finding work as a Java developer back then (early 2002) was nearly impossible. Meanwhile, my cow-orkers back in Philadelphia were all re-employed within six weeks (and most within two). Now I'm living in the Midwest, and while I don't imagine I'll ever make the same salary I was making back East (pre-Dot Bomb), things are getting much better. I'm even getting cold calls from recruiters who have old copies of my resume, which hasn't happened for awhile.
Not true for unemployment. I was working for a company in Pennsylvania when I moved to Oregon. Six months later I got RIFfed and collected PA unemployment for five months, all over the phone. I set up direct deposit when I registered, and weekly filing was done via an IVR system. The only time I even spoke to a real person was during the initial call, and they just took the information I gave them, presumably verified it, and started issuing me checks.
Interestingly enough, I'm currently working on a project where we're rewriting the unemployment system in one of the flatter states. You can bet I'll be bringing up this article in our next staff meeting, and we'll see if our design needs to be changed (figures, something like this comes up two weeks after design reviews are over!)
If so....PUSH THE BUTTON!
+1, Creepy
because of games (both PC and consoles) I've managed to a great amount of English
Sure you have, dude...sure you have.
Uranus...
Sorry, had to say it!
How many n00bz actually believe this? It'd be pretty trivial to have a shutdown timer enable at system startup, then have the kernel call some non-Darwin code to disable the timer or change the interrupt vector to disable the shutdown. Replace this code with a vanilla Darwin and presto, machine shuts down 30secs after startup. Or you could have to do some challenge/response handshake with an onboard controller before you got to runlevel S. Lots of stuff that would be expensive to figure out and emulate, and with virtually everyone connected to the internet, who's to say they couldn't update the configuration occasionally?
Personally, I find it hilarious that there's a standard anarchy symbol....
That might be a solution if you've got the source. One of the more terrifying things learned during the great Y2K scare was that there exist a large number of legacy system that have been patched by directly modifying the binaries. Such systems have no source code anymore, and are not decompilable. Also, let's not forget that much of this code was probably written "oddly" to get another 2% worth of performance out of the original architecture; to do the job properly you'd have to rewrite the fiddly bits in a more standard fashion, then verify that you haven't: a) introduced any new bugs, and b) fixed any bugs the program was depending on. The second may be a non-issue in most cases, but the first is still a non-trivial exercise.
This sounds like the stuff that Tera was working on with their MTA back in the 90s (see this or for more techincal details here). Basically, a processor that could handle up to 128 threads at a time, with almost zero-latency switching among threads. These processors could be easily interconnected to scale up to whatever the customer (e.g., Sandia, Los Alamos, LLL) wanted. From perusing Cray's website, though, I don't see any current machines that appear to be using that architecture, so I assume it didn't play out somehow.
I doubt this will really be an issue, since the system will have to have some kind of unique identifier for each file, so there's no reason why you couldn't get at it.
The way I see it, you'll still organize your work in some sort of hierarchy (folder, directories, whatever), but you'll be able to attach additional information to it. I.e., I'll have my Java project in a standard development hierarchy, but I'll also be able to tag it as "Work" or "Personal", and if it's work-related I'll be able to additionally identify it by project, or by client. I also think that files should inherit any meta-data set for the hierarchy, so that if I have a (folder/directory/...) identified as "World Domination", then all the items within it should also be so identified. Then, if I decide that world domination requires lemon merangue pie instead of cream puffs, I can move my cream puff recipe and it will no longer show up as part of that group.
C#, Gtk+/Gnome, Linux Kernel, and X.org looks a lot more attractive to me
;) Oh, and Display PostScript (not 'Display PDF') was based on Sun's NeWS system, which came out in 1989, so DPS itself was developed during the 90s.
Hmmm, seems to me monolithic kernels were invented in the 60s, and wasn't Project Athena (X-windows) developed in the early 80s? I've heard Objective-C described as "Java without the cruft" and I've heard C# described as "Java with different syntax"
I think the technologies you deride were ahead of their time, and the technologies you espouse are popular due to their simplicity, not their elegance.
I believe that in the early days the need to optimize IO led to designs that made no allowance for transient filesystems.
When Unix was created, there really weren't transient file systems. You had *removable* disks, but changing a disk pack wasn't as simple as yanking a dongle, you had to take the drive offline and spin it down and wait for the heads to retract before you could unmount it. Tapes and the like were handled differently (you did remember that 'tar' stands for Tape ARchiver, didn't you?), they weren't mounted as file systems, just used as block devices. The chance that a drive would suddenly disappear with no warning and just as suddenly reappear was pretty remote.