Re: bison and yacc. It came from the dragon book which for forever was the way to learn to write languages.
HN user
tehologist
The win32 api is extremely well documented, still supported and very stable. With tons of working examples to do pretty much everything with.
As an added bonus, since win32 is so old. AI is quite strong at generating code for it, I have even had success with qwen 3.5 1.5B parameters with win32 and opengl 1.1
Considering you can use 500 kilobyte distro of tcc that can self compile to build win32 apps and those versions will very easily run on wine. I think it is a valid point and a strategy I have used for sometime. Since windows can't decide what you should use for developing Windows apps
I have one, this isn't true. The wattage of a 5070 is about 300. The spark entire unit runs at 200 watts max. In reality it runs like a rtx 5060 with lots of vram. Very good for training, okay for inferencing if you are running batch jobs and don't mind waiting.
This was also when most of these machines were not online. Security wasn't as much of a concern.
Python pdftools to convert to images and tesseract to ocr them to text files. Fast free and can run on CPU.
TCC is less than a meg to download supports win32 very well and as an added bonus created executables run fine under linux wine.
TCC supports win32 and is less than a meg download and as an added bonus supports linux very well thanks to wine.
I don't understand, just use scite editor with tcc. About a couple of megs download, no install required and your apps will run on everything from win 98 to linux with wine. And if the answer is c++ support then you get all the pain you deserve using that cursed language
I was thinking that this looks a lot like prolog or even make with rewrite terms
Literate programming is alive and well in 2025.
https://leo-editor.github.io/leo-editor/
https://kaleguy.github.io/leovue/#/t/2
https://ganelson.github.io/inweb/inweb/index.html
Inform 7 is arguably one of the largest programs ever written in literate style.
I personally think IDE makes for worse programmers vs just using a text editor.
Why not just use a verifiable subset of C? https://compcert.org/compcert-C.html
Imperial vs Metric is a hard requirement not a convention or formatting. I have a co-worker who wants everything to be a one liner, doesn't like if/else statements, thinks exception handling is bad and will fail a code review over a variable that he feels isn't cased properly.
This makes code reviews super slow and painful, it also means you aren't focusing on the important stuff. What the code actually does and if it meets the requirements in functionality. You don't have time for that stuff, you are too busy trying to make this one person happy by turning an if else into a ternary and the end of sprint is a day away.
All source code is self documenting, source code is for developers to read. Computer languages are a human readable version of what the compiler executes and is for the developers, not the compilers benefit. As a developer, I read way more software than I write and if the source is hard to understand then I feel you failed as a developer. Writing is a skill, no less important in software than anywhere else. Properly named functions/variables and easy to follow flow control is a skill that takes years to learn. All developers should keep a thesaurus and a dictionary nearby. If you find yourself writing a lot of comments trying to explain what you are doing in your code, then you probably should refactor.
I used to do this with Virtual Box running locally. I found the performance of the windows x client was superior to trying to use x directly in the virtual machine. I wish the protocol supported audio.
I am pretty sure logo is mostly a lisp without parenthesis. I find it a lot more readable than most lisp dialects. I am not sure why it never caught on.
https://atariage.com/store/index.php?l=product_detail&p=949
http://8bitworkshop.com/v3.1.0/?=&platform=vcs&file=examples...
https://archive.org/details/StellaProgrammersGuide
There is also batari basic, not sure how much more accessible or easy they could make it. The first link cartridges should work in 2600+
The universe is aging at an alarming rate.
I am so happy to see Charles is still releasing new versions. Has a lot of interesting designs on functional programming using the stack. You can see the inspirations from joy and the portable virtual machine is well designed and easy to understand. This is a great project to study and experiment with.
Copyrighting code never made sense to me. We already have patents for intellectual property. If two people use the same RFC or Whitepaper for an algorithm in the same language, they will probably name the variables similarly and their code will look very similar. Just like if two people wrote out the same hamburger recipe or instructions for hooking up a stereo would also write something similar.
The copyright on the implementation will outlive the patent and allow the implementor to legally take action on claims of copyright infringement. Even though a program is literally just a list of instructions to implement the expired patent.
I avoid GPL projects because I am a software developer and the idea of the project dictating how I can release my own source is a big FU to me. If I can find software that is licensed with a non restrictive license I will always support it over anything that is GPL. I have had a few projects I was very interested in and considered helping out on, but the GPL license is a non starter for me.
If you have to redefine the word "FREE" to mean freedom and your license is several pages of lawyer speak, then that is a problem.
I will take anarchy over crazy ideology any day of the week.
From my understanding GPL originated because Stallman was upset about a version of Emacs he was working on at school (MIT Licensed). The person he was working on it with took the source code and started a commercial company, but had no interest in working with Stallman professionally. So Stallman started his free software crusade with his own version of Emacs and replicating every tool needed to build it with his own "FREE" license. This has always bothered me as GPL is far more strict of a license than either BSD or MIT.
Found the video you referenced.
https://www.youtube.com/watch?v=8QP2fDBIxjM&list=PLpM-Dvs8t0...
I met the creator Charles Moore a few times. When I lived in the bay area and used to go to the svfig (silicon valley forth interest group) meeting. He would often talk about forth was like solving a puzzle, likened it to sudoku. It is a good exercise for the brain and I highly recommend it.
I didn't really understand forth till I tried implementing eforth in c.
https://github.com/tehologist/forthkit
Managed to write a compiler/interpreter that could understand enough forth to implement the entire system. Less than 500 lines and only uses stdio.h and compiles using TCC
That was so much fun I built a second one in under 300 lines of javascript for experimenting with canvas api in web browser. Single file doesn't require a server, you can drag and drop code onto text window.
https://github.com/tehologist/ecma6-forth
Runs standalone, I want to get back to it again.
https://github.com/tehologist/forthkit
I did exactly this, was curious if I could write an outer and inner interpreter in pure c in under 500 lines with only 5 c functions. I then used that to boot strap an image that can run using only the inner interpreter.
http://chiselapp.com/user/tehologist/repository/compc/index
Also several experimental versions. Final version includes a pdf that documents how the c code works.