If you had paid attention in shell class and Taco Bell -- you would know that the Taco Bell ingredients are great for quickly passing through your pipeline.
Just - try to pipe it through tail instead of head.
> Really, all this focus on faster Javascript puzzles me. JS, used correctly, should be a thin layer of glue
Right, because Google Maps is just glued-together images.
This dynamic crap must stop! Keep Google Maps and similar applications OUT of the browser. Create windows-only binaries instead. And for the people who don't want windows-only binaries, Google can make a giant JPG at max resolution with a picture of the entire planet on it available. I'm sure the Linux users would be happy with that.
Even thought the boxes stay checked I have had to go to my user preferences and turn on and then back off the new comment system several times in the last two weeks.
Shit, I thought that I was the only person that happened to. I even had to log out/in to get the preference change to "stick".
But if that is the case, how is it possible for anyone to not get any beer? (i.e. the "system" works for the poorest just as it does for the richest, all he has to do is take advantage of it: i.e. get an education , work hard, etc.)
What the OP forgot to mention is that the rich guy drinks German beer, the guys in the middle drink Canadian beer, and the guys drinking for free get American beer.
Years ago, I worked as the service manager in a high-volume white-box PC shop. I was in charge of the guys who built boxes, the guys who troubleshot them, the guys who supplied inventory, and the guys who had to ship the parts back to the wholesaler for RMA.
Building 1000 boxes is six man-months worth of work, minimum. You need to figure in a 2% failure rate on finished machines, so you need to order parts for at least 1020 finished machines; you should also figure in a 3% failure rate during the build, so order enough parts for 1051 boxes. When the builds are done, RMA the bad parts and keep everything around for in-house spares.
Don't buy white-box based on warranty, because the warranty is useless after 90 days or so. You'll probably have to send the part back, it will get swapped with one that's been "fixed" and sent back to you. Half the time, that means you'll get one that somebody else returned and wholesaler's tech can't replicate the problem with, so he sends it to you, hoping you'll be okay.
As for building 1000 boxes at once, the way to do it is in partnership with a wholesaler. You'll need to rent some real estate, about 3000 square feet. Nothing dusty, and no carpets. You can probably get it cheap for 30-45 days, look for stuff that's been for sale/lease for a while. Hire 8 guys for a month who "like computers". Have the wholesaler ship you a tractor-trailer full of parts. Get a bunch of locked cabinets, lock all the RAM, CPUs, harddrives up. Stack the motherboards in a locked room. Stack the cases in a corner. Your 8 guys can unload a 40' trailer, count the parts, and put them away in ~12-14 hours.
Every morning, each guy who shows up gets his parts for the day. A low-output worker can build five boxes. A high-output worker can build 10. No drills allowed unless they have clutches. At the end of the day, they can demonstrate a working machine running windows, and start your burn-in suite. The next morning, for every box that passes burn-in, you give them $25. Then they pack the machine back up in the box the case came in, stack it in the room slated for deliveries.
Parts can be swapped 1:1, don't allow floating parts on the floor or they will never get put in a machine. Also, only allow clear garbage bags on the floor. No food or drink, either.
Oh - the reason for so much real estate? The most productive way to build machines is to use about 4 feet of table each, and to do them all at once. So, if you're building eight boxes that day, you need 32 feet of table. And 8 mice, 8 keyboards, and 8 monitors. Don't unbox mice/monitors/keyboards for your build, it will cost you time and not increase your reliability.
Make sure you provision these 1000 identical machines with removable HDD trays. That way, when one fails, you rip the drive out, stick it in a spare, and send that machine to be either fixed or pitched. Fixing might be expensive, though. Remember your assembly crew? They're long gone, and probably not very good technicians.
- Rogers may only cover 9% of Canada by area, but they cover 94% of the populated land mass
- How many towers is "very few"? Where I live, a city of 160,000, there are at least four. You can find hard info on Industry Canada's web site.
- CDMA coverage for large, flat provinces can be done with fewer towers than GSM, provided they are not very busy. GSM uses time-division multiplexing, and has a fixed-width field describing the radio-propagation delay. This gives a hard limit on range that is separate from radio power.
What would you do if the user said, "But I WANT to send malware?"
That's not so different from this case. T-Mobile didn't have a problem with the data, they had a problem with the control channel usage.
Imagine if, all of a sudden, a bunch of your clients started saturating their ports with connections that only sent one byte and then shut them down, or something similar. And I don't mean one byte at the TCP/IP layer, I mean at the PPPoE layer that required a new CHAP or RADIUS session or whatever per byte.
THAT is a lot more analogous to this problem than something that is well-behaved but high-volume (e.g. Bit-Torrent)
I bet a LOT of ISPs would be in trouble if one of their POPs had suddenly started banging their RADIUS server at 1200% of previous usage overnight.
ISPs also have the luxury of just "buying more". It's possible, for example, for an ISP to buy more transit, or a new uplink. It's just not possible for cellular companies to buy more spectrum in the general case. In this specific circumstance, they had to go back to the hardware vendor to get the firmware redesigned to work better with this new workload without using any more spectrum.
> and enough rooted Androids with an ingenious Taliban created app that it > would seem they would have enough easily accessible tools to carry out an > effective paralyzing terror attack in say D.C.?
You don't need rooted Android phones for this. Any number of EV boards have been on the market for a few hundred dollars for years which could do this.
The only reason the terrorists haven't done this yet is that they are still trying to figure out how to get their toenail clippers and bottled water on the airliner for the trip to Washington.
Yeah, you'd better opt for the OTHER network, you know, the one with great 3G coverage across the country with an network that is completely invulnerable to DOS attacks.
Okay, so I didn't check his math, but are you suggesting that both Canada and Germany require approximately the same number of cell towers per capita in order to maintain the same coverage?
Because if you are, you might, ah, want to look at map. Canada is slightly larger.
> And it's hardly his fault that Linux sucks on laptops.
And really, why do laptops even have to be workstations?
What I need in a laptop is a portable terminal, and these days a portable web browser. When I go laptop shopping, I type on them to see if they keyboard's any good, make sure it has USB ports, at least a couple gigs of RAM, built-in WiFi and away I go. I don't have enough spare time to install and configure an alternate operating system just to satisfy some stupid fanboi ego trip, I use whatever it comes with. Which of course is Windows.
Hm, I just realized the above isn't strictly true with my current laptop any more. I'm accidentally getting Windows-ownership benefits in the form of one those cellular modem doohickeys I picked up in a hurry one day when I was on the road and needed net access while moving. I don't know if it will work on Linux or not, but it sure as hell didn't come with Linux drivers.
It has crossed my mind more than once. I lamented the lack of "F5, Reveal Codes" from WordPerfect 5.1 when I finally had to make the jump to Word in the late 90s. I jumped because everybody else was using it and I had to collaborate on documents. At first, Word wasn't so bad, because I could run Word 6 under WABI on my Sun Workstation. (BTW, it was fast and reliable). Then everybody switched to Word '95, and I finally switched to Word '97.
I've stopped having to collaborate on documents, but I'm really effecient on Word '97, I've been using it long enough that I know where most of their stupidity is hidden, and can even "flow" a document so that it still "works" if I insert text near the beginning. The secret is Format->Paragraph->Keep Lines Together, or ->Keep With Next Line. The other secret is using styles properly. They are actually a lot like CSS, and, for example, you can rig it so that your heading classes stick to your paragraphs and so on.
> If you write long technical documents it is well worth the effort to learn LaTeX. > pdflatex can import PNG, JPEG, EPS and PDF graphics.
How about medium-sized bullshit documents that absolutely have to look pretty as they are intended for consumption by morons with MBAs?
I'm >< this close to springing for an MS Office license for my Mac.
I frequently need to take documents home from work, work on them, and send them back to work, work on them the next day, etc.
Without fail, OOo screws up my documents. Header/Footers are AFU, continued bullets don't, bullet styles change, general document styles change, page breaks become section breaks, Visio-4 inserts become ugly, etc, ad nauseum. It's gotten so bad I sometimes just stay late at the office to avoid going home to OOo.
It's really quite frustrating.
And it's not like I'm living on the bleeding edge of MS-land, either. I bought an Office '97 license, and rather like the product. It is snappy as hell on modern hardware, and does everything I need.
I want to like, OOo, really, I do, but, man, it just does NOT interoperate with my current work flow - and I don't want to have give up Word-97 just to be able to use OOo.
Slashdot Mirror
> The very top chefs and cooks will use 5-8 ingredients at the most to make dishes
Curry, rice, chicken, oil, salt.
That's eight, and boring!
If you had paid attention in shell class and Taco Bell -- you would know that the Taco Bell ingredients are great for quickly passing through your pipeline.
Just - try to pipe it through tail instead of head.
DOM bindings for bytecode would mean defining bytecode, and then, to a large part them implementation.
Did you know that Chrome compiles right from the AST to machine language?
Standardized bytecode in the browser was tried one already, in 1999. It was called "Java".
With the current state of the art, using JavaScript at as intermediate language is not a bad gig. Google Gears does this.
Bah, a 100 tabs is nothing.
I am currently working on a patch for Chromium that lets me run firefox tabs in a window, so that I can have more than one web page per process.
Chrome really sucks because I start running out of processes around 32,000 tabs.
> Really, all this focus on faster Javascript puzzles me. JS, used correctly, should be a thin layer of glue
Right, because Google Maps is just glued-together images.
This dynamic crap must stop! Keep Google Maps and similar applications OUT of the browser. Create windows-only binaries instead. And for the people who don't want windows-only binaries, Google can make a giant JPG at max resolution with a picture of the entire planet on it available. I'm sure the Linux users would be happy with that.
I hate the new comments system, too.
Shit, I thought that I was the only person that happened to. I even had to log out/in to get the preference change to "stick".
They are in charge of making sure the missiles don't accidentally hit Santa Claus.
What the OP forgot to mention is that the rich guy drinks German beer, the guys in the middle drink Canadian beer, and the guys drinking for free get American beer.
Yeah, I know I just pissed off, like, 99.999% of the /. readingship, but this solution works like a G-D charm.
Or at least, I assume it does. Because I tell my iPhone that my Google-Apps domain is really an MS-exchange server, and THAT works perfectly.
I just realized my schedule must be really evill, I rely on Google, Apple and Microsoft(protocols) to get it to me.
The funny part is, soap bubbles are made from soap, not detergents.
They are completely different at a chemical level.
..but I wouldn't want to.
Years ago, I worked as the service manager in a high-volume white-box PC shop. I was in charge of the guys who built boxes, the guys who troubleshot them, the guys who supplied inventory, and the guys who had to ship the parts back to the wholesaler for RMA.
Building 1000 boxes is six man-months worth of work, minimum. You need to figure in a 2% failure rate on finished machines, so you need to order parts for at least 1020 finished machines; you should also figure in a 3% failure rate during the build, so order enough parts for 1051 boxes. When the builds are done, RMA the bad parts and keep everything around for in-house spares.
Don't buy white-box based on warranty, because the warranty is useless after 90 days or so. You'll probably have to send the part back, it will get swapped with one that's been "fixed" and sent back to you. Half the time, that means you'll get one that somebody else returned and wholesaler's tech can't replicate the problem with, so he sends it to you, hoping you'll be okay.
As for building 1000 boxes at once, the way to do it is in partnership with a wholesaler. You'll need to rent some real estate, about 3000 square feet. Nothing dusty, and no carpets. You can probably get it cheap for 30-45 days, look for stuff that's been for sale/lease for a while. Hire 8 guys for a month who "like computers". Have the wholesaler ship you a tractor-trailer full of parts. Get a bunch of locked cabinets, lock all the RAM, CPUs, harddrives up. Stack the motherboards in a locked room. Stack the cases in a corner. Your 8 guys can unload a 40' trailer, count the parts, and put them away in ~12-14 hours.
Every morning, each guy who shows up gets his parts for the day. A low-output worker can build five boxes. A high-output worker can build 10. No drills allowed unless they have clutches. At the end of the day, they can demonstrate a working machine running windows, and start your burn-in suite. The next morning, for every box that passes burn-in, you give them $25. Then they pack the machine back up in the box the case came in, stack it in the room slated for deliveries.
Parts can be swapped 1:1, don't allow floating parts on the floor or they will never get put in a machine. Also, only allow clear garbage bags on the floor. No food or drink, either.
Oh - the reason for so much real estate? The most productive way to build machines is to use about 4 feet of table each, and to do them all at once. So, if you're building eight boxes that day, you need 32 feet of table. And 8 mice, 8 keyboards, and 8 monitors. Don't unbox mice/monitors/keyboards for your build, it will cost you time and not increase your reliability.
Make sure you provision these 1000 identical machines with removable HDD trays. That way, when one fails, you rip the drive out, stick it in a spare, and send that machine to be either fixed or pitched. Fixing might be expensive, though. Remember your assembly crew? They're long gone, and probably not very good technicians.
> or from vegans and other super ecofriendly people.
Vegans are not particularly ecofriendly people. I release as much CH4 consuming vegans as any other mammal by weight.
- Rogers may only cover 9% of Canada by area, but they cover 94% of the populated land mass
- How many towers is "very few"? Where I live, a city of 160,000, there are at least four. You can find hard info on Industry Canada's web site.
- CDMA coverage for large, flat provinces can be done with fewer towers than GSM, provided they are not very busy. GSM uses time-division multiplexing, and has a fixed-width field describing the radio-propagation delay. This gives a hard limit on range that is separate from radio power.
What would you do if the user said, "But I WANT to send malware?"
That's not so different from this case. T-Mobile didn't have a problem with the data, they had a problem with the control channel usage.
Imagine if, all of a sudden, a bunch of your clients started saturating their ports with connections that only sent one byte and then shut them down, or something similar. And I don't mean one byte at the TCP/IP layer, I mean at the PPPoE layer that required a new CHAP or RADIUS session or whatever per byte.
THAT is a lot more analogous to this problem than something that is well-behaved but high-volume (e.g. Bit-Torrent)
I bet a LOT of ISPs would be in trouble if one of their POPs had suddenly started banging their RADIUS server at 1200% of previous usage overnight.
ISPs also have the luxury of just "buying more". It's possible, for example, for an ISP to buy more transit, or a new uplink. It's just not possible for cellular companies to buy more spectrum in the general case. In this specific circumstance, they had to go back to the hardware vendor to get the firmware redesigned to work better with this new workload without using any more spectrum.
> and enough rooted Androids with an ingenious Taliban created app that it
> would seem they would have enough easily accessible tools to carry out an
> effective paralyzing terror attack in say D.C.?
You don't need rooted Android phones for this. Any number of EV boards have been on the market for a few hundred dollars for years which could do this.
The only reason the terrorists haven't done this yet is that they are still trying to figure out how to get their toenail clippers and bottled water on the airliner for the trip to Washington.
Yeah, you'd better opt for the OTHER network, you know, the one with great 3G coverage across the country with an network that is completely invulnerable to DOS attacks.
HA HA HA HAHA HAHA
I feel like Kang.
Okay, so I didn't check his math, but are you suggesting that both Canada and Germany require approximately the same number of cell towers per capita in order to maintain the same coverage?
Because if you are, you might, ah, want to look at map. Canada is slightly larger.
This sounds like something out of a mother's-basement-dweller's worst nightmare!
> And it's hardly his fault that Linux sucks on laptops.
And really, why do laptops even have to be workstations?
What I need in a laptop is a portable terminal, and these days a portable web browser. When I go laptop shopping, I type on them to see if they keyboard's any good, make sure it has USB ports, at least a couple gigs of RAM, built-in WiFi and away I go. I don't have enough spare time to install and configure an alternate operating system just to satisfy some stupid fanboi ego trip, I use whatever it comes with. Which of course is Windows.
Hm, I just realized the above isn't strictly true with my current laptop any more. I'm accidentally getting Windows-ownership benefits in the form of one those cellular modem doohickeys I picked up in a hurry one day when I was on the road and needed net access while moving. I don't know if it will work on Linux or not, but it sure as hell didn't come with Linux drivers.
So, you're saying that C programmers have a rubber soul, and C++ programmers have revolvers?
> I switched to LaTeX.
It has crossed my mind more than once. I lamented the lack of "F5, Reveal Codes" from WordPerfect 5.1 when I finally had to make the jump to Word in the late 90s. I jumped because everybody else was using it and I had to collaborate on documents. At first, Word wasn't so bad, because I could run Word 6 under WABI on my Sun Workstation. (BTW, it was fast and reliable). Then everybody switched to Word '95, and I finally switched to Word '97.
I've stopped having to collaborate on documents, but I'm really effecient on Word '97, I've been using it long enough that I know where most of their stupidity is hidden, and can even "flow" a document so that it still "works" if I insert text near the beginning. The secret is Format->Paragraph->Keep Lines Together, or ->Keep With Next Line. The other secret is using styles properly. They are actually a lot like CSS, and, for example, you can rig it so that your heading classes stick to your paragraphs and so on.
> If you write long technical documents it is well worth the effort to learn LaTeX.
> pdflatex can import PNG, JPEG, EPS and PDF graphics.
How about medium-sized bullshit documents that absolutely have to look pretty as they are intended for consumption by morons with MBAs?
I'm >< this close to springing for an MS Office license for my Mac.
I frequently need to take documents home from work, work on them, and send them back to work, work on them the next day, etc.
Without fail, OOo screws up my documents. Header/Footers are AFU, continued bullets don't, bullet styles change, general document styles change, page breaks become section breaks, Visio-4 inserts become ugly, etc, ad nauseum. It's gotten so bad I sometimes just stay late at the office to avoid going home to OOo.
It's really quite frustrating.
And it's not like I'm living on the bleeding edge of MS-land, either. I bought an Office '97 license, and rather like the product. It is snappy as hell on modern hardware, and does everything I need.
I want to like, OOo, really, I do, but, man, it just does NOT interoperate with my current work flow - and I don't want to have give up Word-97 just to be able to use OOo.
Maybe WINE is the answer?
I actually noticed this recently, on the train.
I was trying to figure out who the hell had a "Public Wifi Hotspot" network with uninterrupted coverage the whole way.
I guess now I know :P
I wonder why I didn't notice that it was an ad-hoc network (Vista UI)? Maybe because I didn't try to connect?
> The gasoline engine will never even start up
I hope they made the fuel injectors easy to access and clean.
I bet in 2-3 years we'll find avid Volters who try to hit the highway for the first time in eons years, only to find their fuel has turned to honey.
These hybrid cars should probably be diesel oil instead of gasoline powered, although diesel fuel still requires stabilization for long-term storage.
> I WELCOME YOU DEAF CATS!
OMG! We have no time to survive! Make our time!