The future of computing? We can only hope ...

[Andyistic]

This is what I want to see:

Anyone who is in charge of operating a computer system (i.e. home user,
administrator, etc.) should be required to learn how to program in C++ and
Intel-AMD assembly.
(Please note: "x86" is no longer being used as a CPU identifier as Intel
dropped it when they came out with the Core 2 series. AMD hasn't used "x86"
in ages. Where is Cyrix?)

Having this programming ability, they should have access to the specs and
algorithms needed to code any drivers which may be needed by the hardware
their computers use.
They need to be able to compile a skeleton OS from a do-it-yourself kit
(i.e. Linux From Scratch) and add the required drivers and modules without
having to rely on code packages from any other source.
Of course, such packages, like shells, would still be available if the
programmer didn't have time to create his/her own.

What I'm really saying is that we should choose the hardware we want to use,
then create an OS with our chosen features to accomodate such hardware.
We shouldn't have to choose the OS first, then hope the hardware we have
works with it.
What would it take to get hardware manufacturers to release the device specs
to the public without fear of infringement?

-- Andy

 

[Jimmy Brush]

That would effictively take us back to the "stone age" of computing, where
this is in fact what had to be done.

Not that I personally would mind, as the "system administrator" you defined
would be able to charge an arm and a leg for such services, as individuals
with the required talent set would be extremely hard to find.

- JB

Vista Support FAQ
http://www.jimmah.com/vista/

 

[CH]

Andy I appreciate the info. Your lofty goal is admirable. I wish I had
programming skills. Not everyone had the chance to learn programs while we
were in formal education programs, and many of us feel that in addition to
the advantages you lobby for, that we would have more insight into the many
ideas we have for features and architecture in Vista, the Longhorn server
line, and other software coming from MSFT on its current roadmap.

I hope you are carrying this metaphor forward so that means that you and
everyone you know can walk into an emergency room and fix whatever comes
your way or walk into a physician's office and effectively treat whatever
you are asked to, or craft a top of the line Federal appellate brief when
you're asked to do so.

Auto mechanic skills come in handy when your car breaks down,and I wouldn't
mind being able to drive like Tiger Woods, throw like the Manning brothers
or Mike Vick, or hit from outside like an NBA point guard.

Currently, I see large American cities where 99% of the people can't
complete passable sentences in English which I'm told is their native
language or the American slang version of it. I gleefully watched Senators
and Represenatatives parade around through the halls of Congress a couple
months ago demanding that the Star Spangle Banner only be sung in English,
none of whom could sing even the first verse when put on the spot by an ABC
News reporter.

I'd be happy if people who ask for helps in this newsgroup all could ask a
coherent question with the information needed to find an answer for them.

CH

 

[Colin Barnhorst]

Why not just use Linux From Scratch? Roll whatever OS features you like.
http://www.linuxfromscratch.org/

 

[jonah]

This is what I want to see:

Anyone who is in charge of operating a computer system (i.e. home user,
administrator, etc.) should be required to learn how to program in C++ and
Intel-AMD assembly.
(Please note: "x86" is no longer being used as a CPU identifier as Intel
dropped it when they came out with the Core 2 series. AMD hasn't used "x86"
in ages. Where is Cyrix?)

Having this programming ability, they should have access to the specs and
algorithms needed to code any drivers which may be needed by the hardware
their computers use.
They need to be able to compile a skeleton OS from a do-it-yourself kit
(i.e. Linux From Scratch) and add the required drivers and modules without
having to rely on code packages from any other source.
Of course, such packages, like shells, would still be available if the
programmer didn't have time to create his/her own.

What I'm really saying is that we should choose the hardware we want to use,
then create an OS with our chosen features to accomodate such hardware.
We shouldn't have to choose the OS first, then hope the hardware we have
works with it.
What would it take to get hardware manufacturers to release the device specs
to the public without fear of infringement?

-- Andy

Gives me a headache just reading this, you are right of course but IMO
life is too short and I have better things to do.

Jonah