Quote:Original post by Jedimace
BIOS is what they use to make DirectX 10, C++ and OpenGL, right? Well, those are all hard, why are they?

No.

Quote:Original post by Jedimace
Is this a good idea?

No. Its one of the worst, most nonsensical ideas I have ever heard in my life.

I'm struggling to understand, but I beleive you've got it all wrong. The BIOS is most certainly not used to create DX10, C++ or OpenGL.
Also there is a reason these tools are harder to learn is because they are lower level tools. Generally the lower you go the more complex the tool is, however with that you gain a great deal of flexibility (and speed). If you were to design a 'super easy' language which was as powerful as C++ you'd rapidly run into the tradeoff between speed/flexibility vs ease of use.
In short, its not going to happen but writing a simple compiler can be a very rewarding experience.

Quote:Original post by Jedimace
OK, well what is it made with then? I just want enough ease of use. I know what I want with the balance of that.

Made with? The "BIOS" refers to firmware that is on your motherboard. That firmware was most likely coded with C, C++ and possibly some assembly. The compiled code is then stored an executed from a ROM.

The BIOS is a rudimentary operating system. If you want "ease of use", use a fully fledged operating system eg. Windows.

Not even to talk about the BIOS part (That opengl and directx have nothing to do with) . But do you know what it takes to create a programming language ?. What approach are you going to take bottom up, top-down parsing ?. Do you know what BNF, LL(k), LR, LALR is ?. Etc etc etc.

All my games interface directly with my graphics card, cutting Windows out of the loop to get 1337 performancing. I find it better than using teh bloatxzor Windo$e, it slows everything down too much. I coded it all myself in hex, cause assembler is for n00bzorz, and I get better platform independance this way... I have optimated my render code so bithaxxored that it mirrors in my cache so i get teh millionzor fps!!!!!

nah, mate, if you want your games to be played on anything other than your PC you need to use an API which has widespread support. Plus, ignoring the bizarre and misled idea of programming in BIOS, assuming you instead wrote, say, GDOS (GameDevOperatingSystem), an uberleet OS purely for writing games in an intuitive and fast way that was indeed truly awesome, then you would have to write motherboard drivers, graphics card drivers, CPU drivers, soundcard drivers yourself for EVERY SINGLE PIECE of hardware you wanted to support. And that isn;t even mentioning the writing of the OS itself...

If you don't like current API's, then write down the interfaces you would like your API to use. Use this as the external interface for a .dll, or the *nix equivalent, and then write a suitable .dll which implements that functionality using directX or openGL - this is actually an achievable goal for every hobbyist, and having the consistent interface means that you can then use your new interface in every project you do, and update your .dll to move with the times without breaking your previous projects.

Plus,

Quote:it would be super easy, like Python, and as powerful as C++, OpenGL, and DirectX 10

is a bad idea. Chose a language that you like - seemingly python. I am aware that you can write bindings for python, why not write some custom bindings for your .dll and use python for all your game coding from then on. But, easy AND powerful is not possible. With great power comes great responsibility (just because I can use a raw pointer to fiddle around with the stack doesn't mean that I should...)