15 ms·
Win32 is the stable Linux userland ABI (and the consequences)
- RcouF1uZ4gsC 5y agoWe might end up in a world, where all the command line applications are Unix/Linux (and run on Windows via WSL) and the GUI applications are Win32 (and run on Linux via Wine) This would be playing to their strengths. There is a much nicer command line/shell ecosystem in Linux and a much nicer GUI ecosystem in Windows.
- pjmlp 5y agoUNIX you mean. That is why so few bother to support Linux OEMs, having some kind of POSIX support is enough for the large majority. However I still disagree, structured shell with REPL like capabilities like PowerShell are so much better and so much closer to the Xerox PARC experience.
- laumars 5y ago> UNIX you mean. Not the GP but generally speaking it’s not a great reach to say that Linux is more widely supported than POSIX. GNU-only flags are often used in shell scripts and you’ll often find binaries are packaged as a snap or Docker container thud anyone running a non-Linux system is left to compile that project themselves. Even WINE itself doesn’t officially support all POSIX-compatible UNIXs.
- smoldesu 5y agoYep. WINE is a second-class citizen on any platform that isn't Linux (as is most POSIX-like software these days), and requires special patches just to run on MacOS (and even paying for Crossover won't give you 32-bit binary support on Mac). For better and worse, the POSIX spec is dead. Besides a few niche use-cases where compatibility with archaic software is necessary, Linux is the new standard for this stuff.
- q-big 5y ago> Linux is the new standard for this stuff. Linux is not a standard, because in opposite to, say, POSIX, it is not standardized, but is an everchanging implementation.
- smoldesu 5y agoI don't mean it in a literal sense, though I get where you're coming from. Think of it this way: your server software's stability is more or less defined by how well it conforms to Linux compatibility. Even software that is designed with perfect POSIX compliance won't run reliably on the majority of servers. Linux, despite not being a standard, has become a spec for server software. The kicker is that nobody can really undermine them unless you can create a true alternative with a more compelling license than GPL. If our industry wants to return to a truly standardized status-quo, we need to put aside our differences and collaborate on a next-gen spec that works. Considering that we barely did this in the 80s with POSIX, I seriously doubt today's developers and researchers are capable of doing it again. I'd love to be proven wrong though.
- mrpippy 5y agoCrossOver does run 32-bit Windows EXEs on macOS
- dundarious 5y agoIt's quite interesting. I'm not sure that broad use of Win32/Wine for all types of GUIs would even work well for things like apps communicating with the broader desktop, and accessibility -- never mind that the desktop software stack is already a crumbling tower of complexity. But I can see it being attractive for full attention/fullscreen apps (like games) that don't use those things or by design bring their own implementations for those things, where the benefit is the reduced decision space for the developer, at the cost of the increased complexity. However, as the article states, ports are often using "compatibility layers" that are just worse versions of Wine though, so for such quasi-ports, there really is no increased complexity in using Wine instead.
- laumars 5y agoUnfortunately the GUI world seems to be settling on web rendering. While this is a massive bonus for cross platform support I’m still having a hard time agreeing that running a dozen Chromium instances is a good thing.
- akkartik 5y agoFavorited (https://news.ycombinator.com/favorites?id=akkartik&comments=t https://news.ycombinator.com/favorites?id=akkartik&comments=...)
- encryptluks2 5y agoI don't think Windows has a nice GUI. It is incredibly bloated.. and Windows has been pushing UWP apps for some time. Please no.. Linux already has an influx of Electron apps, we don't need Windows UI.
- ripley12 5y agoUWP has been unofficially done for a few years now (no official statements, but you could tell from the lack of updates) and they officially shut the door on future updates 4 months ago. https://www.theregister.com/2021/10/26/microsofts_uwp_unwanted_windows_platform/ https://www.theregister.com/2021/10/26/microsofts_uwp_unwant...
- gjsman-1000 5y agoIt’s actually kind of insulting, because if you were one of the few developers to believe Microsoft and write, say, business apps in it as they said, you just got the short end of the stick. It’s not a huge surprise why Microsoft can’t rally developers behind anything.
- ripley12 5y agoYeah, it’s a mess. It seems like eventually they figured out that UWP’s sandbox+packaging requirements were a huge mistake (see Project Reunion/Windows App SDK), but that realization came much too late.
- dtx1 5y agoI developed for UWP, though during the early days when windows phone 10 was still a thing. Honestly it wasn't the sandboxing that turned out to be the biggest problem (see all electron apps nowadays) but that the UWP Plattform was just shit in every way possible, from the design language that forced a desktop to become a phone, the store that never got any traction or quality support, the SDK that needed at least 3 more years of hard work and lots of extensions to become useful but most importantly: The terrible monetization. Microsoft entered a market with android and iphones making developers and companys a lot of money, yet on windows phone and UWP Apps on Desktop it was impossible to make any decent amount of cash.
- stingraycharles 5y agoInterestingly, it works both ways. I recently wanted to play some oldschool Command & Conquer with some friends, and it was very easy to get these old games running in Wine, but my friends (with modern Windows laptops) couldn’t get it to work. Not even with compatibility mode. That was very interesting to me.
- nly 5y agoHardly surprising. Your typical WINE user playing C&C will notice if an update in WINE breaks it, and report it to winehq. EA don't give two shits about legacy C&C games that aren't making them money.
- bennysomething 5y agoCan I run wine on windows then? Only semi joking!
- __s 5y agoYes: https://www.reddit.com/r/bashonubuntuonwindows/comments/6joykc/running_wine_on_wsl https://www.reddit.com/r/bashonubuntuonwindows/comments/6joy... Give it time, WSL support for graphics is in preview: https://docs.microsoft.com/en-us/windows/wsl/tutorials/gui-apps https://docs.microsoft.com/en-us/windows/wsl/tutorials/gui-a...
- mwcampbell 5y agoI think it would be interesting to package up ReactOS [1], which shares a lot of code with Wine, as a VM that could be shipped with an application along with something like QEMU. If I'm not mistaken, QEMU supports virtualization through the Windows Hypervisor Platform and macOS's Hypervisor.framework. Could be a good way for GOG to sell old Windows games. [1]: https://reactos.org/ https://reactos.org/
- Koshkin 5y ago
- marcodiego 5y ago> Linux users tend to be less picky about any possible UX issues induced by Wine. They’ll tolerate a lot of flaws if it means they can have your application at all. Definitely not true: https://news.ycombinator.com/item?id=28978086 https://news.ycombinator.com/item?id=28978086 , Ok, the linked article talks about a "native" port, but still...
- smegsicle 5y ago> Despite having just 5.8% sales, over 38% of bug reports come from Linux > 3/400 bug reports were port specific it's a report about linux users being more likely to report issues in general, not being picky about port quality
- pjmlp 5y ago"What Was IBM’s OS/2, and Why Did It Lose to Windows?" https://www.howtogeek.com/688970/what-was-ibms-os2-and-why-did-it-matter/ https://www.howtogeek.com/688970/what-was-ibms-os2-and-why-d... > Also, OS/2 had a chicken-and-egg problem. Its best selling point was its compatibility with MS-DOS and Windows applications. However, this meant few developers took the time to write OS/2-native apps. So, why run OS/2 at all?
- marcodiego 5y agoIts not easy to "port" the OS/2 situation to the modern world. It as much possible to "run" windows software on linux with wine as it is possible to run linux software on windows with wsl. Of course, since "linux api" is open/public/floss, wsl may have an advantage in compatibility. What is hard to determine is which side this advantage will benefit.
- bogwog 5y agoA more recent example of that is Blackberry 10. The way they tried to get developers was to ship an Android runtime so you can run Android apps. They even offered payments of $100 for every app a developer ported. That just led to the BB appstore getting flooded with low quality Android apps that looked out of place and had terrible performance. Which is not to say that BB10 would’ve succeeded if it had better apps, but it certainly didn’t help. But with Proton/Wine it’s different because the games actually run really well, sometimes even better than they do on Windows, and it’s completely transparent to end users (unlike BB10, where Android apps behaved/looked different) Plus, it doesn’t make a difference to the Linux desktop’s success whether devs write native apps or not. If a new business makes a real effort to develop and sell a Linux desktop product, the only thing that will matter is if customers can adopt it without losing access to the software/workflow they’re familiar with. If they can pull that off, then competing against Windows shouldn’t be that hard; just don’t have a seething hatred of your own customers, and you’ll have a head start on Microsoft. The only issue I see with the Proton reliance is the risk that Microsoft will do Microsoft things, and start introducing subtle API changes designed to break Proton/Wine and sabotage the competition. That’s a legitimate concern, but maybe today’s antitrust climate will make them a little hesitant to do that kind of thing? (Probably not)
- phaedrus 5y agoThis was the same conclusion I came to as well. Both for my personal projects, and what I now recommend at work when the subject of potential Linux ports comes up, is that if WINE is good enough to run it why not just do that?
- smoldesu 5y agoAs a Linux user, I'm generally fine with that "WINE support" mentality, as long as the application isn't demanding (like an NLE, photo editor, DAW, etc). There's a ton of Windows-only tools that I have no problem using on a regular basis, like Lunar IPS and Winamp.
- lnxg33k1 5y ago>> Winamp My hero
- derefr 5y agoIs there still as yet no Linux-native reimplementation of Winamp? (in the sense that it's a lightweight program that 1. plays music and 2. loads Winamp skins + faithfully renders its UI using them, presumably being designed from the ground up primarily to use Winamp skins.) That's doubly-surprising, given that there's already a web reimplementation of Winamp (https://webamp.org/ https://webamp.org/) that does those things. (And it's "lightweight" in terms of not pulling in any JS frameworks; but not especially "lightweight" in terms of you needing a full web browser to run it.)
- moonbug 5y agosure are a lot of parentheses in that.
- zekica 5y agoLinux has stable userland ABI. I managed to run a gui binary from Slackware 12 (from 2007) in a chroot and it worked completely fine. It didn't have modern theming or HiDPI support but it worked fine. Windows apps running via wine and old linux apps running via chroot or any other container (AppImage, snap or Flatpak) all work. The problem is not having specific (major) versions of old libraries in the new OS. If you manage to install them, they will work - this is difficult in most distributions.
- josefx 5y agoUnless you depend on a central service like X11 where only one version runs on the whole system and newer implementations/replacements may intentionally break things. Last time I had to run some ancient software on Linux I just spun up a Virtual Box image with the Linux version it was released for (of course all the mirrors for that where offline by then too).
- salawat 5y agoIt's trivial if you compile from source and onow how to massage the linker!
- NavinF 5y agoOh the linker needs a lot more than a massage; The linker wants full service. When a user needs to run a program, but the inconsiderate lazy dev only built, packaged, and tested the program on 24 ABIs (4 versions of 6 distros) rather than 25 ABIs like he should have, this is what the user wants to see: /data/source/vcpkg/installed/x64-linux/debug/lib/libglib-2.0.a && : /data/source/vcpkg/installed/x64-linux/debug/lib/libglib-2.0.a(gmain.c.o): In function `g_get_worker_context': /data/source/vcpkg/buildtrees/glib/src/2.52.3-34a15219ec.clean/glib/gmain.c:5848: undefined reference to `pthread_sigmask' /data/source/vcpkg/buildtrees/glib/src/2.52.3-34a15219ec.clean/glib/gmain.c:5853: undefined reference to `pthread_sigmask' /data/source/vcpkg/installed/x64-linux/debug/lib/libglib-2.0.a(gregex.c.o): In function `match_info_new': /data/source/vcpkg/buildtrees/glib/src/2.52.3-34a15219ec.clean/glib/gregex.c:588: undefined reference to `pcre_fullinfo' /data/source/vcpkg/installed/x64-linux/debug/lib/libglib-2.0.a(gregex.c.o): In function `g_match_info_next': /data/source/vcpkg/buildtrees/glib/src/2.52.3-34a15219ec.clean/glib/gregex.c:734: undefined reference to `pcre_exec' /data/source/vcpkg/installed/x64-linux/debug/lib/libglib-2.0.a(gregex.c.o): In function `get_matched_substring_number': /data/source/vcpkg/buildtrees/glib/src/2.52.3-34a15219ec.clean/glib/gregex.c:1076: undefined reference to `pcre_get_stringnumber' /data/source/vcpkg/buildtrees/glib/src/2.52.3-34a15219ec.clean/glib/gregex.c:1079: undefined reference to `pcre_get_stringtable_entries' /data/source/vcpkg/installed/x64-linux/debug/lib/libglib-2.0.a(gregex.c.o): In function `g_regex_unref': /data/source/vcpkg/buildtrees/glib/src/2.52.3-34a15219ec.clean/glib/gregex.c:1262: undefined reference to `pcre_free' /data/source/vcpkg/buildtrees/glib/src/2.52.3-34a15219ec.clean/glib/gregex.c:1264: undefined reference to `pcre_free' /data/source/vcpkg/installed/x64-linux/debug/lib/libglib-2.0.a(gregex.c.o): In function `g_regex_new': Clear as mud. Of course you could use the buggy 16 month old version from the package repo.
- TaylorAlexander 5y agoJust my little anecdote: I needed to run an old version of Eagle CAD and I wasn’t sure how to get old Linux versions to run. The old windows version worked great in WINE.
- phendrenad2 5y agoWell, many Linux programs don't work out of the box, so it's possible that the program never worked without talking to an Eagle support rep.
- TaylorAlexander 5y agoI'm not quite sure what you mean. I have a valid license key for that version, but I couldn't figure out how to run the installer. I don't recall exactly what the problem was, but I think it required an old version of a library that was not available in my package manager.
- Tostino 5y agoI took it as a joke about how unstable packages of some Linux software are even when first released, let alone after some time to bitrot.
- pdenton 5y agoToo bad win32 is such a finicky and verbose API that's painful to use for anything beyond the simplest of dialogs. I tried. The MSDN documentation doesn't quite cut it. TheOldNewThing by Raymond Chen is a must-read to get it right. But above all, a stable ABI is only needed for proprietary programs which I abhor for not being FLOSS. As a programmer, I really do think the 4 freedoms are important and loathe anything non-compliant.
- alkonaut 5y agoRunning Win32 UI code as WinForms through .net is a lot less painful than doing straight Win32. Not very good for deploying a tiny program obviously though.
- ripley12 5y agoThere's been a lot of work happening to make WinForms trimmable. I think it will land in the upcoming .NET release (7) or the next one, I'm looking forward to being able to ship small WinForms apps with zero dependencies. https://github.com/dotnet/winforms/issues/4649 https://github.com/dotnet/winforms/issues/4649
- pjmlp 5y agoOr MFC/ATL. Only masochits do pure C Win32, even back in the Win16 days we were better with OWL, MFC and VB.
- tonyedgecombe 5y agoWTL builds on ATL and is far nicer than MFC.
- pjmlp 5y agoIs WTL still mantained, though? That is why I did not mentioned it.
- 5y ago
- philo23 5y ago> Their goal is being able to suspend a game on your desktop and play it on your Deck will likely need them to standardize on a single platform [..] There are some additional challenges with this approach [..] but sticking to a single platform [..] removes some concerns with synchronizing lower level state across multiple platforms. My understanding with the suspend/resume stuff they've talked about for the Deck is less about actually suspending/resuming the game by syncing some low-level state like memory or graphics, and more about quickly syncing save games via Steam cloud saves. I only had a quick look over their docs when the Deck was announced and from what I could tell you basically opt into a new system-level save behavior where at any point the Steamworks library can tell the game "this device is going to suspend now, save your progress" then another computer can start the game and immediately load up the save file, giving the impression of seamless suspend/resume. So as long as your save game files aren't OS specific in some way there's no reason why this should lock you into any specific platform, Windows or otherwise.
- dathinab 5y agoProbably that. Anything else also would be insanely hard. Just trying to "store the GPU state" on a system with AMD GPU and resume it on a system with a NVIDIA GPU (or just old GPU and new GPU from same Vendor) is likely around the area of "lets treat it as impossible".
- davesque 5y agoAlmost impossible and also rather impractical. What each game should care about are the high level details of its game state. Things like "In what map am I located and at what coordinates?" The game engine for each game basically represents a compression algorithm of sorts to decode the meaning of a few concise details like that. If you prefer to represent that information with the raw bytes and bits of internal processor and memory state, you're choosing a hugely inefficient and clunky encoding.
- eropple 5y agoYou're assuming a lot of things in the pursuit of a perfectly spherical game, here. If it were that simple, one might think developers would already do similar. And some do. But a lot of games have issues with this approach, particularly when negotiating data that is partially owned by the engine and that which is owned by game logic.
- Koshkin 5y agoLooks like Win32 is becoming the best GUI (and not only) API for Linux.
- marcodiego 5y agoNo it is not. There are very few win32 popular supported non-game apps on linux right now. Only one I can remember is teamviewer.
- boondaburrah 5y agoI remember when the official Google Picasa client for linux was the windows exe but developed and tested on wine
- marcodiego 5y agoYes, there are examples, but they are few.
- nynx 5y agoEvery time a post like this comes up, I state this opinion: I fully believe that Windows will _eventually_ be replaced with a desktop environment running on top of the linux kernel.
- calvin_ 5y agoNot because it'd be any good, but because it'd be cheaper for Microsoft.
- pjmlp 5y agoJust like Linux only started getting all the money from IBM back in 2000, because it was cheaper than Aix and a good way for IBM to disrupt Microsoft offerings in the enterprise.
- donkarma 5y agoyes and break every single kernel driver ever, nice one
- account42 5y agoKernel drivers can also put behind a compatibility shim if desired, see e.g. https://en.wikipedia.org/wiki/NDISwrapper https://en.wikipedia.org/wiki/NDISwrapper But it's also not like Windows has ever had the same backwards compatibility guarantee for drivers as it has had for applications.
- wmf 5y agoNo, desktop Linux will be replaced by WSL running on top of Windows.
- Snetry 5y agoeh maybe when WSL starts actually being Linux instead of just a cobbled together mess running under the NT kernel
- shmerl 5y agoI was thinking someone should develop a Wine-like layer for Linux ABIs themselves, translating more historic ones into modern ones. That will allow running old native games for a much longer time. In that sense I agree that Wine provides a benefit of preservation and very long term support that native Linux ABIs don't. I completely disagree about regular desktop applications though. Games use case is different becasue they are developed as one time project and game companies move to the next game abandoning support for the old ones in essence after a relatively short time. Such kind of programs need stable ABIs to be usable long term. Desktop applications on the other hand (like browsers for instance) are evolving and are actively developed continuously. They don't need Wine on Linux. I'd simply stay away form those desktop applications which are abandoned.
- homarp 5y agoSee previously "Gabe Newell Wants to Support Linux, Because Windows 8 is a 'Catastrophe'" - https://news.ycombinator.com/item?id=4293046 https://news.ycombinator.com/item?id=4293046 Proton is nice, but still is a wrapper 'behind' what Microsoft can decide to do to make sure they are 'ahead'. From a strategic point of view, this is annoying for Valve. It makes more sense for Valve to try to get more SteamOS only games (and the Steam Deck should help with that), because they control that platform end-to-end (apart from manufacturing their CPU, it's close to what Apple does: Steam store + Steam hardware )
- mahkoh 5y agoIf developers start targeting proton, then Valve will be the gatekeeper that decides which windows apis get widespread adoption in games. Contrary to what the title says, proton will become the stable win32 api. Microsoft's distribution of the proton api could then be called "upstream" or "rolling release".
- pjmlp 5y agoProton doesn't do XBox.
- boondaburrah 5y agoI mean FreeBSD doesn't do Orbis (PS4) games either. Windows and XBox are a bit more like Linux and Android AFAIK (though UWP is a different thing, apparently).
- lewispollard 5y ago> If developers start targeting proton, then Valve will be the gatekeeper Proton is basically wine + dxvk + esync/fsync/wait_v with some community patches (e.g. using a "fake" fullscreen mode that scales up to native res rather than switching resolutions explicitly) and integration for e.g. steam input handler. In other words they're bundling up a bunch of open source tech with sane configuration and adding a few steam integration patches. And it's all open source, on github, too. There isn't much that Valve does explicitly in regards to what windows APIs are supported, and what they do develop and fix gets submitted to upstream wine (though not everything is accepted, I guess). I suppose, if Proton usage explodes such that the bulk of patches to wine get submitted by Valve devs, what you said would be true, but so far that isn't really the case.
- minroot 5y agoI don't understand the whole thing. Instead of working on getting game developers releasing their game to run natively on Linux, people are doing brokenly trying to get things run on Linux with a pile of crap.
- TheRealPomax 5y agoExcept that it's (1) not a pile of crap (it actually works unreasonably well, and keeps improving) and (2) building for one platform and having third party tooling make that work on other platforms means you are not spending five, ten, or even more times as much on purely supporting additional build targets. No sane PM would go "hey let's take a huge chunk of our budget and spend it on native builds and QA for at least five different-enough-to-all-have-their-own-bugs linux platforms in addition to Windows, rather than spending it on actual game development for a single platform".
- NavinF 5y agoYou realize that Linux has <2% market share across all distros and versions, each of which needs a different binary, right? “We shipped Planetary Annihilation on Win, Mac, and Linux. Linux uses we're a big vocal part of the Kickstarter and forums. In the end they accounted for <0.1% of sales but >20% of auto reported crashes and support tickets (most gfx driver related). Would totally skip Linux.” “By the end of my time at Uber I believe very nearly 100% of both crashes and support tickets actually for the game were still Linux related, even after significantly engineering time. Way more Linux specific time put into that project than any other platform. And again, that was for a tiny fraction of the users. Adding Linux support ended up likely costing Uber hundreds of thousands of dollars for a few hundred dollars in sales revenue.” https://mobile.twitter.com/bgolus/status/1080213166116597760?lang=en https://mobile.twitter.com/bgolus/status/1080213166116597760...
- TeddyDD 5y agoCounterpoint: https://www.reddit.com/r/gamedev/comments/qeqn3b/despite_having_just_58_sales_over_38_of_bug/ https://www.reddit.com/r/gamedev/comments/qeqn3b/despite_hav... > all distros and versions, each of which needs a different binary You only need to support Steam runtime.
- nmz 5y ago> After all, we all know the Year of the Linux Desktop is around the corner It's been a while since I've laughed out loud like when I read that. and its not an insult to linux, but I've been hearing about the year of linux on the desktop like I've been hearing about the apocalypse. Believing of the year of linux on the desktop is the same as believing in Nostradamus.
- Underphil 5y agoNot sure who that comes from though. I'm a long time Linux user and could not care less if it ever becomes popular on the desktop.
- sprash 5y agoThe solution is very simple: static linking. Dynamic linking should be completely abolished. This would also solve the "package manger problem" immediately because there will be no dependencies.
- taftster 5y agoYou get all the failures of static linking, too. Security in underlying statically compiled libs, for example.
- calvin_ 5y agoThe deep irony is Windows has achieved its herculean backwards compatibility through dynamic linking.
- mahkoh 5y agoI suppose you would then statically link all gpu drivers into your graphical application? And whenever a new gpu or a new driver is released, you will recompile your application. In case a new driver drops support for older cards, you would then include multiple versions of the driver in your binary. Naturally your binary will be several hundred megabytes large. An interesting idea. I was not aware that proprietary drivers even allowed this.
- sprash 5y agoGraphics drivers is one of the rare if not the only pain point with static linking. The reason is that drivers in general should be part of the kernel but GPU drivers are running in userspace. Proprietary blobs, fast evolving hardware and as a result fast changing APIs are to blame. But on the other hand high level GPU APIs are pretty stable and in general backwards compatible. A program from the year 2000 that only links against OpenGL would still run today (with x86 libs obviously). This means to static link as much as possible still has value.
- andai 5y agoAny distros following this philosophy? Apart from solving the constantly breaking packages problem it sounds like it would also have the fastest installs (at the cost of increased disk usage, though perhaps fs-level (block-level) deduplication could offset this?
- eternityforest 5y agoMaybe Linux should just agree on a standard runtime like Steam has. That can be free and open and cross-distro, and be based on "API Levels" like anything else, so your app can target "API Level 27", and always be usable because API27 never changes, you just make a level 28 next year. Eventually people would get tired of patching old ones, but at that point you just freeze them and have people use a VM to avoid the security holes. Windows has compatibility mode for older windows. And it's great.
- johnny22 5y agothat's basically flatpak, although flatpak runtimes are versioned by year.month
- wmf 5y agoBut Debian/Ubuntu are resisting Flatpak.
- 1_player 5y agoCanonical/Ubuntu are, not Debian.
- andreareina 5y agoQuick search shows Debian has a Flatpak package, which feels like the right amount of involvement. Ubuntu installing Snap packages via apt is exactly the behavior I don't want.
- Geezus-42 5y agoI could see Steam/Proton evolving into a sort of gaming specialized cross platform runtime.
- lmm 5y agoOr FreeBSD, or virtually every other OS out there. Honestly I do wonder why Valve chose Linux over FreeBSD for this use case; for a single-purpose machine FreeBSD offers a far more stable baseline.
- benibela 5y ago20 years ago I was developing software for Windows 98. Recently I tried to run some of the programs on Linux and they still all ran fine unchanged. But the things I wrote for Linux need permanent updates because they break some function change. Especially major versions changes qt4 to qt5 or gtk2 to gtk3...
- phendrenad2 5y agoHow do we fix this? A lot of good analysis of WHAT the problem is here (userland libraries have no "stable API" guarantee, and in fact revel in breaking backward compatibility in some weird sense of spite for people who don't update). Maybe Linus can release Linux II and say "everyone shall use the GTK4 and wayland 1.0 API or you can't use the Linux II trademark" Then again, maybe it doesn't need fixed, since it seems to be working great. Distros just need to ship with WINE preinstalled and better-integrated. Hell, write an entire distro using win32 apps.
- michaelmrose 5y agoIf you can't convince people to use your solutions because they sufficiently better than the seventeen different things actually want to do with their own time on their own machines then trying to abuse trademarks to force them to use what you would prefer is contrary to the ideals of any free software camp you care to name. You would be laughed at equally from all sides and find no users for Linux II save for rebrands that removed all mention of the toxic mark. It would be trivial to go on about all the ways and means that this couldn't possibly work but that would be almost besides the point. The fact that you want this to work is by itself problematic. It's a toxic sort of entitlement to a universe that is a little less complicated and a little less free in order to be a little more convenient and its so problematic that the universe is better off without anything that might be contributed in such a spirit.
- freeone3000 5y agoThis effectively sums up the difficulty in targeting Linux. The concept of any sort of consistency and reliability is immediately dropped. Nothing will ever work the same on two different Linux computers and there's no way to tell if it would, because even compatibility branding is an assault on freedom itself.
- michaelmrose 5y agoAre you seriously calling a single individual using a trademark to tell everyone downstream what software they are allowed to distribute with Linux in order to force everyone to run the software you prefer "compatibility branding". That is dystopian. Linux isn't a sub project of gnome nor will anyone accept it being run like one and why would they? People and projects own their particular contributions they don't own the community and the right to tell others how to use them or their own hardware. Developers of a particular project can rightly say nonpaying users have no right to software they paid nothing for working in a certain fashion but likewise by throwing their software to the wind they have acquired no consideration in return. This means they don't owe you not speaking negatively about said changes, they don't own you not forking, they don't owe you not replacing your software with software that works how they would prefer. People are liable to experience disappearing functionality,software,options as a loss and react accordingly. If a change would be experienced by users as a loss that is paid for not with tangible benefits but with for example developer productivity or satisfaction its unlikely to garner users. Commercial software that is sold outright version on version promotes understanding this. Nobody ever sold version n+1 with the idea that you would accept less features in exchange for a simplified code base unless the software is being sold by developers to developers. End users will never make such a trade. Developers of such software know that they have in fact to compete with their own software n+1 needs to be tangibly better for end users. For example if Wayland were actually desirable AS IS and successfully communicated to its intended users considering what OS, OS version, and software then more than 15% will be using it. 15% update 14 years in is either a failure to be meaningfully better in ways that people actually care about or a failure to communicate. Instead of wishing you could make people use it just keep improving it until people are willing to adopt it.
- dm319 5y agoMight be a crazy idea - but what do people think of repository owners compiling from the source code? Like Valve / Canonical could do it and put out binaries. Obviously there would be agreements about the security/management of the source code. Maybe it could even be done cryptographically so that no source code needs to be visible outside some kind of building machine.
- pinephoneguy 5y agoThis is by far the best solution but too many game devs think keeping the source secret gives them a competitive advantage.
- rob_c 5y agoSeriously the title is like saying that x86 is the only processor for computing we need to embrase it... There are goods and bads to supporting the win32 abi/api with ALL of its quirks and bugs. But most of this (99%+) is trying to support dead projects that will get no support or maintenance even if the bugs turn out to be client side misuse of odd/undocumented errata behaviour. This is a fundamental shift in culture between, release and maintain VS release fire the devs and cash a cheque. Very few closed sourced Windows projects will _ever_ get even the level of updates you get from VMware or Nvidia products during their lifecycle on Linux and these are companies betrated for being mere months behind mainline kernel developments...
- Shadonototra 5y agoI can't believe what I am reading We are doomed
- lenkite 5y agoWell, they could go the whole way and also port WinRT to Linux and MacOS! We can then have proper desktop cross-platform native apps without the electron baggage.
- pinephoneguy 5y agoI've always preferred Windows binaries for closed stuff to Linux ones. If you're not going to open source you thing then don't even bother developing Linux Binaries, we'll just run it in Wine.
- skybrian 5y agoThe article doesn't mention Docker format, which solved this for server-side apps. It seems like that's an example of the Linux ABI getting used on other platforms?
- Shorel 5y agoOne example: Descent2 XXL open source game engine that can run the classic game if you have the levels of Descent 1 and 2. In Windows, it works just as it worked in Windows XP, 7 and so on. Many years after, it still runs. In Linux, any distro not 10 years old, it is basically impossible to make it compile. No binaries can be found that work in any Ubuntu or Red Hat that people actually use in 2022. Whoever said static linking is bad never thought about these scenarios. That's why both Rust and Go are using static linking. The future of not-ridiculously-slow software is going to be statically linked. In a modern computer with modern memory, we should be using the RAM for static linked executables instead of bloated Electron runtimes.
- MuffinFlavored 5y ago> The future of not-ridiculously-slow software is going to be statically linked. If you are running MS Teams, Skype, Discord, and Slack all on one PC, and have Chrome tabs open... how many WebKit/equivalent runtimes is that bundled all together (assuming all of the chat apps still use Electron aka WebKit)?