Back when I was still using windows (probably XP era), I used to run colinux, it was kind of amazing, setting up something like LAMP stack on the linux side was a lot easier and then using windows editors for editing made for quite nice local dev env, I think! Could even try some of the X11 servers on windows and use a linux desktop on top of windows.

When I noticed I kept inching towards more and more unixy enviornment on the windows, I eventually switched to macOS.

Apart from the obvious hack-value, I can't quite imagine even pretend use-case, with some 486 era machine, you would be limited by memory quite quickly!

[0] http://colinux.org/

[0] https://github.com/microsoft/edit

[0] https://www.bbc.co.uk/programmes/w3ct89y8

This reminds me of the book “How to invent everything” by Ryan North, to kind of see the fast-path for many inventions :)

[0] https://thephd.dev/c2y-the-defer-technical-specification-its...

[0] https://developer.apple.com/support/downloads/Apple-File-Sys...

[0] https://www.posti.fi/en/latest-news-at-posti/%20/news/trump-...

Some of the news listings are perfect, given confined space, but no need to be click-baity. See, f.ex. the news-in-english page [1]

[0] https://yle.fi/aihe/tekstitv

[1] https://yle.fi/aihe/tekstitv?P=191

My "project file" was `e.bat` with `edit file1.cpp file2.cpp file3.cpp`, as it was one of the few editors that I knew that had a decent multi file support with easy switching (alt-1,2,3 ..). I still continue remapping editor keybindings to switch to files with alt/cmd-1,2,3,.. and try to have my "active set" as few of the first files in the editor

It wasn't a great code editor, as it didn't have syntax highlighting, and the indent behaviour wasn't super great (which is why in my early career had my indent was two spaces, as that was easy enough to do by hand, and wasn't too much like tab). But I felt very immediate with the code anyway.

I knew that many others used editors like `qedit`, but somehow they never clicked with me. The unixy editors didn't feel right in dos either.

Quickly trying this, it doesn't seem to switch buffers with the same keybindings, even if it does seem to support multiple buffers.

[0] https://learn.microsoft.com/en-us/windows/dev-drive/

[0] https://thephd.dev/c2y-the-defer-technical-specification-its...

Bit of a shame that you can't fully opt-in to be UTF-8 with the *A API, for your own apps. But I think for the issues highlighted in the post, I think it would still be a valid workaround/defence-in-depth thing.

[0] https://learn.microsoft.com/en-us/windows/apps/design/global...

> Shipping to Switzerland only

which is a shame :/

Frankly I don't remember which language they were, either english or finnish. I had both the red and blue boxes (was it, with windows support or not?), and other was unopened.

I usually preferred english versions myself, as I learned computers with english, it was more comfortable with me. Also IBM had some rather odd choices on some words versus Microsoft, which could be jarring (was it Umpilevy for hard drive, as opposed to Kiintolevy or Kovalevy in most other places).

One year (must of been 1997 or so?) IBM had a crazy marketing campaign at Assembly[0], where they practically just handed out the boxes to anyone who would take them. If they had handed out finnish version, I would be surprised if they were that hard to come by.

[0] https://assembly.org/en

[0]: https://www.youtube.com/watch?v=2CGhBLHfP_M

I find all kind of code folding massively throws off my spatial sense of the code. And if I'm browsing random code, then I often need to see the body too, to see if this is the place the work is done, or is it behind some abstraction down the line.

Perhaps I don't need it as much on c++ codebases, as the headers in a sense are that already. And Rust codebases I've dabbled in haven't been quite that big or overwhelming.

The outlineview/(the popup on top of buffer in many editors that lists the outline) is enough to finding my place in a file I feel lost. And if just looking how to use a lib, there is often some API documentation that helps along finding the right things (even if just barebones doxygen or rustdoc).

I'm sure this is as much of a habit thing as other editor preferences. Still I find it surprising how many people like code-folding :)