5 ms·
What would you have them do? Support it on every single distribution out there? They pick a mainstream one and run with it - I get it. It's normal. It's sad, bu
by scrollaway 11y ago
What would you have them do? Support it on every single distribution out there? They pick a mainstream one and run with it - I get it. It's normal. It's sad, but you can't blame them; you gotta blame the ecosystem we're in.
I'm an Arch Linux guy. I strongly dislike both Ubuntu and Canonical, on technical, political and ethical grounds. But I get it.
And you know, a huge part of the problem is that "we", as the Linux community, have no direct interest in pushing compatibility between distributions. It takes a lot of effort, a lot of political reach, and the distros will just run with their own thing a few months later anyway, nullifying the efforts.
Besides... have you seen what happens when people are actually successful at pushing compatibility? Have you seen the shit people throw at Lennart/RH for Systemd? Why would anyone ever want to play that game?
Anyway, not to detract from the topic - it's fantastic news. Unity3d is huge in the game development world and this is a big win.
- masklinn 11y ago> What would you have them do? Support it on every single distribution out there? No, say that Unity comes to Ubuntu.
- deleted 11y ago[deleted]
- scrollaway 11y agoIt's supported on Ubuntu, but if it's available there, it's essentially compatible with Linux. You can't realistically not be compatible with Linux if you're available on Ubuntu.
- baldfat 11y agoUbuntu is Linux, I don't use Ubuntu. I use mostly OpenSUSE/SUSE and sometimes Arch or a Redhat version and if I must Ubuntu or Debian. It will work in Linux just wish we had a solid second tier desktop Distro. Gone are the days when distros decided if something worked or didn't. Thanks to things like SystemD this will continue down that road (Ducks). Also hoping we finally do package management in a elegant modern way soon and not like we are right now.
- vezzy-fnord 11y agoThanks to things like SystemD this will continue down that road (Ducks). How? systemd touches a completely different layer. The main thing that might prevent ELF interoperability across distributions is if the distro has some esoterically configured binutils/glibc toolchain and the provided application is a dynamically linked binary blob.
- baldfat 11y agoSystemD pretty much takes over the core of the OS. This has helped the trend of Distros being interoperational with each other. This is why some people HATE SystemD. Before SystemD we had init scripts in our thousands of packages. Each package system would have different init systems and procedures. This is one of the big reasons why things were not inter-operational between distros. This is why Arch and Debian among others distros jumped off their old init systems and adopted SystemD.
- vezzy-fnord 11y agoThe package systems never had init system integration. What some PMs did was they ran procedures in the postinstall scripts to do things like update SysV symlink farms. In Debian, this was done by sysv-rc and in RPM-based distros, chkconfig or something similar. They're completely orthogonal tools. And no, it was hardly a "big reason" why distros weren't interoperable. Initscripts were rarely supplied by upstream vendors and frequently written downstream. Then many other people didn't use them at all, but wrote runscripts for some flavor of daemontools in about 4 lines or something. The main reason has always boiled down to the toolchain. One proposed way to get around it was fat ELF binaries, but that effort got metaphorically curbstomped by the Linux community. Universal package managers aren't supported for political/branding reasons. In any event, systemd doesn't help with this.
- baldfat 11y ago> The package systems never had init system integration Never said integration saying packages have scripts to init themselves and that was different based on your distro. Don't know why you feel the need to correct a point that distros are becoming more and more alike and that systemd is one of the elements that has helped this? Anywaysssss SystemD is the standard now for most of Linux and I am hoping for MORE standardization.
- fortytw2 11y agoI'd argue that compatibility between distributions isn't a strictly good thing - but rather serves to hamper innovation and new developments in userland from distros in all but a few cases.
- vezzy-fnord 11y agoBesides... have you seen what happens when people are actually successful at pushing compatibility? Have you seen the shit people throw at Lennart/RH for Systemd? Why would anyone ever want to play that game? Let's not bait with systemd, that's a different issue. Package manager interoperability is certainly a political issue. A lot of distributions are identified by their PM infrastructure, so adopting a universal one like Nix or Guix would mean losing their identity. Conflict of interest, quite clearly. We might end up with, GNOME-based distros at least, running a NIH version of Nix called xdg-app, however.
- scrollaway 11y agoPackage management is the least of our worries when it comes to cross-distro compatibility. What truly affects companies wanting to release and support their software on multiple distributions is the lack of universal fat-apps. And yes, xdg-app is the way to go - sadly, only GNOME has been leading that front and cross-desktop talks have stopped. The XDG mailing list is dead. Sending an email there is equivalent to pissing in a violin. Meh, I'm pretty jaded. But I totally do think systemd is a clear example of what happens when a group tries to push for less NIH and more standardization. Tools get replaced and people get upset.
- vezzy-fnord 11y agoxdg-app is a prime example of NIH. It poorly reinvents reproducible, deterministic and isolated builds when battle-tested and academically sound solutions like Nix are available off the shelf. People refusing to adopt it is a good thing in my book, it'll only be harmful in the long term. The Linux community has rejected fat apps (primarily fat ELF binaries) many times, so that's not out of the ordinary. I find the idea of systemd being less NIH to be quite baffling, though. Just look at its ad-hoc LISTEN_FDs protocol rather than adopting something well designed like UCSPI.
- digi_owl 11y ago"fat-apps"? What is the difference between that and a tar.gz with all dependencies included? Mozilla offer Firefox that way, Opera used to offer, well, Opera that way (until they wen't full retard and cloned Chrome). Heck, a RPM is pretty much a fancy tar.gz at first glance (and a DEB a bit more elaborate). I swear i wonder of far up the devops exhaust channel the Linux userspace thinking has gone these days...