It's like having the dream of running Visual Studio 2026 on linux: COMPLETELY RETARDED.
Loss32: Let's Build a Win32/Linux
391–400 of 493 posts
Re: Loss32: Let's Build a Win32/Linux
#392Earlier quoted context omitted.
Versioned glibc symbols are part of the reason that binaries aren't portable across Linux distributions and time.
Only because people aren't putting in the effort to build their binaries properly. You need to link against the oldest glibc version that has all the symbols you need, and then your binary will actually work everywhere(*). * Except for non-glibc distributions of course.
I don’t understand why this is the case, and would like to understand. If I want only functions f1 and f2 which were introduced in glibc versions v1 and v2, why do I have to build with v2 rather than v3? Shouldn’t the symbols be named something like glibc_v1_f1 and glibc_v2_f2 regardless of whether you’re compiling against glibc v2 or glibc v3? If it is instead something like “compiling against vN uses symbols glibc_vN_f1 and glibc_vN_f2” combined with glibc v3 providing glibc_v1_f1, glibc_v2_f1, glibc_v3_f1, glibc_v2_f2 and glbc_v3_f2… why would it be that way?
Re: Loss32: Let's Build a Win32/Linux
#393Earlier quoted context omitted.
Depends on what task you're doing, and to a certain extent how you prefer to do it. For example sure there's plenty of ways to tag/rename media files, but I've yet to find something that matches the power of Mp3tag in a GUI under linux.
Have you tried kid3 ( https://kid3.kde.org )? It has both a GUI and a CLI. From a quick glance at the feature lists it looks quite comparable.
I just did, have you actually tried using them side-by-side? It's hard for me to look favorably on kid3. I actually gave myself 5-10m to try and learn kid3 and a lot of what seems like obvious ways to accomplish a task like 'rename these files using their tags' didn't do anything. I even broke out the manual which didn't help/explain if there was a different mindset I need to adopt. I could manage to manually edit tags/rename file by file, but that seems like table stakes for anything that handles media files (even a file manager) let alone an application that is meant to be a specialist in that area, and we're not into any advanced functionality yet.
More generally though it's not about one specific type of tool, it's that windows and linux have been different ecosystems for decades and that has encouraged different strengths and weaknesses. To catch up would mean a lot of effort even if you're just aiming to be equivalent, or use projects like WINE to blur the lines and use the win32 tool as though the specific platform doesn't matter so much.
Re: Loss32: Let's Build a Win32/Linux
#394Earlier quoted context omitted.
Your tone makes it sound like this is a bad thing. But from a user’s perspective, I do want a distro to package as much software as possible. And it has nothing to do with user freedom. It’s all about being entitled as a user to have the world’s software conveniently packaged.
What if you want to use a newer or older version of just one package without having to update or downgrade the entire goddamn universe? What if you need to use proprietary software? I've had so much trouble with package managers that I'm not even sure they are a good idea to begin with.
That is the point of flatpak or appimage but even before that you could do it by shipping the libraries with your software and use LD_LIBRARY_PATH to link your software to them.
That was what most well packaged proprietary software used to do when installing into /opt.
Re: Loss32: Let's Build a Win32/Linux
#395Re: Loss32: Let's Build a Win32/Linux
#396Earlier quoted context omitted.
Yes. Enterprise, Pro, and Home are the enshittified, retail editions. Enterprise just adds a few more features IIRC but still has ads. The other versions I mentioned above don't have any of that.
Enterprise is not retail and is usually done via volume licensing, but probably without any additional configuration it might have that stuff intact. But you can use group policy etc. freely. I don't know how Win 11 is though
FWIW, ChatGPT advised against LTSC or Server editions for a dev workstation and recommended Enterprise, as you do. However, I can’t find Enterprise from a reputable EU vendor. Do you know of any? Is Enterprise available to end users?
Re: Loss32: Let's Build a Win32/Linux
#397Nice. It would be good if winetricks could install the ReactOS userland, explorer.exe and friends barely exist in upstream wine.
There were some great efforts to build these out in ReactOS a few years ago.
Re: Loss32: Let's Build a Win32/Linux
#398Earlier quoted context omitted.
Indeed. AmigaOS was the pinnacle of personal computing OS design. Everything since has been a regression. Fite me.
What about BeOS ?
Not very likely, what if the BeOS API emerged as "the standard" on Linux?
It would not solve the ABI problem, but it would give at least an opinionated end to end API that was at some point the official API of an OS. It has some praise on its design too.
Re: Loss32: Let's Build a Win32/Linux
#399Earlier quoted context omitted.
Isn't the kernel responsible for the ABI?
ABI is a far larger concept than the kernel UAPI. Remember that the OS includes a lot of things in userspace as well. Many of these things are not even stable between the various contemporary Linux distros, let alone older versions of them. This might include dbus services, fs layout, window manager integration, and all sorts of other things.
Thanks
Re: Loss32: Let's Build a Win32/Linux
#400Earlier quoted context omitted.
> That's not true. React only re-renders down from where the update happens. And it skips over stuff that is provably unchanged -- which, fair, involves manual memoization hints. React only skips over stuff that's provably unchanged. But in many - most? web apps, it rerenders a lot . Yeah, you can add memoization hints. But how many people actually do that? I've worked on several react projects, and I don't think I'v…
>React only skips over stuff that's provably unchanged. But in many - most? web apps, it rerenders a lot. Yeah, you can add memoization hints. But how many people actually do that? Even without any hints, it doesn't re-render "the entire view tree" like your parent comment claims, but only stuff below the place that's updated. E.g. if you're updating a text box, only stuff under the component owning that text box's s…
Thanks for your work on react. I just realised who I’m talking to sweats. I agree that the functional reactive model is a very different programming model than VB6. We all owe a lot to react, even though I personally don’t use the react library itself any more. But it does seem a pity to me how many sloppy, bloated websites out there are built on top of react. And how SwiftUI and others seem to be trying to copy react rather than copy its newer, younger siblings which had a chance to learn from some of react’s choices and iterate on them.
UI libraries aside, I’d really love to see the same reactive programming pattern applied to a compiler. Done well, I’m convinced we should be able to implement sub-millisecond patching of a binary as I chance my code.