anwaypasible
Distinguished
[citation][nom]bv90andy[/nom]But they can choose to use DX or OpenGL, can't the developer also choose to work at low-level? Is that locked?[/citation]
is low-level locked you ask.
kinda.
viewing low-level programming langauge is known as 'bubble-pop electric'
because looking at it will make the average person's head pop.
there are only two things to see, massive amounts of data or mathematical equations small enough to be called obnoxious.
and i'm sure you can picture massive amounts of data already.
but when math equations get as small and complex as '^
your head will start to spin.
special care is taken for those who are privileged enough to view the low-level code.
usually they have to go through mental tests to ensure they have enough cache within their personality to keep themselves walking.
it can be enough to make a person flat-out fall to the ground and refuse to walk.. or even pass out.
which makes it a health risk and an insurance risk.
maybe you are walking down the street and are thinking about mastering your code, then suddenly stumble into the street as you collapse from mental breakdown.
without the proper training, you will know what area you want to edit.. but searching for the specific paragraph of code might take days.
a lot can happen.
maybe you start to forget things.
maybe you start mumbling your words, and then it progresses until the point where you are talking to somebody and your vocal chords quit moving.. but you think you said something aloud.
your grasp of time might be completely lost.
extensive amounts of data takes it's toll on the brain and body.
worst case scenario, you become disabled (either physically or mentally) and perhaps you get down bad enough to be hospitalized.
that hospital stay could take years, it depends on how hard you cracked and fell.
that kind of code is usually reserved for only the smartest and most ambitious persons that walk the earth.
and if you have ever needed to get lower in the processing code, you probably had a counselor.
otherwise you broke in and had a peek at something that might have made no sense at all.
knowing low-level code can also be dangerous because of the empowerment the code has.
such code can do a lot of damage really really fast.
its like the motherboard gives the code highest priority, but in reality.. when the code is executed, it goes fast because the electrical pulses are the shortest.
three small bursts of electricity may not sound like much.
but when you realize our processors are dealing with small bursts of electricity at speeds of 2-4ghz
sometimes a nanosecond becomes a long time.
our motherboards are going the way of sonic purity.
when you want the speed.. static in the air might be enough to interfere.
i dont think we are quite there yet with the motherboards of today.. because sonic is described as extremely sensitive, thus giving rise to uber amounts of clarity.
when talking about electricity, the connections from one capacitor to another are as clean and clear as being lost in space with no planets visible.
the amount of resistance (impedance) is low.
like 0.00000000000009 low.
which is why the government has faith that almost nobody will be able to mess around with the motherboard.
it takes way too much money to build an oscilloscope with a resistance low enough to make sense of what is going on.
even if you manage to build the oscilloscope.. you are gonna lose all of the little details because the electron gun is either too high in resistance or too slow and stupid to move that small of an amount.
one way to try would be to extend the distance between the electron gun and the phosphorus screen.
but if you think anybody is gonna sell you a tube that is 15ft from front to back, it wont happen.
and if you think anybody is going to give you the gas required to fill up that tube, you are instantly going to raise a question because 80% of the world doesnt use CRT televisions anymore.
humans have spent decades upon decades getting computers working.
that information was not lost or tossed aside.
the only information that does get thrown away is the hardware ideas.. not usually the software ideas.
once you have working hardware, its all about the software from there on.
so if you dare to look back at all of the progress that has happened.. i feel a bit sorry for you, because low-level programming langauge needs an operating system all by itself to make quick and organized sense of the data.
dont be suprised to hear that some low-level programming has millions of pages of text.
things start with manual input.. then automation takes place and all of those results go into memory.
then you start using the results in memory to build some more.. and all of those results are put into memory.
intelligence is a thing of memory/cache.
humans are amazingly beautiful because once they learn something, they can allocate.
its like being taught something brand new, and you get excited about it and start to calculate answers as if placing a train on the tracks and letting it roll into the future.
is low-level locked you ask.
kinda.
viewing low-level programming langauge is known as 'bubble-pop electric'
because looking at it will make the average person's head pop.
there are only two things to see, massive amounts of data or mathematical equations small enough to be called obnoxious.
and i'm sure you can picture massive amounts of data already.
but when math equations get as small and complex as '^
your head will start to spin.
special care is taken for those who are privileged enough to view the low-level code.
usually they have to go through mental tests to ensure they have enough cache within their personality to keep themselves walking.
it can be enough to make a person flat-out fall to the ground and refuse to walk.. or even pass out.
which makes it a health risk and an insurance risk.
maybe you are walking down the street and are thinking about mastering your code, then suddenly stumble into the street as you collapse from mental breakdown.
without the proper training, you will know what area you want to edit.. but searching for the specific paragraph of code might take days.
a lot can happen.
maybe you start to forget things.
maybe you start mumbling your words, and then it progresses until the point where you are talking to somebody and your vocal chords quit moving.. but you think you said something aloud.
your grasp of time might be completely lost.
extensive amounts of data takes it's toll on the brain and body.
worst case scenario, you become disabled (either physically or mentally) and perhaps you get down bad enough to be hospitalized.
that hospital stay could take years, it depends on how hard you cracked and fell.
that kind of code is usually reserved for only the smartest and most ambitious persons that walk the earth.
and if you have ever needed to get lower in the processing code, you probably had a counselor.
otherwise you broke in and had a peek at something that might have made no sense at all.
knowing low-level code can also be dangerous because of the empowerment the code has.
such code can do a lot of damage really really fast.
its like the motherboard gives the code highest priority, but in reality.. when the code is executed, it goes fast because the electrical pulses are the shortest.
three small bursts of electricity may not sound like much.
but when you realize our processors are dealing with small bursts of electricity at speeds of 2-4ghz
sometimes a nanosecond becomes a long time.
our motherboards are going the way of sonic purity.
when you want the speed.. static in the air might be enough to interfere.
i dont think we are quite there yet with the motherboards of today.. because sonic is described as extremely sensitive, thus giving rise to uber amounts of clarity.
when talking about electricity, the connections from one capacitor to another are as clean and clear as being lost in space with no planets visible.
the amount of resistance (impedance) is low.
like 0.00000000000009 low.
which is why the government has faith that almost nobody will be able to mess around with the motherboard.
it takes way too much money to build an oscilloscope with a resistance low enough to make sense of what is going on.
even if you manage to build the oscilloscope.. you are gonna lose all of the little details because the electron gun is either too high in resistance or too slow and stupid to move that small of an amount.
one way to try would be to extend the distance between the electron gun and the phosphorus screen.
but if you think anybody is gonna sell you a tube that is 15ft from front to back, it wont happen.
and if you think anybody is going to give you the gas required to fill up that tube, you are instantly going to raise a question because 80% of the world doesnt use CRT televisions anymore.
humans have spent decades upon decades getting computers working.
that information was not lost or tossed aside.
the only information that does get thrown away is the hardware ideas.. not usually the software ideas.
once you have working hardware, its all about the software from there on.
so if you dare to look back at all of the progress that has happened.. i feel a bit sorry for you, because low-level programming langauge needs an operating system all by itself to make quick and organized sense of the data.
dont be suprised to hear that some low-level programming has millions of pages of text.
things start with manual input.. then automation takes place and all of those results go into memory.
then you start using the results in memory to build some more.. and all of those results are put into memory.
intelligence is a thing of memory/cache.
humans are amazingly beautiful because once they learn something, they can allocate.
its like being taught something brand new, and you get excited about it and start to calculate answers as if placing a train on the tracks and letting it roll into the future.