TermKit was one of the inspirations for Extraterm ( https://extraterm.org/ ). It separates command output, allows for reuse of previous output, as well mixing content types.
The terminal VSCode has been picking up on these kinds of features lately. Now they can even "sticky" the previous command line at the top of the window when scrolling through long output.
It has taken a long time, but these ideas are slowing spreading around.
Design patterns, for example, really should only be studied once you have quite a bit of experience with complex code bases under your belt. You need to have done battle with some nasty code problems in bigger code bases before you really understand the problems design patterns are trying to solve. Inexperienced developers can't be trusted to apply them because they don't have that judgement. It just looks like a shiny thing.
True for so much of compsci stuff. You won't understand regular languages, automata, grammars etc until you have done a fair bit of pattern grokking yourself.
Synthetic images like generated graphs with fine lines and text (i.e. not photographs), need pixel perfect rendering otherwise they look terrible. This is likely to be a far more common and useful use case for images in a terminal than showing photos.
For images with fine lines we have both ReGIS and Tek4014. ReGIS specifies pixel values (and became somewhat of a pain when DEC terminals with more than 240 scanlines appeared) but Tektronix graphics work with (IIRC) a coordinate space of 4096x4096 addressable points. It's not too amenable to extensions and has very little functionality besides drawing straight lines in various styles and monospaced text in a couple (3, IIRC) sizes.
It's really not that hard. Under GDPR you have a right to privacy, and companies can't demand you give it up as part of some kind of condition to gain access to their service.
Cosmopolitan is cool and I have some uses in mind for it that I wish to get to.
But what I don't understand is the use case for an exe which supports both running as an user app on normal operating systems and from the BIOS. For which application specifically does it makes sense to run it in both these very different contexts?
Look at it the other way round, from someone who wants to put something in the BIOS. It's going to be much more convenient to be able to test as much of that as possible without leaving user mode and actually having to run it by restarting a (potentially virtual) machine.
But also: sbcl. You just know someone's going to do lisp-from-boot with this, if they haven't already.
They aren’t adding value to the Windows platform, unless you consider any application is adding value to the platform it is running on. In which case why should one pay for dev tools, their dev computer, libraries, art assets, etc…
Of course MS asked for it. They created and sustain this situation where software needs to signed for it to easily run on the Windows platform. Who do you think put the signature checking code and root keys in Windows?? The code signing gnomes?? fairies??
They didn't ask for ImageMagick. Would they have asked ImageMagick to develop the software for their platform to enrich it, I would have agreed that they should pay. Otherwise anyone can say I enrich your ecosystem so pay me.
> A scrollbar is not only a control, it's also an indicator.
Thank you! finally someone understands what a scrollbar is for. It primary job is to show the user that the document is bigger than the window, and secondly, to show which part of the document is visible. Letting the user scroll around is not the primary function!
I was genuinely surprised when Apple started hiding scrollbars by default in macOS. Their UI designers clearly don't have a clue what the basic UI controls really do.
Not just that "the document is bigger than the window" but the best scrollbars tell you, approximately, how tall the document is in relation to the window height! Proper scrollbars are, possibly, one of the best UI elements ever invented.
Aside from a status flag in a database (which doesn't actually reflect reality), I don't have anything about location in any contract. I doubt that's atypical, at least in the US.
The terminal VSCode has been picking up on these kinds of features lately. Now they can even "sticky" the previous command line at the top of the window when scrolling through long output.
It has taken a long time, but these ideas are slowing spreading around.