They're search quality IS slipping. I have to dig further into the results to find something useful. And for general queries, for get about it! General queries results are filled with spammer results on the first couple of pages.
Take a pinch of Standard Linux [linuxbase.org]
Wrap it up in Xen [cam.ac.uk]
Add a touch of SELinux [nsa.gov]
And a little bitty bit of Globus [globus.org]
Oh like a Sandboxed Platform [blogspot.com]
Oh Lordy, Lordy, mixed with Free and Open Source Code [freshmeat.net]
You know you lump it all together
And you get a lump of poorly integrated junk.
If you want examples of operating systems that help with gridding, check out Plan 9 from Bell Labs and it's sister project Inferno. Nice thing about Inferno is that it runs on Linux, Windows, Mac OS X, Plan 9, and on native hardware.
b/w is cheap, disk space is cheap, ram is cheap, cpu time is cheap, developer time well maybe not so much. If one is looking at a problem and the solution seems to be text files then non of your concerns are likely to a consideration. Engineering time and tool compatability are though.
Saying things like "hardware is cheap" leads to the performance problems of today. It's extremely bad thinking by a developer and leads to bad code.
There are plenty of areas where text files are fine but XML is not.
Never said you did but methinks someone has prematurely jumped on the XML bashing wagon. There are many problem domains where the _best_ solution isn't necessarily the most elegant or the most efficient one.
I think someone haphazardly jumped on the XML bandwagon after being sucked in by the media hype, never having actually looked at the "technology".
A general statement like "it makes sense to use XML when dealing with text files" is pure stupidity.
XML increases the data size which increases the time it takes to transfer, the disk space, and the memory space it uses. Further, XML parsers are rather slow.
"Very simple databases" and I'm guessing "very simple load".
Try comparing PostgreSQL and MySQL while doing concurrent SELECT's, INSERT's, and UPDATE's. PostgreSQL will be faster under high concurrent load as it does row locking instead of table locking.
PostgreSQL handles higher load than MySQL in general. Speed is usually pointless: It takes more time to run the PHP script or transfer the data back to the web client than it does to recall from the database.
NetBSD was the first open source OS to have IPv6 support. Yeah, "way out of date" IP stack.
NetBSD was the first open source OS to have USB support. Yeah, "way out of date" hardware support. Further, NetBSD allows for "Machine Independent" drivers, leading to portability far beyond other operating systems.
Not enough developers? You don't need a lot of developers. Code remains cleaner when only educated people submit features.
Unlike with other operating systems -- including FreeBSD, OpenBSD, and Linux -- NetBSD holds off on releasing features until they are stable. That's why there are few releases. This is a good thing.
It's one of the most secure operating systems in the world. Compare the NetBSD 1.6.2 security patch list to the OpenBSD 3.5 security patch list.
I assure you that's a bug, not a feature.
They're search quality IS slipping. I have to dig further into the results to find something useful. And for general queries, for get about it! General queries results are filled with spammer results on the first couple of pages.
Screw having libraries doing it. Have the publishers do it. Most books now a-days are written in an electronic form anyway.
... They'll be bought out by Google, of course! http://www.broom.org/epic/
Take a pinch of Standard Linux [linuxbase.org] Wrap it up in Xen [cam.ac.uk] Add a touch of SELinux [nsa.gov] And a little bitty bit of Globus [globus.org] Oh like a Sandboxed Platform [blogspot.com] Oh Lordy, Lordy, mixed with Free and Open Source Code [freshmeat.net] You know you lump it all together And you get a lump of poorly integrated junk.
Um, why do you want thread migration?
If you want examples of operating systems that help with gridding, check out Plan 9 from Bell Labs and it's sister project Inferno. Nice thing about Inferno is that it runs on Linux, Windows, Mac OS X, Plan 9, and on native hardware.
Well then, if you were to believe FuckedGoogle, Google is evil.
What defines evil?
Hmm... Apparently my JavaScript settings were too tight. Once I enabled a couple of things within Firefox, those features came alive.
... And why is this better than the normal web? I have to click more to find what I want and it's not in any greater detail than that of the web.
I completely admit most of my MySQL knowledge comes from the 3.x days.
b/w is cheap, disk space is cheap, ram is cheap, cpu time is cheap, developer time well maybe not so much. If one is looking at a problem and the solution seems to be text files then non of your concerns are likely to a consideration. Engineering time and tool compatability are though.
Saying things like "hardware is cheap" leads to the performance problems of today. It's extremely bad thinking by a developer and leads to bad code.
There are plenty of areas where text files are fine but XML is not.
Never said you did but methinks someone has prematurely jumped on the XML bashing wagon. There are many problem domains where the _best_ solution isn't necessarily the most elegant or the most efficient one.
I think someone haphazardly jumped on the XML bandwagon after being sucked in by the media hype, never having actually looked at the "technology".
A general statement like "it makes sense to use XML when dealing with text files" is pure stupidity.
XML increases the data size which increases the time it takes to transfer, the disk space, and the memory space it uses. Further, XML parsers are rather slow.
XML? I wouldn't.
"Very simple databases" and I'm guessing "very simple load". Try comparing PostgreSQL and MySQL while doing concurrent SELECT's, INSERT's, and UPDATE's. PostgreSQL will be faster under high concurrent load as it does row locking instead of table locking. PostgreSQL handles higher load than MySQL in general. Speed is usually pointless: It takes more time to run the PHP script or transfer the data back to the web client than it does to recall from the database.
Wrong on so many counts.
NetBSD was the first open source OS to have IPv6 support. Yeah, "way out of date" IP stack.
NetBSD was the first open source OS to have USB support. Yeah, "way out of date" hardware support. Further, NetBSD allows for "Machine Independent" drivers, leading to portability far beyond other operating systems.
Not enough developers? You don't need a lot of developers. Code remains cleaner when only educated people submit features.
Unlike with other operating systems -- including FreeBSD, OpenBSD, and Linux -- NetBSD holds off on releasing features until they are stable. That's why there are few releases. This is a good thing.
It's one of the most secure operating systems in the world. Compare the NetBSD 1.6.2 security patch list to the OpenBSD 3.5 security patch list.
Touché.
Adding it to your bookshelf does no good: You have to read it.
The books homepage, http://www-cs-faculty.stanford.edu/~knuth/taocp.ht ml offers the fascicle for download for free. http://www-cs-faculty.stanford.edu/~knuth/fasc1.ps .gz You can still get $2.56 for each bug found, I believe.
~ knuth/taocp.html ~ knuth/fasc1.ps.gz
Mirrors:
http://www-cs-faculty.stanford.edu.nyud.net:8090/
http://www-cs-faculty.stanford.edu.nyud.net:8090/
However, the open robots tend to be a little less user-friendly.
How long before I can take my blank iRobot, goto kidnappster.com, download Lucy Lui, and make out in a movie theater?
Also, if you wanted something interactive, try Dia.
It was created with Graphviz.
Those are far more expensive than popcorn.
Just because you say it doesn't make it so.