bluGill

i last looked into this about 20 years ago. I concluded I could make it work but I don’t use wine enough to bother.

Sure, when linux loads are process it follows a standard procedure to see how to run the file. If the file has ELF markers it runs the process via the ELF loader. If the file has #! as the first then it uses a different process to run that script. (I doubt a.out executable format is supported anymore, but that at least used to be an option). There is no reason you cannot hack this process to detect windows executable and then use wine to load/run the application. I’m not sure why nobody has done this, but the basic things have been supported in linux for decades.

How much will you print? Have you looked into print services - there are companies with the expensive printers that will print your parts for you. Since a print is typically overnight or longer this may be just as fast. If something goes wrong with the print it isn’t your problem.

A terminal is something like a DEC model Vt220, or IBM 3270. These are physical machines with a keyboard, and a display. Most often the display was a CRT, but some were just a printer, I supposed some must have had a LCD but I’ve never seen one. A few did have a mouse, but that was rare. They might look like a computer, but they do not have a CPU (or they do but the CPU is very under powered). The point is you can have 100 cheap (cheap as in 4x the cost of a modern PC, without factoring in inflation) terminals connecting to an expensive powerful computer (expensive as in millions of not inflation adjusted dollars, powerful as in a modern smart phone is faster by nearly any measure). Every terminal had some special commands that programs could use to do something more fancy than plain text, but different ones had different abilities.

These days a powerful PC is cheaper than any terminal could be and vastly more powerful than those old computers, so it doesn’t make sense to have one except as a collectors item. However terminals themselves did leave a useful of program design. Most command line programs know how to control a terminal to do some pretty printing. Thus we often use terminal emulators which let our computer pretend to be one of those old terminals. The DEC vt100 for whatever reason ends up being the most commonly emulated terminal when someone says terminal emulator - there really was a model vt100 terminal at one time.

Note that a web browser counts as a terminal emulator by the above definition. Nobody thinks of them that way, but they fit.

the problem with automatic meta communities
is not all are the same despite the name. Communities on a nsfw server do not belong with the rest. I can imagine a server where the policy\purpose is to mock a topic, or mayb humor takes servers.

Mostly they are the same people.

If you use a linux audio distro linux is easier than windows. Everything works out of the box, not weird drivers to install with all their bloatware.

Try to do it manually is hard, but there are some great pretuned distros that make it easy.

Because the people who developed X11 (that is Xorg) haven declared that. Maybe they should have named it X12, but they didn’t for whatever reason. However the people doing the work have already given up on working on X11 they gave up on X11 beyond the bare minimum almost 10 years ago because some real issues with X11 as a protocol are not fixable.

There were other attempts to a successor to X11, but they never got the support of people doing the work on X11 (in part because they didn’t understand the problem with X11 and so kept many bad things while ‘fixing’ things that were not broken)

Which is to say: you have two choices: get involved with continuing X11 development, or jump to Wayland. Throw a couple million $$$ per year at X11 (either pay developers, or convince a dozen developers to maintain X11) and I’ll retract my statement, until then X11 is dead. If you cannot do that then Wayland is your only option.

They can beef of linux support of freebsd a little and do some other help to the desktop experience there. Freebsd has always been more pragmatic, and for most uses of an os you can’t tell a real world difference. (pkg instead of apt, and other such differences are minor)

While density is helpful ,US suburbs can support great transit for less than the cost of their cars. However they can’t support bad transit, or even okay transit.

It does matter because projects like *BSD can prove continuous usage of the term. As such either the trademark is easy to break (it is common use), or it can only be a trademark in very specific contexts that are unlikely to apply.

Linux is the imposter here. Segmentation fault refers to how the PDP-(I forget) hardware organized memory. It comes from the original unix implementation which linux has never had any part of.