The authors should take the parent comment as a sign their manifesto's title is bad. Some will read the title and make a snap judgement that the manifesto must be totally against AI.
IceWM is a good DE for xrdp servers (https://en.wikipedia.org/wiki/Xrdp). This makes it my main window manager on a workstation I access through Remote Desktop. On my old ThinkPad, I had to migrate off IceWM because Xorg on Debian 13 no longer provided video acceleration. I have switched to Wayland and KDE.
With IceWM, you need to take care of the SSH agent that KDE or Cinnamon would start for you. You can do it with something like this in your `.xinitrc`:
As I said, the computer is a workstation. The xrdp server is a server in the same sense as sshd. I access the workstation remotely from my laptop, iPad, Android phone, etc. I picked Remote Desktop over, say, X2Go because it had the best iPad client some years ago (Microsoft's own).
> It was found that many publications that use Unicode Braille characters use U+2800 with a marking glyph. A
marking space is not without precedent, consider U+1680 OGHAM SPACE MARK. However, in some cases,
U+2800 is clearly used as a symbol, to indicate the presence of a space when describing a Braille sequence
corresponding to a symbol or punctuation, similar to the use of ␣ (U+2423 OPEN BOX) to indicate the
presence of a space. Especially in cases where it is used in a trailing position, as in the [UNE13] example, it is
clear that it would be inappropriate for this symbol to disappear.
> Considering this usage as a marking symbol, together with concerns about changing the relatively stable—and
often hardcoded—White_Space property (a property of only 25 code points, last changed in Unicode 6.3, when
U+180E MONGOLIAN VOWEL SEPARATOR ceased to be a space), the PAG preferred a more targeted
change.
but still unreasonable. In the presence of issues for each of the two options, you pick the correct one unless you have rather strong reasons, which they don't:
> U+2800 is clearly used as a symbol, to indicate the presence of a space when describing a Braille sequence corresponding to a symbol or punctuation, similar to the use of ␣
Why is that? Have you perhaps forgotten to add "␣" equivalent for Braille? So maybe do that instead so people can us a mark to mark something?
> Especially in cases where it is used in a trailing position, as in the [UNE13] example, it is
clear that it would be inappropriate for this symbol to disappear
Nothing disappears in the cited example, the line is very short , how is it possible to reject a fix when you can't even find an example of that fix breaking someone?
> last changed in
and this approach is why we can't have nice things and generations of computer users continue to suffer due to some dumb oversight decades ago. And it's not like we get a payoff of great stability, not, that standard is uber complicated and changes all the time
Good reminder to play Aerofoil. I starred the repository a while ago and forgot about it. By chance, I never played that much Glider PRO, which I know is the more popular game with more houses.
I liked the Flash version of Glider PRO made by Mark Arenz in 2006, which the developer put on GitHub a few years ago (without source): https://github.com/markarenz/rid-flash-archive. Worth a try to see how close it got as a 2000s Flash game. Wikipedia used to say this:
> In 2006, Mark Arenz teamed up with Calhoun to construct a version of Glider PRO built in Adobe Flash.[citation needed]
That's an interesting fork. If it runs SimCity 2000 already, you could set up a page that lets one try it (with user-supplied game files). You can do the same thing as my project: set the GitHub Pages source to GitHub Actions and create a workflow for Pages (https://github.com/dbohdan/glider/blob/b4d14cfd52873c0378995...).
I didn't know about Systemless. I know Classic Mac fans to share it with.
I dug up the project and posted it: https://mac.statico.io/ - click the "How it Works" header to read how Claude decided to make it work. Everything is on GitHub.
Still getting sound working, but I hope to have that done shortly.
Neat. Shufflepuck Café has sound and seems to be fully playable. Its one problem is that Executor doesn't capture the cursor, so a rapid mouse movement causes the cursor to leave the screen and stop moving the paddle.
If you want to add more games, consider The Yukon Trail. Thanks to the magic of bootleg CD-ROMs, it's the Trail game I had as a child in Europe. It is probably weaker than Oregon, but it's worth a playthrough. Collections generally ignore it in favor of the more famous sibling.
I am. My desktop computing has shifted towards fish + vidir, but I use Total Commander for Android on my phone all the time. I have wondered why. What is the difference? Is it just the input method (easier to type shell commands on a physical keyboard)? Well, I don't think so.
The orthodox file manager was created for copying files between two disks. File management on my phone still follows the same pattern: copy or move something between the phone's storage and, for example, an SFTP remote. The remote directories are pretty stable; it makes sense to bookmark them.
Meanwhile, on my computer one-off mass copying has become rare compared to the era of removable media. Most of my mass file operations are moving files to or from a subdirectory in a code project or renaming them. This is an awkward fit for an OFM: you need to go to directory A, duplicate its path to the other pane, switch to the other pane, and then navigate up or down a level to directory B. A dynamic "parent directory" or "../foo/" second pane might help.
reply