This is definitely the path to real expandability and much like the path "real" sites take. Also, make as many a.ftp.host sites as possible. It is then always possible to direct 10 or 20 of them to the same server by dns, but also to transparently split apart the ones that are overloaded later.
If your budget is really tight then load as much disk as convienent on each server, make them cheap linux or BSD servers, and base the node size on whats cheap in HDs these days. Organize your directory structure so one tree contains all data from each named server (atree/ and btree/ if a & b are on the same physical server) so you can split easily by node. and all the CGI et cetera on the local servers, so you can only slow it down a bit.
On another note, a typical thing to do is professors.host (who have fewer procs usually, but therefore get better response times) nongeeks.host and a.cs.host b.cs.host so that the cs users can get angry at each other for bringing down a server, whle the nongeeks who'll be more likely to think it is your fault won't have problems. On a similar note, if your setup allows easy user migration, you could disallow cgi on most servers, allowing it only by permission (and migrating that user, then.)
Possibly they meant do away with the necessity of the keyboard... I doubt they're going to be totally getting rid of it soon... possibly in the ibook, but not in the powerbook. You can still put a disk drive in the powerbook.
Most of the comments I've glanced over are angled at someone buying MacOS X as a server... for which it will probably start out inferior, esp for price. Rarely does linux work as well out of the box as a Mac, but that's not the point.
The point is that for users who 1) don't enjoy (even if they're good at it) taking apart their computers and 2) who's time is worth a decent penny should generally buy a mac. Often, they actually do buy a mac. I bought a PC because I was poor, with money, I'd buy a mac.
For these people, who are most of mac users, X should be a godsend in terms of speed and reliability. The beauty of everyone who buys the best low-end workstation (mac) automatically getting a *nix system underneath, is amazing to me. This should blow everything else away... and no argument I can see except stigyness would make someone buy something else...
I've heard not too long ago that there was still a brisk trade in Apple IIs for schools that still had Apple II based systems. I am personally (slightly) involved in a project that actually ships Apple IIe's around the US, because that's cheaper than hiring a programmer to redo the app.
Slashdot Mirror
I stopped her outside and took several digital pics of her :) Several others were pretty impressive, too.
This is definitely the path to real expandability and much like the path "real" sites take. Also, make as many a.ftp.host sites as possible. It is then always possible to direct 10 or 20 of them to the same server by dns, but also to transparently split apart the ones that are overloaded later.
If your budget is really tight then load as much disk as convienent on each server, make them cheap linux or BSD servers, and base the node size on whats cheap in HDs these days. Organize your directory structure so one tree contains all data from each named server (atree/ and btree/ if a & b are on the same physical server) so you can split easily by node. and all the CGI et cetera on the local servers, so you can only slow it down a bit.
On another note, a typical thing to do is professors.host (who have fewer procs usually, but therefore get better response times) nongeeks.host and a.cs.host b.cs.host so that the cs users can get angry at each other for bringing down a server, whle the nongeeks who'll be more likely to think it is your fault won't have problems. On a similar note, if your setup allows easy user migration, you could disallow cgi on most servers, allowing it only by permission (and migrating that user, then.)
Plus, I really like their music.
Possibly they meant do away with the necessity of the keyboard... I doubt they're going to be totally getting rid of it soon... possibly in the ibook, but not in the powerbook. You can still put a disk drive in the powerbook.
Most of the comments I've glanced over are angled at someone buying MacOS X as a server... for which it will probably start out inferior, esp for price. Rarely does linux work as well out of the box as a Mac, but that's not the point.
The point is that for users who 1) don't enjoy (even if they're good at it) taking apart their computers and 2) who's time is worth a decent penny should generally buy a mac. Often, they actually do buy a mac. I bought a PC because I was poor, with money, I'd buy a mac.
For these people, who are most of mac users, X should be a godsend in terms of speed and reliability. The beauty of everyone who buys the best low-end workstation (mac) automatically getting a *nix system underneath, is amazing to me. This should blow everything else away... and no argument I can see except stigyness would make someone buy something else...
many happy fnords -
Arete
I've heard not too long ago that there was still a brisk trade in Apple IIs for schools that still had Apple II based systems. I am personally (slightly) involved in a project that actually ships Apple IIe's around the US, because that's cheaper than hiring a programmer to redo the app.
(well, it's only like 5 of them, but still.)