Continúo con el tema del arte ASCII. Aquí presento el editor de sprites que he creado.
Recherches récentes
Options de recherche
#ascii
4 messages4 participants0 message aujourd’hui
I have been learning how to code in Python by creating a very fun little ASCII based text game and I have honestly not had that much fun with a video game since I was like 10 years old.
Bon, naturellement, j'ai beaucoup tenté de mettre en avant notre propre jeu, Oremus.
Mais jetez donc un œil à cet autre jeu du concours de fiction interactive 2025 : Le Comte et La Communiste. Réalisation impeccable, interface originale en ASCII, mécaniques d'infiltration et d'espionnage...
I love looking at people's website source code, especially when I stumble across cool things like this:
view-source:https://www.write-on.org/
"there is absolutely no good reason to not begin your architecture with support for [languages other than English]"
https://jenniferkeane.ie/have-you-ever-been-told-that-your-name-is-incorrect/
jenniferkeane.ieHave you ever been told that your name is incorrect? – Jennifer Keane
Zephyr
Custom font in the making once again. I thought I'll post this and regret later as the font will likely be totally different.
What sets apart the Cascii web-based ASCII diagram editor from similar tools is it manipulates whole shapes, not just individual characters, and can save them for further modification. Plus it's shokingly easy to self-host and run locally.
GitHubGitHub - casparwylie/cascii-core: A web-based ASCII and Unicode diagram builder written in vanilla JavascriptA web-based ASCII and Unicode diagram builder written in vanilla Javascript - casparwylie/cascii-core
ASCII Sandwich anyone?
Just dropped `v0.8.0` of `p5.asciify`, introducing layered ASCII rendering pipelines—stackable, flexible, deliciously ASCII!
Check out what's new → https://github.com/humanbydefinition/p5.asciify/releases/tag/v0.8.0
I recently launched the open beta for https://place.textmode.art — a collaborative platform inspired by Reddit's r/place where you create textmode art on a 1024x1024 grid. Log in with Reddit to jump in & join the Discord to chat or give feedback: https://discord.gg/T4EcXZJC
#Development #Launches
Cascii · A web-based ASCII and Unicode diagram builder https://ilo.im/162yk1
_____
#Programming #Generator #ASCII #Unicode #Diagrams #WebDev #JavaScript
⁂ I think I found an easter egg in neovim 
just by chance, I typed ":smile" as a command and it gave me an ASCII art as the output. 
Video below shows the output, I had to record the output because if I took only a screenshot more then half of the output would had been cut off. I know a screen cast is a bit too much just to show an ASCII art, but this is the only way that I can show the whole output. 
GIF
GitHub - casparwylie/cascii-core: A web-based ASCII and Unicode diagram builder written in vanilla Javascript https://github.com/casparwylie/cascii-core #architecture #OpenSource #diagrams #software #diagram #GitHub #design #ascii #app #web
GitHubGitHub - casparwylie/cascii-core: A web-based ASCII and Unicode diagram builder written in vanilla JavascriptA web-based ASCII and Unicode diagram builder written in vanilla Javascript - casparwylie/cascii-core
#WintermuteBBS - that's my second, #Linux based #BBS running the #MBSEBBS software - is now #back #online !
I've updated MBSE BBS to the latest version 1.1.0 (this is a pre-release but I don't mind) and purged quite a bunch of inactive users.
There will be smaller updates and changes throughout the next weeks, as some of the #rss #feeds no longer work and will either be updated or removed (most likely the latter) .
With the code to support plain #ASCII terminals being rewitten in this new release, I will try to rework some of the ASCII screens - but this is may take some time.
Finally, I can contact alien life forms through my terminal 
**astroterm**: A planetarium for your terminal.
Explore stars, planets, constellations, and more.
GitHub: GIF
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.")