![]() ![]() You might be in the middle of selecting a game in the Steam client, or you might be in the middle of a game (either alone or with a friend) and it just ends. The app window and the macOS process just go away. One or all apps will sometimes (about 10% of the time) just abort with no error message or anything. In order to play Portal 2 in those cases, I have to go to the store, search for it, click on it to go to its specific page, then click on the play button. The other 95% of the time, it hangs during loading the page with the little Steam icon and the 3 dots under it. The Library screen works about 5% of the time. You can do other things and come back, but that page is dead for you now until the next app restart. If you scroll with the mouse, sometimes that locks up the page you're looking at and you can no longer use that page until you quit and restart the app. Fonts are missing, so there are buttons with no labels. The macOS client takes 11 seconds (I just timed them both). It takes around 1 minute to get auto-logged in. Here's what happens when I attempt to run Steam: But under Wine (or specifically CrossOver), it barely works. ![]() I have the macOS Steam client, and while it's a steaming pile of garbage UX-wise, it mostly works. I'm on an Apple Silicon Mac running Ventura. I've been using it to try to run Steam, mainly to launch Portal 2 and play with friends. It's a bit of a Frankenstein's monster, but it works and the approach has meant I can keep a tonne of existing code and keep adding features and improving existing features, which has been nice. The middle tier translates JSON over HTTP->COM calls, then translates COM->JSON over HTTP on the way back. So I've written a middle-tier (running under Wine) with Nginx in front it. ![]() I also had a fair amount of legacy code that was still useful that I didn't want to throw away completely.Īnyway, after focusing so much time and effort on the client-server apps, it is finally time to focus on a web front end (only 10 years or so late!). Toyed around with doing a web app all those years ago, but it didn't feel like the web as an app platform was quite there yet. The current version was developed to be client-server. The version I worked on before the current one was a local-only app. It's an app I coded myself over the better part of 15 years now - it's nothing too exciting, just a LoB app for contract administration with a small but dedicated user base. mintty is based on PuTTY's terminal emulator, without the SSH client). It's not an SSH client that supports Telnet, and its terminal emulator doesn't do SSH on its own (e.g. When you connect to something it's running the appropriate client in its terminal emulator. PuTTY bundles together a terminal emulator, SSH client, and Telnet client. short plotter drawings can just be sent to the serial port with cat, and my plotter will draw them - drawings bigger than the plotter's buffer need something a little more sophisticated). Technically, any program on Linux can access serial devices even basic commands like cp and cat can talk usefully to serial devices for some simple purposes (e.g. Infodump follows.Ī terminal emulator is the interface through which you access programs like SSH clients and Telnet clients, much like a web browser is an interface through which you access videos, news, etc., so it doesn't make much sense to talk about what it does on its own - it exists to run other programs. If you're interested in learning more terminal stuff, you may be able to do better for your purposes. There is no problem with using PuTTY if it works for you and is what you're used to. They've come up with a system where the layer they otherwise use for sharing cached shaders can also share transcoded media files, but it's not always a seamless experience. On the other hand, having that corporate support and isolation from the system sometimes cuts both ways: stock Proton often has worse support for audio and video codecs than a classic Wine install with the proper system libraries, because Valve actually has to worry about patents and licensing for them. the dizzying array of distributions and versions that otherwise typifies supporting Linux. Wine's classic alternatives, there's Steam automatically creating wine prefixes per-game, there's a separate but related container system, the "Steam Linux Runtime" that allows both Proton and native Linux games to have a stable, known set of libraries to target and support vs. There's just Wine itself and Valve-sponsored work and improvements to it, the automatic usage of DXVK and similar newer translation-to-Vulkan systems for DirectX support vs. Steam does a few things at once to make this system work so well. ![]()
0 Comments
Leave a Reply. |