Improvements have been made, as well as things making it worse. There are different ways in which they can be better and worse, not only one way. Some of these are mentioned in that article, but I do not entirely agree with all of the ideas there even though some are valid.
I think that software (and hardware) should be made in a better way which combines what should be good from new and old things, instead of necessarily avoiding what they were in the past due to thinking that the newer ones are somehow inherently better even though it is not that simple.
Yes, and I prefer to use a keyboard. (For television and something else where there isn't a full keyboard, you can use numbers. I intended to invent Movie Decimal for this purpose, and have implemented a subset of Movie Decimal (the subset involving titles, although the full Movie Decimal is supposed to allow many other search criteria as well such as year, genre, who assigned the ID (similar to OID), etc) and already found it useful. It can allow quick entry for someone who is used to Movie Decimal, and slow but understandable if you are not used to it (since the display will tell you what numbers to push next, making it easy to understand).)
I have written some useful small programs in uxn, such as: hex decoder in 39 bytes (which handles optional spaces and line breaks, uppercase and lowercase, etc), a program to convert JSON to NDJSON in 125 bytes, a program to convert DER to a subset of TER in 220 bytes, BLAKE2s in 1024 bytes (although some of it is padding for alignment, which is why it comes out to exactly 1024), a card game (including graphics, sound effects, fonts, scoring, etc) in 1853 bytes, etc. (These do not always check for errors (although the card game does check that you had made a valid move), which is one of the things that makes them short; since you might want such things sometimes that makes other programs longer, and this is not specific to uxn or to programs I wrote.) Other people might have also done.
The description of uxn and varvara are also small and might need only two pages (I did not write it).
I also remember reading in a book that someone made a game on Atari in 2 kilobytes, and described how they could make it fit (by making the map symmetric, etc), which was rejected because they had 4 kilobyte cartridges by then. (The article in this submission also links to a different game that (probably) someone else made in 2 kilobytes, but this time with JavaScript and HTML. Atari and uxn/varvara are much simpler systems than HTML/JavaScript, though.)
uxntal and varvara bring me such joy, it's that perfect complexity where everything feels like a fun puzzle you can approach one step at a time.
The first time I saw it years back I was skeptical. As foremost a hardware guy I saw instructions in transistor count and gate delay, all that spaffed away on 16x16 multiply and you couldn't spare one flip flop for an overflow flag? Preposterous!
But the software already written was cool enough to convince me it was worth emulating, and once you've got an emulator you may as well write some software. A few short programs and I was in love.
It's not about running code efficiently, it's about making it fun to write efficient code.
No sharp edges, no corner cases, generally minimal machine state. The cognitive load is so much smaller than any real world assembly I've used.
I didn't mean to write such a lot of meandering offtopic fluff, but damn, I just love that little guy
( ⊖-w-⊖)
I think the CSS they use (which isn't much) is good enough (and "img{max-width:100%}" really ought to be the default setting even if the user disables CSS).
I think 100 W incandescent are too bright; I use 5 W incandescent lights (usually only one at a time, sometimes two if one is insufficient). I also find LED lighting (and flurescent) to be irritating (and they actually use a bit more power, the LED lighting that they installed (but I removed) uses 8 W instead of the 5 W that the incandescent light uses), so I don't use them.
However, I think that often you should not need to be overly reliant on electric power. If you have enough windows then you should not need electric light in the day time, if the incandescent light in the winter time also provides heat, if you have candles when needed, moon light (depending on the phase of the moon), etc, and I can write by hand and many things can be done without a computer (including, walk to where you need to go; I do not have a car so I walk if it is close enough or car pooling with someone else if far away), there is sweater and blankets and candles (which also provide light) in case you are cold in the winter time, etc. If you learn to work things without electric power too then it avoids some of the overly reliance on it.
Getting rid of the roads for cars (and the cars) would also have some advantages (it would need more walking and others but those things can help, anyways).
You can duplicate the functionality of computer games (and other computer programs) without decompiling them, in some cases. However, this can require a lot of testing to figure out the working. Having a reimplementation (whether due to decompilation or due to figuring out the behaviour without decompiling it) can be helpful to explain the game rules better too, which many computer games don't explain very well in their documentation, so this means it is possible to write a better documentation (one example where this is helpful is Pokemon). (I have figured out the working of Hero Hearts without decompilation, and making it (at least in my opinion) better than the original, without needing any LLM/generative-AI to do this. Some people (including myself but mostly others) have guessed at (and tested) some behaviours of ZZT, both by testing and by partial decompilation, but eventually someone did rewrite the source code which produces the same executable file than the original, so it is known that it is the correct implementation.)
I agree that there are advantages of the usability of VHS; the menus should not be needed (even if they are helpful on some DVDs, they shouldn't be required). There are disadvantages as well, such as being slow (to rewind back to the beginning) and being damaged (although DVDs can be damaged too). Index searching is possible with VHS but I think it is mostly only used when recording TV shows and is not used with movies, even though I think can sometimes be helpful with movies.
Where a menu might help is a list of the titles and chapters, although such things can also be printed on the box and selected directly by numeric entry (in which case the menu is not needed, but can be helpful in case you do not have the box). Subtitles, audio, etc can usually be selected by other functions in the DVD player. (Sometimes there are other functions as well, but mostly it should be good enough to just select titles and chapters by numeric entry. DVD players ought to have the option that you can disable unwanted functions in order to just play the selected title directly.) VHS also has index marks but those are mostly used for making your own recording rather than movies.
I think that it should not need to be mutually exclusive. You can make it you can enter the programs yourself (if you prefer to do for whatever reason, including, it does not work well (like you mention), or because of Dijkstra objection or other objections to the use of AI for programming the computer or AI in general), but that AI can also be possible.
> At home, I use software that is well-crafted to do some thing. Or I write a series of scripts to do narrow things that for some reason aren't in Aptitude or Snap, for example "copy all the photos off my iPhone and rename them and sort them by date in my filesystem".
> Perhaps I have no imagination, but I don't feel like having an LLM make applications on my phone. I want good software that someone that I trust wrote.
I do not use LLM either, and do not intend to do. I can write my own programs. Even if someone does want to use LLM, it should neither be required nor expected nor the default (and there are also reasons why I think that it should be discouraged to use LLM too much); you should be able to write the scripts and programs by yourself if you want to do it that way (and the computer made to make this possible to do without LLM), even if some people can make LLM to do it at their option, but it should not to require LLM and AI.
I also think that the computer that can start with a programming language such as BASIC or Forth (without first needing menus and GUI to access all of the programs) is useful, and that it is not as good that many modern computers do not do like that.
Let me add my voice to that. It's strange to me that people are now talking about LLM integration in daily-driving their computer as if it would be something desirable. As if being able to "write one's own programs" directly wouldn't be enough; as if the focus shouldn't be on just making that as easy as possible, so that you can just type out what you want instead of expecting a nondeterministic system to infer your meaning. And that's before considering the security risks.
It feels to me rather analogous to being in a foreign country and, rather than learning the local language, you get to hire this translator that works for absurdly cheap, but you have no real idea of the accuracy (because you didn't learn!) and for some reason the translator is only able to speak while physically holding your wallet.
Oddly enough, from what I can tell, AI-powered translation services are not capturing a lot of imagination, while interest in AI-powered (human) language tutoring is booming (at least on the supply side).
> you should be able to write the scripts and programs by yourself if you want to do it that way
Having chat gpt one write me a powershell script took a 3 hour manual task using software and made it a 10 minute task which I can repeat any time I fancy should I need to.
Writing something similar would've taken me an hour+ just to dig out the key pieces of information I needed to start in a language I am proficient in. Why would I waste my time?
I think that software (and hardware) should be made in a better way which combines what should be good from new and old things, instead of necessarily avoiding what they were in the past due to thinking that the newer ones are somehow inherently better even though it is not that simple.