Recherches récentes
Options de recherche
#ascii
Porting Doom to Typescript Types took 3.5 Trillion Lines, 90GB of RAM and a full Year of Work.
The feat was devised by Software Engineer Dmitri Mitropoulos, founder of Michigan Typescript and co-founder of Squiggleconf. He released a video showcasing the results of a year-long effort to get Doom running inside of Typescript's Types system.
![[ImageSource: Dmitri Mitropoulos]
Typescript is a language built on top of Javascript, that add static typing to catch many errant mistakes before your executes, think of it as guardrails which check that functions and other variables are being used correctly. While this is commonly used in all kinds of development, it's unheard of to run a game within Typescript's Type system.
The port itself runs inside three and a half trillion lines of types, totalling a gargantuan size of 177 TB. This is run through Typescript's Type tracker, which takes 12 days to compile the first frame of Doom (0.0000009645 fps). This meant that 20 million type instantiations were running every second in order to get the output.
Mitropoulos explained in the Michigan TypeScript Discord server that this could be improved to take "1 to 12 hours", as long as someone works on it, with the developer noting that he has notes for where potential performance optimizations could be made.
<https://discord.gg/pfKUSmSY>
This was done by running the project within a custom WASM runtime, which is then processed through Typescript within an editor to display a frame.
<https://github.com/MichiganTypeScript/typescript-types-only-wasm-runtime>](https://nerdculture.de/system/media_attachments/files/114/166/740/010/112/784/original/f54d5e08b8f270ce.png "[ImageSource: Dmitri Mitropoulos]
Typescript is a language built on top of Javascript, that add static typing to catch many errant mistakes before your executes, think of it as guardrails which check that functions and other variables are being used correctly. While this is commonly used in all kinds of development, it's unheard of to run a game within Typescript's Type system.
The port itself runs inside three and a half trillion lines of types, totalling a gargantuan size of 177 TB. This is run through Typescript's Type tracker, which takes 12 days to compile the first frame of Doom (0.0000009645 fps). This meant that 20 million type instantiations were running every second in order to get the output.
Mitropoulos explained in the Michigan TypeScript Discord server that this could be improved to take \"1 to 12 hours\", as long as someone works on it, with the developer noting that he has notes for where potential performance optimizations could be made.
<https://discord.gg/pfKUSmSY>
This was done by running the project within a custom WASM runtime, which is then processed through Typescript within an editor to display a frame.
<https://github.com/MichiganTypeScript/typescript-types-only-wasm-runtime>")
![Dmitri Mitropoulos further explained that each value within the Typescript Types system equates to a line of pixels [totalling 128,000 lines of pixels in total], resulting in a "resolution" of 320x200, displayed in ASCII.
To do this, the developer needed to remove limitations within the Typescript compiler itself, highlighting just how large the project got, with the Type tracker runtime consuming over 90 GB of RAM while it was running.
This huge overhead meant that common tools within Typescript could not be used, which meant that the herculean task of encoding every element of Doom in types. This required learning to develop elements like an L1 CPU cache, within Typescript Types itself. Due to Typescript requiring iteration on a single string from the left-hand side, binary algorithms had to be input in reverse.
"Oh, and AI can't help" Dmitri Mitropoulos added, describing that the work was so low level that AI couldn't possibly assist with any of the tasks. Too bad, Grok 3.
Mitropoulos said that he undertook the challenge after completing "every other" Types challenge, and wanted to understand why Doom wouldn't be able to run within Types. However, he managed to find "ridiculous" workarounds to make it all work, despite his own disbelief in the project.](https://nerdculture.de/system/media_attachments/files/114/166/742/069/675/680/original/110e43577d22fe1d.jpeg "Dmitri Mitropoulos further explained that each value within the Typescript Types system equates to a line of pixels [totalling 128,000 lines of pixels in total], resulting in a \"resolution\" of 320x200, displayed in ASCII.
To do this, the developer needed to remove limitations within the Typescript compiler itself, highlighting just how large the project got, with the Type tracker runtime consuming over 90 GB of RAM while it was running.
This huge overhead meant that common tools within Typescript could not be used, which meant that the herculean task of encoding every element of Doom in types. This required learning to develop elements like an L1 CPU cache, within Typescript Types itself. Due to Typescript requiring iteration on a single string from the left-hand side, binary algorithms had to be input in reverse.
\"Oh, and AI can't help\" Dmitri Mitropoulos added, describing that the work was so low level that AI couldn't possibly assist with any of the tasks. Too bad, Grok 3.
Mitropoulos said that he undertook the challenge after completing \"every other\" Types challenge, and wanted to understand why Doom wouldn't be able to run within Types. However, he managed to find \"ridiculous\" workarounds to make it all work, despite his own disbelief in the project.")
Durdraw 0.29.0 has been released! New features include Durview, (an artpack viewer with 16colo.rs integration), custom character sets, better handling of large files, and more. Check it out at https://github.com/cmang/durdraw
Apparently ChatGPT is pretty good at converting graphical charts to ACSII.
OK Once more, one will say that @Freenet is just a space for nerds with high computer skills... But that's not true...
BTW I did participate in a small coding challenge in the spirit of good old #demoscene and you can check the results at https://gitlab.com/hyphanet/demo-challenge-1
Join us ! It's nice and fun !
This is not a pipe character.
As with all such usages the reasons are historical.
More details in this Nostalgia Nerd episode 
¯\_ (ツ) _/¯ 
Ah, behold: the 𝓢𝓾𝓹𝓮𝓻 𝓔𝔁𝓬𝓵𝓾𝓼𝓲𝓿𝓮 no-HTML #Club 
. Because nothing screams "cutting edge" like a '90s text file 
. Welcome to the #Minimalist #Monkhood, where members brag about their #ASCII #Art collections 
while pretending to be anti-establishment. Next time, just send a carrier pigeon 
.
http://no-html.club/index.txt #SuperExclusive #noHTML #CarrierPigeon #HackerNews #ngated
Ah, behold the groundbreaking #innovation of #txtl: a static #website devoted to text #utilities! Because, you know, the world was desperately lacking in #ASCII wizardry 
. Who needs AI when you can strip whitespace at lightning speed? 
️ Clearly, txtl is here to revolutionize the web, one #plaintext at a time 
.
https://viveksjain.github.io/txtl/ #development #humor #HackerNews #ngated
Heh, I've never been an artsy-fartsy graphics guy but I just now recalled how typewriters and matrix printers implemented bold text with 1 color back in the day - just rewind back and type harder!
So I tried the similar with my e-ink display. Just go back and redraw a bold character with 1 pixel offset - and you get a nice readable bold text!
I consider this a major personal achievement of the week.
I drew @BrodieOnLinux as ASCII art, because his Linux youtube channels are sweet.
« The Hungry Crocodiles »
Amstrad ASCII - 40x25 chars - 4 colours
Submitted at Amstrad ASCII Compo 2024, ranked 3rd.
#demoscene #amstrad #amstradcpc #amscii #ascii #asciiart
Did one of my dorfs work themselves to death in the smelter workshop?
retro is always wonderfull ！
