Why aren't these folks using Java? Remember write once, run everywhere? It's got an authentication mechanism, and the whole 'you can converse with the originating server' schtick seems to make it ideal.
Yes, if you RTFA you'll know the dots correspond to a map larger than the US.
What _I_ want to know is: Can I scan a page at reasonable resolution and have the laser printer crank out replacements? Then the paper costs about 3 cents a sheet.
If no, how long til we have a 12k app that generates a useful sequence that can be sent to a laser printer? (BTW, the pages look like they've got a roughtly 12% greyscale screen on them...)
"It was a dark and stormy night. My name is Jonny Wong. I'm employed at a company in Dongguan that makes the ~/` key for keyboards."
"We've been having problems with a competitor that makes Black ~/` keys. Ours are white or ivory. They're trying to muscle in on our buisiness, they want to take our 2/3rds of the market."
A Friend (not a FOAF, just a friend) worked for a company that wrote software for optimising the layout on ICs. The error they coded wasn't ever supposed to be encountered outside the development area, unfortunately the got a call from a customer asking what
"The hardware reliability isn't really the problem, it can be good enough, the issue is single box scalability."
I dunno, our current major project is running on an ES7000 (8 processors, fully redundant, running Windows Datacenter) It seems pretty beastly to me.
At the point here where X Unix implementation is x% faster than Y Microsoft implementation, the issue is decided by other factors. As long as either is fast enough to handle the load, n-th degree performance doesn't matter.
In out case, the company that won the contract specified the hardware, it was part of a total cost contract (you get one amount of money to make this work, work within those boundaries.)
_Presumably_ that company is happy enough with Windows performance on a 'big iron' box.
I think the big problem here is the tendency to DBify EVERYTHING POSSIBLE.
Like the State field in an online form.
Every single hit requires a tag to the databases. Why?
Because, heck if we ever get another state, it'll be easy to update! Ummm, that's a LOT of cycles used for something that hasn't happened in, what, 50 years or so. (Hawaii, 1959)
Building ADA compliant websites pull in some audiences that normally you wouldn't expect. If the font tags are properly coded, and the page devolves well if Style Sheets are turned off, you'd be surprised how your sites assist the elderly who can't see 12 pt text at 1600x1280, but can select a larger default font in thier browser.
Likewise, our major application (initial unemployment registration) can be accessed with an Ipaq IR connected to a nokia cellphone and works well (enough) at 9600 baud.
This thread may be too old for anybody to see this, but: Windows XP has a 'make bootable MSDOS' floppy option. I discovered it by accident as we're STILL using floppies at the office to kickstart multicasting OS downloads.
We're expecting to move the process ovr to bootable CDROMS but REALLY that's just an _image_ of a floppy with some additional storage we don't need. (All of the code, drivers, etc, fit on about 1.2mb of space) The OS image is about 1.5Gb, so you'd be swapping CD's if you wanted to do a non network rollout of the OS anyway.
I didn't say there WEREN'T issues. IIRC there was FUD saying embedded controllers in Fire Engines would think the oil hadn't been changed in 100+ years and would prevent the truck from running.
The fact that you never programmed the TIME into that embedded controller never seemed to occur to anybody.
Neither the Naval Observatory NOR the 105 year old folks had issues as a result of an _embedded_systems_ failure, which is what this thread is about.
Slashdot Mirror
To win back that initial 10 BILLION [pinky finger to lips] investment? $1 per Ghz?
$.01 per Ghz?
Why aren't these folks using Java? Remember write once, run everywhere? It's got an authentication mechanism, and the whole 'you can converse with the originating server' schtick seems to make it ideal.
So four companies merged to create United linux. I'm still confused as there's still Lycoris, Lindows, Mandrake, Redhat, etc.
In my PERSONAL experience in futzing with Lycoris, I went out and BOUGHT Redhat.
Redhat seems to suffer from Microsoftitis, that is, if it's a Un*x app, it's running on Redhat first.
Yes, if you RTFA you'll know the dots correspond to a map larger than the US.
What _I_ want to know is: Can I scan a page at reasonable resolution and have the laser printer crank out replacements? Then the paper costs about 3 cents a sheet.
If no, how long til we have a 12k app that generates a useful sequence that can be sent to a laser printer? (BTW, the pages look like they've got a roughtly 12% greyscale screen on them...)
John Katz! Is that you? :P
(waiting out the 20 second timer)
"It was a dark and stormy night. My name is Jonny Wong. I'm employed at a company in Dongguan that makes the ~/` key for keyboards."
"We've been having problems with a competitor that makes Black ~/` keys. Ours are white or ivory. They're trying to muscle in on our buisiness, they want to take our 2/3rds of the market."
A Friend (not a FOAF, just a friend) worked for a company that wrote software for optimising the layout on ICs. The error they coded wasn't ever supposed to be encountered outside the development area, unfortunately the got a call from a customer asking what
"Error: Wrong Gender, unable to have sex."
meant.
"The hardware reliability isn't really the problem, it can be good enough, the issue is single box scalability."
I dunno, our current major project is running on an ES7000 (8 processors, fully redundant, running Windows Datacenter) It seems pretty beastly to me.
At the point here where X Unix implementation is x% faster than Y Microsoft implementation, the issue is decided by other factors. As long as either is fast enough to handle the load, n-th degree performance doesn't matter.
In out case, the company that won the contract specified the hardware, it was part of a total cost contract (you get one amount of money to make this work, work within those boundaries.)
_Presumably_ that company is happy enough with Windows performance on a 'big iron' box.
I think the big problem here is the tendency to DBify EVERYTHING POSSIBLE.
Like the State field in an online form.
Every single hit requires a tag to the databases. Why?
Because, heck if we ever get another state, it'll be easy to update! Ummm, that's a LOT of cycles used for something that hasn't happened in, what, 50 years or so. (Hawaii, 1959)
Agreed on all points.
Anybody remember how their grandparents (or parents if they're 70-ish or older) handled things like refrigerators and in house electricity?
My grandparents would unplug their TV every night so that the electricity wouldn't 'leak out'.
are ugly?
{This space unintentionall left blank for the filters}
This Can't Possibly Be a Real Person
No one thinks this way
It's gotta be a 'bot of some sort.
Dude, you had me TOTALLY lost till you got to 'Bottom line -- don't buy one yet!'
Were you talking English?
"Those are going to replace CD's in a couple of years. Guess I'll have to buy the White album again" - Agent K
Building ADA compliant websites pull in some audiences that normally you wouldn't expect. If the font tags are properly coded, and the page devolves well if Style Sheets are turned off, you'd be surprised how your sites assist the elderly who can't see 12 pt text at 1600x1280, but can select a larger default font in thier browser.
Likewise, our major application (initial unemployment registration) can be accessed with an Ipaq IR connected to a nokia cellphone and works well (enough) at 9600 baud.
Yes®, it's® true®. I® like® the® Microsoft® Windows® XP® operating® system® enough® to® change® my® whole® computing® world® around®.
{Stuff deleted}
© 2002 Microsoft Corporation. All rights reserved.
This thread may be too old for anybody to see this, but: Windows XP has a 'make bootable MSDOS' floppy option. I discovered it by accident as we're STILL using floppies at the office to kickstart multicasting OS downloads.
We're expecting to move the process ovr to bootable CDROMS but REALLY that's just an _image_ of a floppy with some additional storage we don't need. (All of the code, drivers, etc, fit on about 1.2mb of space) The OS image is about 1.5Gb, so you'd be swapping CD's if you wanted to do a non network rollout of the OS anyway.
ROFLMAO! That's classic!
I predict a large company will make an existing product smaller, and double the number of features for 90% of the current price.
I also predict that 99% of the people that BUY that product will be unaware that those features exist and consequently not use them.
I preduct the people least likely to use those features will buy that product because 'It's pretty'.
I didn't say there WEREN'T issues. IIRC there was FUD saying embedded controllers in Fire Engines would think the oil hadn't been changed in 100+ years and would prevent the truck from running.
The fact that you never programmed the TIME into that embedded controller never seemed to occur to anybody.
Neither the Naval Observatory NOR the 105 year old folks had issues as a result of an _embedded_systems_ failure, which is what this thread is about.
I seem to remember hearing 'when {blah} happens to embedded systems, many things will be affected in subtle and BAD ways.'
Where {blah} = y2k, now {blah} = DRM
Now I'm entirely AGAINST what DRM stands for, but that particular comment won't win any supporters after Y2k used it up.
But still 3D digitally boob based:
My wife routinely kicks my butt at DOA3. And we both routinely pick the female characters as they're the most interesting.
More power than send all of mankind to outerspace dedicated to accurately rendering BoobDynamics(tm)
'Like VMS, better known as the Operating System of the Gods'
Dude. Have you USED VMS? [shudder.]
The 'set' command had, like _400_ different behaviors.
Anybody else see the irony in comparing THIS machine to the $199 Walmart/Lindows/AOL machine?
$199 to 'three or four thousand dollars' is quite the spread for two items that, at a certain level, are more alike than different.