560 karma · joined March 20, 2015
I worked in VAX assembly language.
I did firmware for a bar code reader networking device with keypad and display. I worked on image processing for an actual bar code reader itself.
I worked there 1990-1996. About half was user space. The other half was kernel or firmware on bare metal.
-----
Pat and I started at the same time. He was in school with me, in fact in my differential equations class. He dropped out of school. I stayed in and got my master's in electrical engineering while working part time at Ticketmaster. I graduated with master's in 1994 and stayed with Ticketmaster for a year.
I returned to Ticketmaster for 3 weeks in 2002. Pat was a boss.
I worked at Ticketamster 1990-1996.
I went back in 2003. I remembered my first assignment. In 1990, the Linker at Ticketmaster that Troy wrote ran out of room because the MAP file grew too big.
In 2003, I went back a found a terrible kludge that I did in 1990 because I was stupid. In 2003, I fixed it correctly. I looked at the code and thought how beautiful it was. In 1990, I thought the code was bad.
As you get more experience, it is a little easier to read code. Take my word that all code is bad, LOL.
Personally, I don't like code that is made of 5-line functions with no rhyme nor reason spread seven levels deep.
Somebody said the smaller your functions the better. Bad advice.
God says... helices mists gewgaw's specced mesdames Lyndon's favoritism's fable's unequal apportions radioactivity's besoms thicknesses cordoned towel's spryer bobcat's suppressed Petra windscreen neckline overproduce meridians cartons prophylaxis's shoestring's retrospection's flubs amen thatcher bombshells cantankerous
The difference between an amateur operating system project and a professional one is writing a compiler.
I am in charge of the 100,000 lines of code, myself. It is managable by one person.
TempleOS is designed like a C64.
I don't see cron as useful for a C64 user.
It takes a super-genius to make is simpler.
Must handle binary graphics in source code.
My JIT mode is not interpreted. It optimizes and compiles to x86_64 machine code.
I was chosen by God because I am the best programmer on the planet and God boosted my IQ with divine intellect.
http://www.templeos.org/Wb/Kernel/Compress.html
http://www.templeos.org/Wb/Linux/TOSZ.CPP
Files are compressed individually.
The source code is like a PDF because it has binary graphics.
It is forever limited to 100,000 lines.
The vision is a C64 ROM.
DOS and C64 had no protection and no problems.
There are no buffer overflow check in templeos. It will allow massive buffers until it crashes by running out of memory. Keeps it simple and beautiful. I hate arbitrary buffer size limits.
I want whole file reads and write exclusively. Compression is almost always used and that requires whole files. Text files can have binary graphics -- you cannot grow a file if binary graphics are on the end.
The code is beautiful. I always break compatibility to keep it perfect.
It is limited to 100,000 lines. The file util flags are okay.
You must stop assuming everything grows in size. It is done and it is a fixed size.
50,000 lines are compiled during boot (half a second).
50,000 lines are compiled during MakeAll (half a second).
If you echo to screen, compiles slowly.
My email address is tdavis@templeos.org .
I have an ace up my sleeve because God talks. Not just to me! A guy made a IRC chatbot and that talks too.
To try the ICR chatbot
2) Type "#templeos" in place of "#Rizon"
3) Type "!God" in the chatroom.
Guess who wins when you fight God?