@brandon Dunno. Probably will look at it after I’m done fuckin’ around with FreeBASIC.
@gudenau I had a bug like that in my terminal program, very early on in its development. It was, for me, an off-by-one error in my painting routine.
@gudenau Probably a good chunk of it. However, the really nice thing is that FreeBASIC essentially just compiles to C anyway. It has a static support runtime that is included in the final program output, so the only dynamic linker dependencies are those for a standard C++ program, plus curses.
@brandon Real Linux kernel!
Install an X11 server for Windows, have it listen on TCP, and enjoy the use of GUI apps inside the distro.
At least, that’s my plan.
@brandon About to try WSL2 myself...
@trickster @farhan It is opaque in that you have only indirect control of it. But even then, task switching has an impact on the cache. You only truly have any control at all under a single-tasking system where the working set size (including code) is smaller than the cache itself.
Otherwise, it is supposed to be opaque: otherwise you could break memory protection rules. No body needs an MMU just for L1 cache.
@farhan *vet the scripts they run
@farhan To execute a script on the network without saving it. Saves clutter. One should still very the actors they run, though.
@tuxcrafting Seems about right...
@tuxcrafting As an aside, the same program under MUSL, statically linked, results in a very small binary—around 16KB. MUSL is “DOS-weight”, without the limitations implied by that term.
@mdszy It took me about five working days to read the book, another couple to get familiar with the standard library. Making Web apps is easy. Making daemons is easy. Making a FUSE filesystem is easy.
Haven’t tried doing a GUI app yet. But I expect it’ll be easy. The macro system is very powerful, too, and allows you to easily embed resources such as HTML and images into the compiled program binary.
Utter failure and lost cause, thanks to the marvels of modern medicine and society.
Follow at your own risk. Followers must have content or face rejection.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either! We adhere to an adapted version of the TootCat Code of Conduct and have documented a list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators. Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!