Sure it would. When it selected the 5-star category, the "next song" pointer would be null, so it would pick again. You wouldn't reset the groups until the last unplayed song was played. Which could suck, your tunage would start out strong and get progressively weaker as the party went on. Oh well, I never said it was a perfect solution, just that you could make it work!;)
A visitor from Seattle asked my how far I drove to work, and I answered is 28 miles. He looked horrifed, and asked how long it took. That answer is 35 minutes. His jaw dropped. (I don't have to park on the highway on the way to work.) Apparently this is unheard of in Seattle.
Yeah, I'm still getting used to this. I used to live near Philadelphia and work in Jersey. Total distance was some 22 miles, but I had to drive across the city, so travel time was around 1:15. Now I live in Lincoln, NE and when I was working in Omaha, my 70 mile trip used to take me ~55 minutes.
The like had never been done before, raising both the price and the expectation of failure
Actually, that isn't true. There are at least three other automated baggage-handling systems (at San Francisco, Munich, and Frankfurt). I think the biggest problem was the #1 project killer: a delivery date was dictated before any analysis or design work was done. Not to mention the fact that the airport had actually begun construction before the system was even fully specified (forcing the design to fit the established plans, instead of allowing flexibility in the plans to accomodate the new system).
I heard a rumor that Siemens (who built the Frankfurt system) was invited to bid on the Denver system, and quickly declined after reading the RFP.
meetings are to be abhorred by any sensible person
I'm with you on that, I strongly believe that any meeting over an hour long is one that the leader hasn't prepared for sufficiently. I also find that getting two or three people together and stepping outside for a moment generates better results than formal meetings.
I found it interesting that the author of the article described meetings as "cozy", and felt like he was getting away with something because he didn't have to work. That hardly speaks of a good work eithic, yet this person (apparently) went on to found a startup that got bought out by Yahoo.
I'd puzzle over this dichotomy, but I have work to do....
Instead of like IBM, who manufactured their own hardware and didn't lock it to any specific software, and who still enjoy a lion's share of the market they created...
As everyone knows: "Real programmers can write FORTRAN in any language". I'm currently working on a large project, and it's all monolithic Java. Everybody just creates an EJB for their part of the system and everything goes into a method in the EJB. Polymorphism? Can't do it -- parameter passing is done by stuffing everything into a hash table and passing the hash table, so all methods would have the same signature. Subclassing? Nah, just throw some declarations in a file and use Source->Generate Getters and Setters; voila, instant JavaBean, and there's your class. "Everybody knows" that "all business logic belongs in an EJB", including (apparently) input validation, range checking and other field-level sanity checks. I predict there's going to be some high-visibility tankage when this dog gets released.
Seriously, use whatever's appropriate for your shop. If you're writing something seriously big, I'd stick with Java or.NET since Java's made to scale and.NET's just a warmed-over Java...;) That's for ERP-scale systems (think SAP), though; if your app can be implemented with lots of mostly-autonomous servers (a la Google), then you should be able to use PHP or Python. Just make sure your base IPC structure is tight (database, message queues, whatever).
I think MSFT put some pressure on HP to drop this partnership
Now that they're moving towards just supporting Windows Server on Itanium (no more HP-UX on PA-RISC, Tru64 and VMS on Alpha, or NonStop), they've become Microsoft's bitch.
Like the hockey goalie said: "You think your job is tough? Every time I make a mistake, a red light flashes, a loud buzzer goes off, and 10,000 people BOO!"
Actually, IPv6 is happening all over, just not here. It's the protocol of choice in China, India, Japan -- just not the US. In ten years we'll probably be playing catch-up in that area. Or the rest of the world may move to IPv6 and cede the IPv4 landscape/address space to us. Wouldn't that be fine...
requirements: Land on the moon. Get back to Earth. Do it in a way that a human passenger will have a high probability of surviving the trip without irreparable physical harm
Ummm, you forgot step 1: achieve escape velocity. That's one of the trickier parts. You've got to figure out what kind of thrust you need, in order to get that you need to know how heavy your launch vehicle is, in order to calculate that you need to know what kind of propellant you're using, in order to know that you've got to know what kind of specific impulse you need, in order to know that you need to know what kind of thrust you need....
The application of even "basic technology ironed out in the last century" needs lots of research (even if you've got man-centuries of experience).
i'd imagine that could get lucrative with the whole "i have an ipod, now i want an apple computer" thing
Except the whole point of the grandparent post is that Apple should allow OS X to run on non-Apple hardware. If you've bought an iPod, you've already picked an Apple product over the competition, now they're betting you'll do it again.
Yeah, there's no comparison between the two, sorry if I implied that there was (beyond the fact that they're both machines I'd like to have). At first I wanted the Mini because it's small and quiet and ran OS X and treated Java apps as first-class citizens, but the more I thought about it the more I realized that what I really wanted was a new development box. Ergo, the Sun. It's not small and I doubt it's quiet (they haven't shipped mine yet, so I can't say), but it'll be a better fit for my needs. No iLife, though, which is one of the things I was looking forward to on the Mini.
Absolutely! I was all hot to get a Mini, but figured I'd have to spend close to US$800 to get one I consider "usable" (512+MB, WiFi). Ultimately I just ordered one of these, but I still might get one for my wife.
That's what they used back in Ye Olden Dayse. Basically, you had all your devices chained together on a wire, and ran a current (20-50mA) through it to represent ones and interrupted it for zeroes. ISTR the max speed was ~110 baud, but I really don't know. It was popular because it was pretty noise-tolerant, and required little circuitry to implement. And yes, translation between current-loop and RS-232 interfaces is a done deal.
We were doing bank processing on a S/370 and had jobs than ran 24/7 (back before we even had the phrase "24/7"). We upgraded to a new 3081 (basically a pair of S/370s in a single box). However, they couldn't install the disk controller (a separate box) until the next day, so what they did was to run cables over to the still-running S/370 and use it as the disk controller for a couple of days. Well, as they were pulling the cables, they somehow managed to snag the EPO (emergency power-off) line, and the entire server room (remember, this is two mainframes and a few dozen washing-machine size disk drives and their attendant power supplies) spun down within a few seconds. I can still hear the shift manager screaming "WHAT THE F*** JUST HAPPENED!?!?" from all the way down the hall...
I could seriously get behind this, if instead it were to include:
* Translate a 10-line HLL routine into assembler, hand-assemble it and punch it in using a hex keypad. * Write a simple filter using at least two pipes and at least one of sed/awk/perl. * Given a C struct definition and a hex dump, find a section of the dump that contains said struct.
I could go on, but that alone would probably give most skr1pt k1dd13s a heart attack...
somewhere near me there is likely someone who can communicate with other people around the world under pretty much any conditions short of a massive EMP
Lots of us even have that covered. I keep an old AN/GRC-19 set around "just in case". It's a military rig from the 60s that uses EMP-hard tubes. Output power is 100 watts, which is good for about 50 miles with a 15-foot whip antenna. Of course, I'll be scrounging car batteries left and right to operate it, since it draws some hefty amps, but since 95% of the cars on the road today won't survive an EMP, I don't think they'll be in short supply.
Well, when you consider that most of that code was driving custom TTL circuits for sound and video generation, and many games had not only custom (primitive) GPUs but multiple 8-bit processors, you can see why it's pretty hairy. Add in the fact that if you don't get all the timing right, you won't be faithful to the feel of the original game, and it isn't so hard to understand.
Out where I used to be from (Oregon), the main reason to home-school kids was to give them intense religious indoctrination, and little else. I once overheard a home-schooled girl who, when asked a simple history question (what was the Louisiana Purchase, I believe), stated "That's not in the Bible, I don't have to know that."
Sure, when you fry some custom IC... you're hosed.
As those of us who collect Tek scopes know too well... (you have an equal chance of getting a working all-tube (e.g., 545/547/647) model than a later 5000- or 7000-series, despite the fact that the former are some twenty years older than the latter).
That said, I just this past weekend saved the in-law's 15-year-old microwave. It was totally dead (no display, no interior light) and had no external breaker, but pop the case and there's a 125V 15W fuse on the PS board. Took about half a heartbeat to stick a meter on it and see it was failed. Ran down to Radio Shack and picked up a 4-pack for US$3.50, ran back and put everything back together and it works just fine. Total time: 40 minutes. Money saved: ~US$650 (current price of feature-equivalent convection microwave).
Slashdot Mirror
Heh, too bad they're all displayed on a 3" screen...
"Whoa, those babies are huge -- I think..."
(looks slantwise at cat occupying 90% of available desk space, recalls refilling food and water bowls before settling down to read /.)
Don't go there.
Sure it would. When it selected the 5-star category, the "next song" pointer would be null, so it would pick again. You wouldn't reset the groups until the last unplayed song was played. Which could suck, your tunage would start out strong and get progressively weaker as the party went on. Oh well, I never said it was a perfect solution, just that you could make it work! ;)
A visitor from Seattle asked my how far I drove to work, and I answered is 28 miles. He looked horrifed, and asked how long it took. That answer is 35 minutes. His jaw dropped. (I don't have to park on the highway on the way to work.) Apparently this is unheard of in Seattle.
Yeah, I'm still getting used to this. I used to live near Philadelphia and work in Jersey. Total distance was some 22 miles, but I had to drive across the city, so travel time was around 1:15. Now I live in Lincoln, NE and when I was working in Omaha, my 70 mile trip used to take me ~55 minutes.
The like had never been done before, raising both the price and the expectation of failure
Actually, that isn't true. There are at least three other automated baggage-handling systems (at San Francisco, Munich, and Frankfurt). I think the biggest problem was the #1 project killer: a delivery date was dictated before any analysis or design work was done. Not to mention the fact that the airport had actually begun construction before the system was even fully specified (forcing the design to fit the established plans, instead of allowing flexibility in the plans to accomodate the new system).
I heard a rumor that Siemens (who built the Frankfurt system) was invited to bid on the Denver system, and quickly declined after reading the RFP.
meetings are to be abhorred by any sensible person
I'm with you on that, I strongly believe that any meeting over an hour long is one that the leader hasn't prepared for sufficiently. I also find that getting two or three people together and stepping outside for a moment generates better results than formal meetings.
I found it interesting that the author of the article described meetings as "cozy", and felt like he was getting away with something because he didn't have to work. That hardly speaks of a good work eithic, yet this person (apparently) went on to found a startup that got bought out by Yahoo.
I'd puzzle over this dichotomy, but I have work to do....
Instead of like IBM, who manufactured their own hardware and didn't lock it to any specific software, and who still enjoy a lion's share of the market they created...
As everyone knows: "Real programmers can write FORTRAN in any language". I'm currently working on a large project, and it's all monolithic Java. Everybody just creates an EJB for their part of the system and everything goes into a method in the EJB. Polymorphism? Can't do it -- parameter passing is done by stuffing everything into a hash table and passing the hash table, so all methods would have the same signature. Subclassing? Nah, just throw some declarations in a file and use Source->Generate Getters and Setters; voila, instant JavaBean, and there's your class. "Everybody knows" that "all business logic belongs in an EJB", including (apparently) input validation, range checking and other field-level sanity checks. I predict there's going to be some high-visibility tankage when this dog gets released.
.NET since Java's made to scale and .NET's just a warmed-over Java...;) That's for ERP-scale systems (think SAP), though; if your app can be implemented with lots of mostly-autonomous servers (a la Google), then you should be able to use PHP or Python. Just make sure your base IPC structure is tight (database, message queues, whatever).
Seriously, use whatever's appropriate for your shop. If you're writing something seriously big, I'd stick with Java or
I think MSFT put some pressure on HP to drop this partnership
Now that they're moving towards just supporting Windows Server on Itanium (no more HP-UX on PA-RISC, Tru64 and VMS on Alpha, or NonStop), they've become Microsoft's bitch.
Like the hockey goalie said: "You think your job is tough? Every time I make a mistake, a red light flashes, a loud buzzer goes off, and 10,000 people BOO!"
IPv6 seems to never happen
Actually, IPv6 is happening all over, just not here. It's the protocol of choice in China, India, Japan -- just not the US. In ten years we'll probably be playing catch-up in that area. Or the rest of the world may move to IPv6 and cede the IPv4 landscape/address space to us. Wouldn't that be fine...
requirements: Land on the moon. Get back to Earth. Do it in a way that a human passenger will have a high probability of surviving the trip without irreparable physical harm
Ummm, you forgot step 1: achieve escape velocity. That's one of the trickier parts. You've got to figure out what kind of thrust you need, in order to get that you need to know how heavy your launch vehicle is, in order to calculate that you need to know what kind of propellant you're using, in order to know that you've got to know what kind of specific impulse you need, in order to know that you need to know what kind of thrust you need....
The application of even "basic technology ironed out in the last century" needs lots of research (even if you've got man-centuries of experience).
And my teeth have never been whiter!
i'd imagine that could get lucrative with the whole "i have an ipod, now i want an apple computer" thing
Except the whole point of the grandparent post is that Apple should allow OS X to run on non-Apple hardware. If you've bought an iPod, you've already picked an Apple product over the competition, now they're betting you'll do it again.
Yeah, there's no comparison between the two, sorry if I implied that there was (beyond the fact that they're both machines I'd like to have). At first I wanted the Mini because it's small and quiet and ran OS X and treated Java apps as first-class citizens, but the more I thought about it the more I realized that what I really wanted was a new development box. Ergo, the Sun. It's not small and I doubt it's quiet (they haven't shipped mine yet, so I can't say), but it'll be a better fit for my needs. No iLife, though, which is one of the things I was looking forward to on the Mini.
Absolutely! I was all hot to get a Mini, but figured I'd have to spend close to US$800 to get one I consider "usable" (512+MB, WiFi). Ultimately I just ordered one of these, but I still might get one for my wife.
MiniTrue, MiniPlenty and....MiniSciTech? Hmmm, that doesn't sound familiar...
That's what they used back in Ye Olden Dayse. Basically, you had all your devices chained together on a wire, and ran a current (20-50mA) through it to represent ones and interrupted it for zeroes. ISTR the max speed was ~110 baud, but I really don't know. It was popular because it was pretty noise-tolerant, and required little circuitry to implement. And yes, translation between current-loop and RS-232 interfaces is a done deal.
regular serial port
I think you misspelled "current-loop TTY interface".
Heh, reminds me of a story from Ye Olden Times...
We were doing bank processing on a S/370 and had jobs than ran 24/7 (back before we even had the phrase "24/7"). We upgraded to a new 3081 (basically a pair of S/370s in a single box). However, they couldn't install the disk controller (a separate box) until the next day, so what they did was to run cables over to the still-running S/370 and use it as the disk controller for a couple of days. Well, as they were pulling the cables, they somehow managed to snag the EPO (emergency power-off) line, and the entire server room (remember, this is two mainframes and a few dozen washing-machine size disk drives and their attendant power supplies) spun down within a few seconds. I can still hear the shift manager screaming "WHAT THE F*** JUST HAPPENED!?!?" from all the way down the hall...
I could seriously get behind this, if instead it were to include:
* Translate a 10-line HLL routine into assembler, hand-assemble it and punch it in using a hex keypad.
* Write a simple filter using at least two pipes and at least one of sed/awk/perl.
* Given a C struct definition and a hex dump, find a section of the dump that contains said struct.
I could go on, but that alone would probably give most skr1pt k1dd13s a heart attack...
somewhere near me there is likely someone who can communicate with other people around the world under pretty much any conditions short of a massive EMP
Lots of us even have that covered. I keep an old AN/GRC-19 set around "just in case". It's a military rig from the 60s that uses EMP-hard tubes. Output power is 100 watts, which is good for about 50 miles with a 15-foot whip antenna. Of course, I'll be scrounging car batteries left and right to operate it, since it draws some hefty amps, but since 95% of the cars on the road today won't survive an EMP, I don't think they'll be in short supply.
Well, when you consider that most of that code was driving custom TTL circuits for sound and video generation, and many games had not only custom (primitive) GPUs but multiple 8-bit processors, you can see why it's pretty hairy. Add in the fact that if you don't get all the timing right, you won't be faithful to the feel of the original game, and it isn't so hard to understand.
Out where I used to be from (Oregon), the main reason to home-school kids was to give them intense religious indoctrination, and little else. I once overheard a home-schooled girl who, when asked a simple history question (what was the Louisiana Purchase, I believe), stated "That's not in the Bible, I don't have to know that."
Chilling.
Sure, when you fry some custom IC ... you're hosed.
As those of us who collect Tek scopes know too well... (you have an equal chance of getting a working all-tube (e.g., 545/547/647) model than a later 5000- or 7000-series, despite the fact that the former are some twenty years older than the latter).
That said, I just this past weekend saved the in-law's 15-year-old microwave. It was totally dead (no display, no interior light) and had no external breaker, but pop the case and there's a 125V 15W fuse on the PS board. Took about half a heartbeat to stick a meter on it and see it was failed. Ran down to Radio Shack and picked up a 4-pack for US$3.50, ran back and put everything back together and it works just fine. Total time: 40 minutes. Money saved: ~US$650 (current price of feature-equivalent convection microwave).