1) Do not free memory allocated in one language (even more: in one library unless explicitly documented so) into another. Rust can use a custom allocator, and what it uses by default is an implementation detail that can change at a blink.
2) Do not use Vec<T> to pass arrays to C. Use boxed slices. Do not even try to allocate a Vec and free a Box... how can it even work?!
3) free(ptr) can be called even in ptr is NULL
4) ... I frankly stopped reading. I will never know if Rust actually needs Go's defer or not.
To run win32 applications inside Windows operating systems that are too modern (e.g. for 16bit apps), in a browser or on macOS (recent versions of macOS do not have 32bit support and IIRC runnin 32bit wine was not easy).
Of course these are my guesses, I don't think the "purpose" of boxedwine is ever explicitly stated.
Oh oh oh! It in fact now does feel pretty obvious: I missed the part about how if you have this entire stack as one piece you can run it in the browser. Thanks!!
... There are plenty of those kind of games being sold and developed, though.
I only play single player stuff and have a backlog that just keeps increasing, I can't keep with the pace. They aren't the most publicized AAA titles though (BG3 probably bring an exception given its popularity, and the Zeldas thanks to Nintendo).
It's just like music, where there's plenty of good one being made, but can't be found anywhere close to the top 10 hits or on radio (at least, for the kind of music I like).
So yeah... One can dream, but the dream is, for once, alive (mostly thanks to GoG, Steam and Humble).
Pentium 60MHz was P5 though, not P54C ... if I'm not mistaken. IIRC the slowest P54C was the 75MHz one as they all had 1.5x multiplier or greater? Again, I wouldn't rule out my memory being wrong.
I can't find a description of an arrest warrant, but the case I was thinking of was this one from 2010 where three Google execs were found guilty and given suspended jail sentenced by an Italian court. https://www.theguardian.com/technology/2010/feb/24/google-vi...
MS/PC-DOS shipped with debug.com since pretty much the first versions. It is a perfectly usable assembler where you can type a short loop that receives characters from the serial port and outputs them to a file. Similar things have been done many times to salvage hosed systems where a little more than copy file COM1: was required.
With the Internet today, you probably don't even need to remember the instruction names, you can probably find a printout of a program that does this.
For me, if you spend your life reading and writing prose or code, text rendering quality is surely paramount. I’m curious what you think the energy should be spent on instead.
Text legibility is paramount, not rendering quality. Monochrome bitmap fonts are extremely legible once you're used to them, and they don't need 4K displays. Vector fonts with high-quality hinting and antialiasing disabled are almost as good.
It costs almost nothing to your GPU to render fonts in high quality with subpixel antialiasing. Especially when you can cache the rendered glyphs in a texture for reuse.
Compiling? Staying cool and not turning on the fan? Avoiding unnecessary waste?
Really anything rather than a thing that has only drawbacks.
As far as readability goes... can't see a difference with monospace text, maybe even worse as fonts tend to be thinner and need adjustments. Maybe a little better with proportional text on websites and documents.
