I ask this as an honest question, just wondering if there's something I'm missing... why not a d10? Also, if you can reduce your alphabet to 20 letters (text is remarkably readable with w transmitted as uu, k and c collapsed, etc) you can avoid the modulus entirely. Just thoughts.
Also, do note that they always have refurbished keyboards in stock, it seems. I paid about $170 for a refurbished essential... I can type all day on this, while I max out in about an hour on a 'normal' or 'microsoft ergonomic' keyboard. Is it worth $300? Probably. But if you're a student, like I, you can pay a bit less.
Okay, let's rephrase. "What happens when I know of a BSD-licensed package which can save me and my company untold hours of time and work, that my company would approve of incorporating into it's product, and that I can't get to without bloody internet access?" Blocking the 'net is blocking any developer's greatest resource. MSDN is great, but until I can get ANYTHING I might EVER want on my hard drive, I need the net.
I normally have no more respect for slashdot moderation than anyone else... but dude, it's time to be scared when your development practices are modded as funny!
Which one of these things doesn't belong? "Clear Interrupt Flag" =?= CLI? Well, yes, there happens to be a CLI instruction on the 8088/x86 processors which CLears the Interrupt flag... but I don't think this counts as a formal acronym. It just came about because all the 'clear' instructions begin with CL.
The problem with mineral oil (/motor oil/unscented baby oil) is that, while it's non-conductive when pure, it's noticeably hydrophilic. Yes, I know we all think of oil and water not mixing, but if you leave a container of mineral oil exposed to the air for several days, the water content goes from effectively zero to about 0.2%, if my memory serves me correctly. Not a hell of a lot, but enough to scare me in terms of conduction and corrosiveness.
But keep in mind that, to the software, the raid partition looks like a single, linear file. So if the defrag program makes a file use, say, the 4-8th megabyte of 'disk' space, it's actually using the 2-4th megabyte of each real disk. (Of course, this is assuming simple striping, but a similar argument applies to raid 5.)
A lot of people have said that, if software vendors were to be held liable for security holes, open software would be up the creek. I'm not so sure about that... it seems like a reasonable form of liability would be the exact same liability my dry cleaner has, if they ruin my favorite shirt... as it says on the sign, liability limitted to 10x the price I paid for the product. Free (as in beer) software, then, is still worth exactly what you pay for it; and the developer does not have to worry about legal repercussions.
I believe he means that so many firewalls and such are blocking everything but 'kosher' HTTP. Even if I'm running HTTP over TCP/IP, it doesn't mean that I can also run My Own Protocol over TCP/IP... too often, these days, it's blocked somewhere down the line.
Actually, the AGP port spec does allow only one slot, as you say. (That's why AGP is a port, not a bus.) But it's very possible to design a computer with more than one AGP port, the same way you can design one with more than one serial port (or, for that matter, with more than one PCI bus... but let's not go into that.) No, no one that I know of is doing this yet, but I'm sure it will happen soon enough.
My picturebook, which is a perfect size other than the small monitor, weighs 2.2 lbs. The split (I have the monitor off right now for repairs, using a postal scale) is 1.4lbs body/0.8 lbs screen. So two screens, plus some attaching hinges, plus an extra battery, would weigh 1.4+0.8+0.8+0.2+0.6 = 3.8lbs... certainly not outrageous.
"Actually, screen size is not that important. If the resolution is there, you can always just sit closer."
I said that myself, when buying a picturebook. Admittedly, it's a great short-term solution. But the simple fact is that sitting too close to a monitor wears your eyes out faster; you get more tired reading characters.2" high than ones.4" high. High resolution small screens are great... but only for stuff like OSX, with resolution-independent graphics. And even then, they're still small screens.
That was a fast slashdotting. Anyway, I've had an idea like this for a while, although I imagine my desired monitor layout is kinda different. Years ago, I used to use a standard two-fold wallet; small, convenient, and good enough. Then, when I started getting too much junk for it, I switched to a trifold; even smaller cross section, though thicker; room for more cards; and just more convenient.
Basically, what I want is a trifold laptop. Currently, laptop size is limitted by screensize. (See the picturebook or libretto for proof.) With a trifold, you could have a laptop the size of the picturebook (2.2 lbs, 1024x480 screen) with/two/ screens that unfold, one on top of the other, giving you effectively 1024x960. Now, there would be no way to conceal the joint between the screens; this would be two monitors, not one large one that fold. But even so, it seems like a beautiful idea.
You're missing the obvious, if the goal is to make as much money as possible. If you're NASA, hold the lottery; get a few tens of millions of dollars. But RIG the lottery so a minion of yours wins; then have the 'winner' ALSO auction the ticket on ebay, and get a few more millions right there. To the end-purchaser, it's the same as just buying the ticket from NASA directly, but there's an extra profit-making step of scamming the whole country!
Having used JET somewhat extensively, I can say that Swing works beautifully in it... exactly as you'd expect, and at a reasonable speed, to boot. It doesn't make small applications, but it optimizes relatively heavily. There's more than hope: it's already there!
The meter is the length of the path travelled by light in vacuum during a time interval of 1/299 792 458 of a second.
Which is exactly the same as 'a fixed, integral number [namely 299_792_458] of wavelengths of light from a particular optical transition [a specific vibration of the cesium atom].' Basically, you missed a step of logic, and you're violently agreeing with the source.
While the use of the GART you mention (video chipsets with no onboard memory) really does suck, performance-wise, the GART itself is not useless. Most games today limit themselves to 16MB or so of textures, so that they run properly, without swapping to main memory, with a 32MB video card. However, if you want a game with 256MB of textures, say, you have three options.
1) Get a video card with 270+MB of memory. (Yeah, right.)
2) Snatch from main memory the portions of the texture you need. (This gets slow AND ugly if you use more than ~16MB in a single frame.)
3) Use the GART, take (less of) a performance hit, and just keep the textures in system memory.
This was the original purpose of the GART, and is still important.
Um... Java's great. Yeah, there's no buffer overflow. But the big problem with it is code like you just write. People say "ooh, it's all so easy in Java!" and write crap like that. Yay, you have no buffer exploits! Now how about that denial of service setup, where you always wait for the client to close the socket? Um, oops?
No, it's not fast enough. That's the point. If you place some faith in humanity,/every/ problem can be solved in constant time; that is, every problem we'll ever solve, in all of humanity's history, is solved in O(1) time, if we take the constant to be the lifetime of the universe. The point is, while asymptotic behaviour gives you some very good gut feel for how easy a problem is, it's not at all hard to come up with pathological problems where this simply isn't valid.
Seems like something like this would be a life-saver in the multicast arena. Currently, if you want to multicast something, and allow a client to pick up anywhere, you have to multicast a repeating loop, and allow the client to pick up anywhere in the loop, then detect (numbered sections, usually) when the loop has gone all the way around. With this method, most of the overhead of bookkeeping would be removed; or, rather, would be inherent in the protocol. For you and I, writing a chat room, it hardly makes a difference... but for a company like Akamai, or for huge mirror sites, this might be a big deal.
Slashdot Mirror
I ask this as an honest question, just wondering if there's something I'm missing... why not a d10? Also, if you can reduce your alphabet to 20 letters (text is remarkably readable with w transmitted as uu, k and c collapsed, etc) you can avoid the modulus entirely. Just thoughts.
Also, do note that they always have refurbished keyboards in stock, it seems. I paid about $170 for a refurbished essential... I can type all day on this, while I max out in about an hour on a 'normal' or 'microsoft ergonomic' keyboard. Is it worth $300? Probably. But if you're a student, like I, you can pay a bit less.
Okay, let's rephrase. "What happens when I know of a BSD-licensed package which can save me and my company untold hours of time and work, that my company would approve of incorporating into it's product, and that I can't get to without bloody internet access?" Blocking the 'net is blocking any developer's greatest resource. MSDN is great, but until I can get ANYTHING I might EVER want on my hard drive, I need the net.
And of course, META NAME="SLASHBOT" just sounds cool.
I normally have no more respect for slashdot moderation than anyone else... but dude, it's time to be scared when your development practices are modded as funny!
Yes. HP, Compaq.... those are the only two I've worked with that had >16GB of memory, but I'm sure everyone else has one too.
Windows NT Technology? Department of Redundancy Department?
Which one of these things doesn't belong? "Clear Interrupt Flag" =?= CLI? Well, yes, there happens to be a CLI instruction on the 8088/x86 processors which CLears the Interrupt flag... but I don't think this counts as a formal acronym. It just came about because all the 'clear' instructions begin with CL.
The problem with mineral oil (/motor oil/unscented baby oil) is that, while it's non-conductive when pure, it's noticeably hydrophilic. Yes, I know we all think of oil and water not mixing, but if you leave a container of mineral oil exposed to the air for several days, the water content goes from effectively zero to about 0.2%, if my memory serves me correctly. Not a hell of a lot, but enough to scare me in terms of conduction and corrosiveness.
Segway Human Transporter? http://www.satirewire.com/news/0112/sht.shtml
But keep in mind that, to the software, the raid partition looks like a single, linear file. So if the defrag program makes a file use, say, the 4-8th megabyte of 'disk' space, it's actually using the 2-4th megabyte of each real disk. (Of course, this is assuming simple striping, but a similar argument applies to raid 5.)
A lot of people have said that, if software vendors were to be held liable for security holes, open software would be up the creek. I'm not so sure about that... it seems like a reasonable form of liability would be the exact same liability my dry cleaner has, if they ruin my favorite shirt... as it says on the sign, liability limitted to 10x the price I paid for the product. Free (as in beer) software, then, is still worth exactly what you pay for it; and the developer does not have to worry about legal repercussions.
Compatability. Visual appeal. Simplicity. Content. www.addaon.com
I believe he means that so many firewalls and such are blocking everything but 'kosher' HTTP. Even if I'm running HTTP over TCP/IP, it doesn't mean that I can also run My Own Protocol over TCP/IP... too often, these days, it's blocked somewhere down the line.
Actually, the AGP port spec does allow only one slot, as you say. (That's why AGP is a port, not a bus.) But it's very possible to design a computer with more than one AGP port, the same way you can design one with more than one serial port (or, for that matter, with more than one PCI bus... but let's not go into that.) No, no one that I know of is doing this yet, but I'm sure it will happen soon enough.
My picturebook, which is a perfect size other than the small monitor, weighs 2.2 lbs. The split (I have the monitor off right now for repairs, using a postal scale) is 1.4lbs body/0.8 lbs screen. So two screens, plus some attaching hinges, plus an extra battery, would weigh 1.4+0.8+0.8+0.2+0.6 = 3.8lbs... certainly not outrageous.
"Actually, screen size is not that important. If the resolution is there, you can always just sit closer."
.2" high than ones .4" high. High resolution small screens are great... but only for stuff like OSX, with resolution-independent graphics. And even then, they're still small screens.
I said that myself, when buying a picturebook. Admittedly, it's a great short-term solution. But the simple fact is that sitting too close to a monitor wears your eyes out faster; you get more tired reading characters
That was a fast slashdotting. Anyway, I've had an idea like this for a while, although I imagine my desired monitor layout is kinda different. Years ago, I used to use a standard two-fold wallet; small, convenient, and good enough. Then, when I started getting too much junk for it, I switched to a trifold; even smaller cross section, though thicker; room for more cards; and just more convenient.
/two/ screens that unfold, one on top of the other, giving you effectively 1024x960. Now, there would be no way to conceal the joint between the screens; this would be two monitors, not one large one that fold. But even so, it seems like a beautiful idea.
Basically, what I want is a trifold laptop. Currently, laptop size is limitted by screensize. (See the picturebook or libretto for proof.) With a trifold, you could have a laptop the size of the picturebook (2.2 lbs, 1024x480 screen) with
Adam
You're missing the obvious, if the goal is to make as much money as possible. If you're NASA, hold the lottery; get a few tens of millions of dollars. But RIG the lottery so a minion of yours wins; then have the 'winner' ALSO auction the ticket on ebay, and get a few more millions right there. To the end-purchaser, it's the same as just buying the ticket from NASA directly, but there's an extra profit-making step of scamming the whole country!
Having used JET somewhat extensively, I can say that Swing works beautifully in it... exactly as you'd expect, and at a reasonable speed, to boot. It doesn't make small applications, but it optimizes relatively heavily. There's more than hope: it's already there!
The meter is the length of the path travelled by light in vacuum during a time interval of 1/299 792 458 of a second.
Which is exactly the same as 'a fixed, integral number [namely 299_792_458] of wavelengths of light from a particular optical transition [a specific vibration of the cesium atom].' Basically, you missed a step of logic, and you're violently agreeing with the source.
While the use of the GART you mention (video chipsets with no onboard memory) really does suck, performance-wise, the GART itself is not useless. Most games today limit themselves to 16MB or so of textures, so that they run properly, without swapping to main memory, with a 32MB video card. However, if you want a game with 256MB of textures, say, you have three options.
1) Get a video card with 270+MB of memory. (Yeah, right.)
2) Snatch from main memory the portions of the texture you need. (This gets slow AND ugly if you use more than ~16MB in a single frame.)
3) Use the GART, take (less of) a performance hit, and just keep the textures in system memory.
This was the original purpose of the GART, and is still important.
Um... Java's great. Yeah, there's no buffer overflow. But the big problem with it is code like you just write. People say "ooh, it's all so easy in Java!" and write crap like that. Yay, you have no buffer exploits! Now how about that denial of service setup, where you always wait for the client to close the socket? Um, oops?
"Fast enough?"
/every/ problem can be solved in constant time; that is, every problem we'll ever solve, in all of humanity's history, is solved in O(1) time, if we take the constant to be the lifetime of the universe. The point is, while asymptotic behaviour gives you some very good gut feel for how easy a problem is, it's not at all hard to come up with pathological problems where this simply isn't valid.
No, it's not fast enough. That's the point. If you place some faith in humanity,
"the transmitter can continually stream packets"
Seems like something like this would be a life-saver in the multicast arena. Currently, if you want to multicast something, and allow a client to pick up anywhere, you have to multicast a repeating loop, and allow the client to pick up anywhere in the loop, then detect (numbered sections, usually) when the loop has gone all the way around. With this method, most of the overhead of bookkeeping would be removed; or, rather, would be inherent in the protocol. For you and I, writing a chat room, it hardly makes a difference... but for a company like Akamai, or for huge mirror sites, this might be a big deal.