Originally posted by: Cerb
Originally posted by: Terumo
If Apache is working, then it's a user problem. How has little servers and HTML anything to do with it?
If it was working how could it be a problem, unless something wrong with it in the first place.
Secondly, the largest server market is those little servers. Be it the gamer with his HL or UT clan server, to the mom and pop business selling trinkets.
Gotta agree with n0c on this one. CLI is easy, and sure as hell beats the M$ wizards. Configuring applications is easier when you can read and edit a flat text file, and use a simple, quick command line tool or three to reload it and then test changes. Long live BASh.
Flat files are a problem in itself, especially for system resources. Some geniuses thought that would be wonderful way to bypass the database problems with running a forum, but the idea was shot down quickly when the benefits vs. real performance were explained.
But that's another issue.
Cerb, the way you admin will change a lot when grandma will be doing your tasks with a GUI and a simple step-by-step guide. It will have to be a GUI, as history shows it's the best interface the general public accepts. You know about the Dell servers that have DRAC cards? Do you know how popular they are to sysadmins? Yeah, it's not just because it's a one stop shop of the essentials to run a server, it's because a sysadmin can do his business (even remotely), and get back to other business quickly.
KISS principle is more than a string command.
'End user servers' is a contradiction, too, Terumo. Want to elaborate on what on earth you're talking about, there?
When grandma's of the world can admin servers that are designed to automate general server admin tasks. It's when end users (server owners and/or operators) can run a server with the ease of a desktop. Bypassing the need for dedicated sysadmins, for the general server market and beyond.
System administration, as we know it now, in the future will go the way of the buggy whips. It has to be.
So wrap this up in context: multi browser platforms creates non standards which one source of compliance will not overcome -- no amount of crying and bashing will change the matter. Browsers by their very nature will specialize with new code for their audience. If the mass public wants blinking text, browser developers will offer it (even in W3C reads the Articles of War to web developers). Because of specialization there can't be a one standard to fit every browser, and because specialization make web designing a real time consuming chore, it maybe necessary to reserve resources to one browser that serves most of the market (which is what the program developers have to do too).
When the time comes when everyone is finally reading XML (or a new language), then compliance will be more uniform. That will not occur in the near future. So at this stage, to save resources, web designers may HAVE to make choices to pare down spent resources. It's understandable, and sometimes necessary.
BTW, I find it funny that purists seek one standard, meanwhile complain about MS, when the uniform nature of computer programs could only exist if there was a monolithic OS platform.

Can't have your cake and eat it too, without owning up the hypocrisy involved.
And for the server argument: GUIs are the only way the server environment will become user friendly to the masses, who in the future will be wanting their own servers for their own needs. It's just natural evolution for the masses to transcend the server market. And system administrators (like those Unix Ph.D's who once ran the IBM mainframes) will be left out, when grandma can do the same work with just a couple of clicks and a step-by-step guide that even 8 year-olds can understand.
It'll all has to be, because simplicity is the goal.