That's a pretty strong statement for something that works quite well in the real world. I'd argue that TCP works quite well for anything doing bulk data transfer given the constraints inherent in the system. TCP has no way of knowing for instance if packet loss is due to congestion or noisy links. It assumes the former because it is on the internet, but that's not always a good assumption (this is big on devices like mobile phones with web browsers). TCP is terrible for time sensitive data (streaming voice/video for instance), but that's why pretty much every streaming application uses UDP or something similar. Streaming applications can get away with that because they self regulate their transmit rate, whereas bulk data wants to fill up any available space in the pipe to get the data transferred as fast as possible. Slow start is a necessary evil in a world where you don't know what the link conditions are from the start and don't want to slam a bottlenecked router with a big opening dump of data.
TCP stream oriented model is also a godsend for application developers. Networking is hard enough without having to build your own application state control systems (which is what would happen if you tried to make TCP stateless) for every single connection. It would be a nightmare.
Those who don't understand TCP are doomed to reimplement it, badly.
The problem is that TCP self regulates and throttles itself back in the face of network congestion. UDP does not, it just blasts packets out as fast as you can feed it. Without some sort of flow control, you could disproportionally hurt TCP flows (which are trying to be good and throttling themselves back when they hit a bottleneck) by your big ugly UDP stream.
That said, the bottleneck for end users is typically the uplink on their last mile connection, so this probably won't bring the internet down or crash any ISPs, but it will make life worse for people sharing the connection.
Fun fact: The original implementations of TCP did not have flow control (it was on a test network after all). It did not take long for it to become apparent that flow control is a necessary feature. A few network meltdowns made the case quite well.
Wouldn't a better technology be something that can be built out of locally available materials with technology compact enough to fly there in a spacecraft? I'm not sure what it would be, but I'm guessing it probably won't include carbon nanotubes or anything like them unless we're talking about going there in 2080 or something.
I was under the impression that someone was given the crappy original and told to make it look nice. They then spent a bunch of hours meticulously touching it up (basically painting over her face with a portrait of her face) and making it look presentable.
To be honest, real people don't surround themselves with the flag, but the media doesn't report on real people, they report on crazy people who are frequently a little jingoistic.
Uh, because you tell it which set of IP addresses is your local subnet? Firewalls aren't magic, people have been using them for years and years now. In the worst case scenario, there's a port labeled "WAN" and it has the firewall. In fact that's how most home routers work already!
Not that I'm an Intel fanboy, but SPECmarks are hardly the first thing that come to mind when I think about "reliable unbiased metrics". In fact the term that usually comes to mind when people start quoting SPECmark numbers is "lie".
It really depends. A college degree is extremely useful for getting your foot in the door, but real life experience is even better. The problem of course is that your average 21 year old has no life experience, so without a degree he's SOL. For people who were already in the job market when the computer industry sprung up, it's a little different. I know a lot of the people I work with have completely unrelated degrees because IT type degrees just didn't exist back then.
The point is, if you're going to go into a high tech field and you don't already have some sort of in (like your father owns the company or you've been working closely with one of the developers on a side project for years or something), then a degree is probably going to be necessary for the HR folks to even give you a second glance. IMHO, degrees from fancy institutions are largely overrated unless you're trying to become a full partner in a high end legal firm or something like that. A generic 4 year degree from a reputable but inexpensive school (State U) is more than enough for most HR folks, and the people who do the actual hiring likely won't care that much where your degree is from, just so long as you know what you're doing.
That is a concern though, if your local school's program is terrible and you come away with no usable skills, then your degree is worthless. You'll never get past the second interview without considerable studying on your own (never a bad idea however). Once you build up a lot of marketable skills and a network of professionals then you won't need a degree, but that's almost impossible to do without first getting into the industry somehow.
My wife normally hates video games, but she really liked Boom Blox for the Wii. It's mostly nonviolent (there are some levels where you shoot baseballs at ghosts with a gun) and has a pretty good multiplayer mode. Some of the multiplayer is competitive, but there is also a good amount of it that is cooperative (although frequently that cooperative means taking turns). At the very least there are so many different game modes that if you run into something you don't like it's ok, just move on to the next mode.
I think the upshot is that the UI is better so you'll be more productive, but the multimedia stuff is still going to be hampered by the DRM crap Microsoft added to Vista. It doesn't matter if you're working with your own material in a DRM unencumbered format, the backend DRM stuff still runs regardless.
You could play Red Alert 3. It would have to be less painful than trying to get it to work over the internet. Stupid Westwood still using network code from 1998...
You say nobody uses laptops for games, but you clearly have not been to any college lan parties lately. This is clearly a luggable designed for gaming, not a commuter laptop. The battery life probably sucks and it no doubt weighs a ton, but even so it's a lot easier to carry around than a full tower and the game performance should be more than adequate. Sure it'll be obsolete real fast, but these kinds of laptops aren't meant for the budget minded consumer.
He probably works for one of those Ethernet card companies that still thinks Ring Buffers are some kind of amazing trade secret they have to protect lest other companies copy them.
I'm more shocked that you still need a driver for a PS/2 wheel mouse (I'm assuming it's not USB given the age). What the heck did they do that it needs special driver support?
I'm not surprised you have trouble with an 802.11 card. There are so many chipset variations for those things and they're revised so frequently that almost nobody bothers with driver support beyond what's on the CD in the box. This goes double if it's unusual in some way (USB, Compact Flash, Compact PCI, etc...). Just be glad you don't have a TV Tuner card.
It's not that the hardware manufacturers are developing for MacOS, it's just that they've been too lazy to port their drivers to Vista, especially for older hardware. I mean look at what happened to people who had SoundBlaster Live based cards (which still work fine and are considerably better than most built-in sound still). Compare that to Linux where the support for them is actively maintained to this day.
You should show him wall(1). There's always the ever useless finger(1) command as well.
If you really want to blow someone's mind, show them some of the more advanced vi tricks. I still contend to this day that it's impossible for any mere mortal to know all of the possible commands in vi.
To be fair, the Usenet was killed by the old truth that if you give the people a cheap broadcast mechanism, the first thing they'll do is try to put advertisements on it.
It has been said that prostitution is the oldest profession, but before they could be prostitutes they had to advertise their services.
It only compresses if you ask it to, and frankly, the results are usually less than impressive. From the manpage:
-C Requests compression of all data (including stdin, stdout,
stderr, and data for forwarded X11 and TCP connections). The
compression algorithm is the same used by gzip(1), and the
``level'' can be controlled by the CompressionLevel option for
protocol version 1. Compression is desirable on modem lines and
other slow connections, but will only slow down things on fast
networks. The default value can be set on a host-by-host basis
in the configuration files; see the Compression option.
Assuming the RNG is kind enough to provide you with one. Maybe I'd be more into it if there was a robust crafting system in the game, such that you could build yourself an inventory of useful (necessary) items for every contingency with the carcasses of the monsters you kill and common items. Then it would be a game where eventually you could learn enough tricks to have a reasonable chance of not being ganked by the RNG at some point on pretty much every playthrough.
I'm also not sure why the Nethack community considers it to be a cardinal sin to have savepoints. Certainly every other game developer in the world has realized that if you're going to put random deaths into the game, you should probably not make the death penalty as harsh as possible. It's not like noobs will be ascending right away, since there is so much prep work you need to do (hopefully before the RNG decides to stop generating food/edible monsters) before you'll stand a chance on the lower levels (not to mention the plains!).
Slashdot Mirror
That's a pretty strong statement for something that works quite well in the real world. I'd argue that TCP works quite well for anything doing bulk data transfer given the constraints inherent in the system. TCP has no way of knowing for instance if packet loss is due to congestion or noisy links. It assumes the former because it is on the internet, but that's not always a good assumption (this is big on devices like mobile phones with web browsers). TCP is terrible for time sensitive data (streaming voice/video for instance), but that's why pretty much every streaming application uses UDP or something similar. Streaming applications can get away with that because they self regulate their transmit rate, whereas bulk data wants to fill up any available space in the pipe to get the data transferred as fast as possible. Slow start is a necessary evil in a world where you don't know what the link conditions are from the start and don't want to slam a bottlenecked router with a big opening dump of data.
TCP stream oriented model is also a godsend for application developers. Networking is hard enough without having to build your own application state control systems (which is what would happen if you tried to make TCP stateless) for every single connection. It would be a nightmare.
Those who don't understand TCP are doomed to reimplement it, badly.
The problem is that TCP self regulates and throttles itself back in the face of network congestion. UDP does not, it just blasts packets out as fast as you can feed it. Without some sort of flow control, you could disproportionally hurt TCP flows (which are trying to be good and throttling themselves back when they hit a bottleneck) by your big ugly UDP stream.
That said, the bottleneck for end users is typically the uplink on their last mile connection, so this probably won't bring the internet down or crash any ISPs, but it will make life worse for people sharing the connection.
Fun fact: The original implementations of TCP did not have flow control (it was on a test network after all). It did not take long for it to become apparent that flow control is a necessary feature. A few network meltdowns made the case quite well.
Wouldn't a better technology be something that can be built out of locally available materials with technology compact enough to fly there in a spacecraft? I'm not sure what it would be, but I'm guessing it probably won't include carbon nanotubes or anything like them unless we're talking about going there in 2080 or something.
I was under the impression that someone was given the crappy original and told to make it look nice. They then spent a bunch of hours meticulously touching it up (basically painting over her face with a portrait of her face) and making it look presentable.
To be honest, real people don't surround themselves with the flag, but the media doesn't report on real people, they report on crazy people who are frequently a little jingoistic.
Certainly it would take all of the fun out of the thread to actually read the story and see the original photo.
Uh, because you tell it which set of IP addresses is your local subnet? Firewalls aren't magic, people have been using them for years and years now. In the worst case scenario, there's a port labeled "WAN" and it has the firewall. In fact that's how most home routers work already!
Not that I'm an Intel fanboy, but SPECmarks are hardly the first thing that come to mind when I think about "reliable unbiased metrics". In fact the term that usually comes to mind when people start quoting SPECmark numbers is "lie".
And I'm asking you not to be an ass. It appears that neither of us will go home happy.
Isn't supercatavation basically an extreme form of the same basic principal?
It really depends. A college degree is extremely useful for getting your foot in the door, but real life experience is even better. The problem of course is that your average 21 year old has no life experience, so without a degree he's SOL. For people who were already in the job market when the computer industry sprung up, it's a little different. I know a lot of the people I work with have completely unrelated degrees because IT type degrees just didn't exist back then.
The point is, if you're going to go into a high tech field and you don't already have some sort of in (like your father owns the company or you've been working closely with one of the developers on a side project for years or something), then a degree is probably going to be necessary for the HR folks to even give you a second glance. IMHO, degrees from fancy institutions are largely overrated unless you're trying to become a full partner in a high end legal firm or something like that. A generic 4 year degree from a reputable but inexpensive school (State U) is more than enough for most HR folks, and the people who do the actual hiring likely won't care that much where your degree is from, just so long as you know what you're doing.
That is a concern though, if your local school's program is terrible and you come away with no usable skills, then your degree is worthless. You'll never get past the second interview without considerable studying on your own (never a bad idea however). Once you build up a lot of marketable skills and a network of professionals then you won't need a degree, but that's almost impossible to do without first getting into the industry somehow.
My wife normally hates video games, but she really liked Boom Blox for the Wii. It's mostly nonviolent (there are some levels where you shoot baseballs at ghosts with a gun) and has a pretty good multiplayer mode. Some of the multiplayer is competitive, but there is also a good amount of it that is cooperative (although frequently that cooperative means taking turns). At the very least there are so many different game modes that if you run into something you don't like it's ok, just move on to the next mode.
I think the upshot is that the UI is better so you'll be more productive, but the multimedia stuff is still going to be hampered by the DRM crap Microsoft added to Vista. It doesn't matter if you're working with your own material in a DRM unencumbered format, the backend DRM stuff still runs regardless.
You could play Red Alert 3. It would have to be less painful than trying to get it to work over the internet. Stupid Westwood still using network code from 1998...
The adage is: Life follows the Onion.
You say nobody uses laptops for games, but you clearly have not been to any college lan parties lately. This is clearly a luggable designed for gaming, not a commuter laptop. The battery life probably sucks and it no doubt weighs a ton, but even so it's a lot easier to carry around than a full tower and the game performance should be more than adequate. Sure it'll be obsolete real fast, but these kinds of laptops aren't meant for the budget minded consumer.
He probably works for one of those Ethernet card companies that still thinks Ring Buffers are some kind of amazing trade secret they have to protect lest other companies copy them.
Because you won't pass on your genes?
I'm more shocked that you still need a driver for a PS/2 wheel mouse (I'm assuming it's not USB given the age). What the heck did they do that it needs special driver support?
I'm not surprised you have trouble with an 802.11 card. There are so many chipset variations for those things and they're revised so frequently that almost nobody bothers with driver support beyond what's on the CD in the box. This goes double if it's unusual in some way (USB, Compact Flash, Compact PCI, etc...). Just be glad you don't have a TV Tuner card.
It's not that the hardware manufacturers are developing for MacOS, it's just that they've been too lazy to port their drivers to Vista, especially for older hardware. I mean look at what happened to people who had SoundBlaster Live based cards (which still work fine and are considerably better than most built-in sound still). Compare that to Linux where the support for them is actively maintained to this day.
I guess I should have said "now useless". Carmack's .plan file hasn't been updated in how long?
I always use "w" to see who's logged in.
You should show him wall(1). There's always the ever useless finger(1) command as well.
If you really want to blow someone's mind, show them some of the more advanced vi tricks. I still contend to this day that it's impossible for any mere mortal to know all of the possible commands in vi.
To be fair, the Usenet was killed by the old truth that if you give the people a cheap broadcast mechanism, the first thing they'll do is try to put advertisements on it.
It has been said that prostitution is the oldest profession, but before they could be prostitutes they had to advertise their services.
Assuming the RNG is kind enough to provide you with one. Maybe I'd be more into it if there was a robust crafting system in the game, such that you could build yourself an inventory of useful (necessary) items for every contingency with the carcasses of the monsters you kill and common items. Then it would be a game where eventually you could learn enough tricks to have a reasonable chance of not being ganked by the RNG at some point on pretty much every playthrough.
I'm also not sure why the Nethack community considers it to be a cardinal sin to have savepoints. Certainly every other game developer in the world has realized that if you're going to put random deaths into the game, you should probably not make the death penalty as harsh as possible. It's not like noobs will be ascending right away, since there is so much prep work you need to do (hopefully before the RNG decides to stop generating food/edible monsters) before you'll stand a chance on the lower levels (not to mention the plains!).