Microsoft's obsession with the name "Explorer" goes beyond their web browsers. The default shell (i.e. the GUI) is called "Explorer." The file bowser is called "Explorer." Their web browser (as you've mentioned) is called "Explorer."
This naming convention stems from the fact that each application stems from a single source, possibly within the kernel (or so I have been told). They are different views on the same thing.
I'm not exactly sure what this has to do with the chair... I'd imagine you're right about associating anything to do with the Internet to the word "Explorer" (and MS by secondary association, of course).
The cheese contains Sodium Caseinate, which is almost always (or so i understand) derived from dairy products. As a vegetarian who is too lazy to be vegan, I have looked into stuff like that. Very few "non-dairy" cheeses are actually fully non-dairy. Since I can't really imagine life without cheese, I'll stay an L-O Veggie (I love eggs, too;-) So, for me, this sounds like a really cool product, though I'd be concerned with the overabundance of nutrients in the thing. As long as you don't have one at every meal, though, it ought to be fine.
Well, it's really not that far from many major East-coast (U.S.) cities. Why, it's just a hop, skip and a jump from Buffalo, NY;-) Granted, it'd be a full days' drive away for me (Chicago), but it's just a (roughly) 2-hour flight away. Since air travel is relatively cheap, geographic location seems somewhat secondary, really. It's not like it's in Antarctica or something... Plus, I think it's a good thing to have the conference in a country that seems to have (relatively) progressive views on and polcies about security issues. While I'm not an expert on Canadian law, I'll bet it's better than the U.S.:-p
If I recall my Future Tech class correctly, a few cable-alternative services have been using MMDS for nearly 20 years. I'm pretty sure that Cleveland and New Orleans services still exist today. It was cheaper to set up MMDS towers than to string cable through an already-dense wire-line infrastructure, apparently. Are there other markets outside of the U.S. that currently make use of MMDS?
Still, it's very cool to have yet another fat pipe, especially since it's wireless. I'm just sort of puzzled that the article seems to be implying that MMDS is some sort of fantastic new invention. The Cisco tech's a novel use of the spectrum, granted, but the bandwidh's been there for a while; since the beginning of time if you want to be literal;-) Before I get myself into a cosmological debate, I'll just stop here.
Well, I've seen some people posting that Icecast isn't suitable for live streaming. Well, that's not true, 'cause that's what I do with it;-)
I have (or rather had; I graduated in June) set up a Linux server at a tiny college station to serve up web pages, mailing lists and an MP3 stream of their broadcast. I'd direct you to it, but the power is not too reliable in the area, so it's often down for long spans of time because the new admin is too busy(?) to walk over and switch it back on. I couldn't convince the exec board to shell out for an APS, unfortunately...
The server itself is not very beefy (and does not need to be, really). It's a Celeron 333a with 128 MB RAM running RedHat 6.0 (when it's running...). I have the station's broadcast jacked directly into the input of the soundcard (SB AWE64). I run Liveice at 32 kbps, 22khz 'cause it doesn't sound too 'underwater' at that rate. The CPU and memory loads are trivial. I had wmmon running on my desktop when I was working on the machine at school and barely noticed the CPU trace at the bottom of the CPU meter. The memory load looked to be about 10%, if that much. The site's never been very busy, so that could be a factor. For connectivity, I hang the server off of the campus network, which is fast ether to the Internet gateway, which I think is frame-relay (the admins were rather secretive about it).
So, basically Linux + IceCast + Celeron 333a + 128 MB RAM is plenty for me. If you have a huge amont of traffic, you may need more, but I'm betting (as other people have noted) that you'll saturate yr pipe before yr server starts to sweat.
> I run on a 450 MHz AMD-K6-2, > with the 3d-now! extensions (of course). I can > tell you from experience that the FFT that > Seti@Home uses routine on an AMD SUCKS. It takes > forever to do a single block of data, and I > calculated it would eventually take something > like 70 hours to complete the block. I was > disappointed.
Wow, 70 hours? I'm running SETI@Home on Linux with an AMD K6-2 450, and according to my handy tk-SETI@Home client, I am averaging 14 hours 55 minutes. Granted, that's not great, but it's not 70 hours, either. 'Course, it may have something to do with my Super7 100 MHz bus and 128 MB RAM, though I am pretty much in the dark as to how the client uses resources... Anyway, I just thought I'd throw in my.02 regarding performance.
Slashdot Mirror
Microsoft's obsession with the name "Explorer" goes beyond their web browsers. The default shell (i.e. the GUI) is called "Explorer." The file bowser is called "Explorer." Their web browser (as you've mentioned) is called "Explorer."
This naming convention stems from the fact that each application stems from a single source, possibly within the kernel (or so I have been told). They are different views on the same thing.
I'm not exactly sure what this has to do with the chair... I'd imagine you're right about associating anything to do with the Internet to the word "Explorer" (and MS by secondary association, of course).
So... There you have it.
-Chris
The cheese contains Sodium Caseinate, which is almost always (or so i understand) derived from dairy products. As a vegetarian who is too lazy to be vegan, I have looked into stuff like that. Very few "non-dairy" cheeses are actually fully non-dairy. Since I can't really imagine life without cheese, I'll stay an L-O Veggie (I love eggs, too ;-) So, for me, this sounds like a really cool product, though I'd be concerned with the overabundance of nutrients in the thing. As long as you don't have one at every meal, though, it ought to be fine.
Just picking nits,
-Chris
Well, it's really not that far from many major East-coast (U.S.) cities. Why, it's just a hop, skip and a jump from Buffalo, NY ;-) Granted, it'd be a full days' drive away for me (Chicago), but it's just a (roughly) 2-hour flight away. Since air travel is relatively cheap, geographic location seems somewhat secondary, really. It's not like it's in Antarctica or something... Plus, I think it's a good thing to have the conference in a country that seems to have (relatively) progressive views on and polcies about security issues. While I'm not an expert on Canadian law, I'll bet it's better than the U.S. :-p
-Chris
If I recall my Future Tech class correctly, a few cable-alternative services have been using MMDS for nearly 20 years. I'm pretty sure that Cleveland and New Orleans services still exist today. It was cheaper to set up MMDS towers than to string cable through an already-dense wire-line infrastructure, apparently. Are there other markets outside of the U.S. that currently make use of MMDS?
;-) Before I get myself into a cosmological debate, I'll just stop here.
Still, it's very cool to have yet another fat pipe, especially since it's wireless. I'm just sort of puzzled that the article seems to be implying that MMDS is some sort of fantastic new invention. The Cisco tech's a novel use of the spectrum, granted, but the bandwidh's been there for a while; since the beginning of time if you want to be literal
-Chris
Well, I've seen some people posting that Icecast isn't suitable for live streaming. Well, that's not true, 'cause that's what I do with it ;-)
I have (or rather had; I graduated in June) set up a Linux server at a tiny college station to serve up web pages, mailing lists and an MP3 stream of their broadcast. I'd direct you to it, but the power is not too reliable in the area, so it's often down for long spans of time because the new admin is too busy(?) to walk over and switch it back on. I couldn't convince the exec board to shell out for an APS, unfortunately...
The server itself is not very beefy (and does not need to be, really). It's a Celeron 333a with 128 MB RAM running RedHat 6.0 (when it's running...). I have the station's broadcast jacked directly into the input of the soundcard (SB AWE64). I run Liveice at 32 kbps, 22khz 'cause it doesn't sound too 'underwater' at that rate. The CPU and memory loads are trivial. I had wmmon running on my desktop when I was working on the machine at school and barely noticed the CPU trace at the bottom of the CPU meter. The memory load looked to be about 10%, if that much. The site's never been very busy, so that could be a factor. For connectivity, I hang the server off of the campus network, which is fast ether to the Internet gateway, which I think is frame-relay (the admins were rather secretive about it).
So, basically Linux + IceCast + Celeron 333a + 128 MB RAM is plenty for me. If you have a huge amont of traffic, you may need more, but I'm betting (as other people have noted) that you'll saturate yr pipe before yr server starts to sweat.
HTH,
-Chris
> I run on a 450 MHz AMD-K6-2,
.02 regarding performance.
> with the 3d-now! extensions (of course). I can
> tell you from experience that the FFT that
> Seti@Home uses routine on an AMD SUCKS. It takes
> forever to do a single block of data, and I
> calculated it would eventually take something
> like 70 hours to complete the block. I was
> disappointed.
Wow, 70 hours? I'm running SETI@Home on Linux with an AMD K6-2 450, and according to my handy tk-SETI@Home client, I am averaging 14 hours 55 minutes. Granted, that's not great, but it's not 70 hours, either. 'Course, it may have something to do with my Super7 100 MHz bus and 128 MB RAM, though I am pretty much in the dark as to how the client uses resources... Anyway, I just thought I'd throw in my
-Chris