Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Why is it always the NAFO pussies who act like
TempleOS doom-port when
edit: i'm only familiar with C and similar, never touched HolyC
What is the longest amount of time you committed to a single project or work of art on your own? A month is difficult for most, a year impressive if not unrealistic. Imagine spending a decade growing something from start to finish by sheer force of will.Give any competent CS graduate time and after 10 years of full-time work they'll write their own templeos. I'd reckon 90% of them will be better in fact, because they would rely on actual design practices and tried-and-tested methods instead of schizophrenic delusions.
You're welcome to visit github to see tens of thousands (if not hundreds) of autists who have been maintaining the same library, driver or program for multiple years for free. Billions of devices rely on their free work and they don't even try to claim fame for it.What is the longest amount of time you committed to a single project or work of art on your own? A month is difficult for most, a year impressive if not unrealistic. Imagine spending a decade growing something from start to finish by sheer force of will.
Unfortunately won't happen due to hardware support, the best hope would be a new Apple who produces their own hardware and tailor-made software, but as it goes, you're never going to compete with the big boys when you need to beg Broadcom to write drivers for your OS so people can have an ethernet connection, saying nothing of things like GPU acceleration on NVIDIA etc...Terry A. Davis is really an inspiring person and has inspired a shit ton of programmers to build wild and crazy things just because.
I am genuinely hoping for a time where tons of people are able to create their own operating systems that are completely viable and can compete with the big boys.
You've been DEBOONKED by Andreas Kling, creator of SerenityOS.Give any competent CS graduate time and after 10 years of full-time work they'll write their own templeos. I'd reckon 90% of them will be better in fact, because they would rely on actual design practices and tried-and-tested methods instead of schizophrenic delusions.
Already exists, in fact CyberChud was started as a fork of Alec Murphy's ELF loader written for chocolate-doom: https://gitgud.io/CrunkLord420/chocolate-doomTempleOS doom-port when
edit: i'm only familiar with C and similar, never touched HolyC
>maintaining a driver for a single device is on the level of an entire OSBillions of devices rely on their free work and they don't even try to claim fame for it.
I wish that port was limited to TempleOS's color pallete and used the PC Speaker sound effects that are in the game, otherwhise it feels off having regular Doom on it, it should look more like this instead.Already exists, in fact CyberChud was started as a fork of Alec Murphy's ELF loader written for chocolate-doom: https://gitgud.io/CrunkLord420/chocolate-doom
I should point out that Alec Murphy's chocolate-doom ELF loader is flawed as he does not relocate the ELF into allocate TempleOS memory space and is subject to random memory corruption. My version does alignment, segment allocation, relocation, correctly updates the global offset table and a bunch of other stuff that it previously didn't.
https://youtube.com/watch?v=-SVZftr06Lg
I feel like Linux users should be okay with compiling it themselves. I updated the README.md with slightly better instructions, but other than using the cmake flags outlined and ensuring dependencies are installed it's largely automatic.spent a good few days trying to get it up and running on my steamdeck, boxes crashes when it tries to boot it (I'd say its doing shit that boxes doesn't support) and im not willing to unlock the root partition just to install virtual box, vmware or bloody qemu.
im just gonna wait for crunk to release a linux version then try and get it working.
I'll build in a vm on my desktop then transfer the compiled version to my deck then report my results.I feel like Linux users should be okay with compiling it themselves. I updated the README.md with slightly better instructions, but other than using the cmake flags outlined and ensuring dependencies are installed it's largely automatic.