HNHacker News
TopNewBestAskShowJobs

zxzax

603 karma · joined April 19, 2021

submissionscomments
zxzax··on Systemd: The Good Parts
The code savings from including udev in systemd turned out to be greater, as there was more re-usable code already written in systemd. Please be the better person and don't revive this flamewar, it's not helpful, let's stick to the technical facts and work together to find the answers we seek -- for example you can look at the git logs to see all the shared functionality and the code that was changed around: https://github.com/systemd/systemd/tree/main/src/udev
zxzax··on Systemd: The Good Parts
So that really seems to be the core of the problem to me: nobody really wants to seriously maintain udev as an individual project. It's not a fun or glamorous project to work on, it's boring, nobody will notice it unless it breaks, and nobody really seems to care that it depends on libsystemd. For most people this is just an implementation detail. For an embedded distro I can't see why you would use udevd or eudev, you probably want a much simpler device manager without the giant hwdb.
zxzax··on Systemd: The Good Parts
The issue is not with the actual udev device event logic itself, but with all the other bits I talked about. Those are the things that would need to be duplicated.

>to force other distributions into using libsystemd, which would logically end with them also using systemd itself.

As I said elsewhere, libsystemd is just a library with some generic functions provided for convenience. This is like saying that installing python libraries on your system logically means that the PSF is trying to take over your system and forcibly rewrite everything in python, it doesn't make any sense.

zxzax··on Systemd: The Good Parts
That doesn't really make any sense, libsystemd is just a library with some fairly generic functionality.
zxzax··on Systemd: The Good Parts
Because that would not reduce code duplication. I don't know if you have ever worked on any of the low-level Linux libraries written in C, but the amount of unnecessary code duplication across them is awful. The standard library features provided by glibc are extremely inadequate for modern applications, every non-trivial C project I've seen starts to include their own private implementations of various C++ things like hashmaps, binary trees, dynamically sized strings, unicode support, async event loops, etc.

For utilities that have to interact with low level kernel APIs it's even worse, every library seems to have to reimplement their own parsing of various other random things like netlink, or in the various pseudo filesystems like sysfs, procfs, cgroupfs, etc etc, the situation is really way out of hand. I don't know how to solve this in a reasonable manner beyond what systemd is already doing. Yes people will complain that they have a systemd dependency now but what else can you do? This is the exact reason the BSDs update the kernel, libc, init and core utils in tandem and consider a lot of the kernel API to be private, Linux was just slow to catch on in that regard.

zxzax··on Systemd: The Good Parts
Libsystemd is just a shared library with some common code used by various systemd daemons (an epoll-based event loop, the dbus protocol implementation, uuid generation, parsers for the binary logs, etc). I can understand why people don't want to run systemd as pid1, but having some other external daemon depend on this library doesn't make it any harder to bootstrap that type of distribution.
zxzax··on Systemd: The Good Parts
I don't understand, is this not what you were asking for initially? libsystemd.so is just a shared library, it's not any more of a giant pain than any other library.
zxzax··on Systemd: The Good Parts
The udevd package in gentoo does exactly this, which is supported as an alternative to eudev: https://packages.gentoo.org/packages/sys-fs/udev

I believe the reason for eudev is to avoid some of those other unwanted changes from upstream udev that broke udev scripts. Which to me is a fine technical justification, but not really related to another udev implementation having a build dependency on libsystemd. The udevd package seems maintained so I really don't understand what operational issues that comment is getting at.

zxzax··on Systemd: The Good Parts
Not sure why you're saying that -- moving it to a library is basically what happened. The libudev code got moved to libsystemd, and now libudev is a wrapper around that.
zxzax··on Systemd: The Good Parts
According to Lennart that's correct, the reason it was done was to reduce the amount of duplicate code: https://lwn.net/Articles/490441/
zxzax··on Systemd: The Good Parts
>that decision [...] was done for purely anti-competitive reasons.

This is not correct, I don't know where you got this idea. The systemd-udevd daemon still runs without systemd. The code has moved into the systemd repository, and it has a build dependency on libsystemd, but otherwise it has no runtime dependency; your distro should be able to package it separately if it wants.

zxzax··on As a longtime BSD user, I have my doubts about our future
I personally wouldn't take these incidents on twitter as indicative of anything, there is quite a lot of information missing there. You or I probably don't know the full history of the company or what transpired for it to get to that point, only the people who experienced it firsthand really know that. Social media is its own community that is really good at turning things outside itself into polarization and outrage, it's not what a community manager for some open source project would usually turn towards in order to solve problems within a community. Leave twitter's problems to twitter.
zxzax··on As a longtime BSD user, I have my doubts about our future
Right, but Firefox is its own special case. I don't get that complaint in the context of GTK or Qt apps -- dbus is the native IPC there. Taking it out without a replacement is just going to break things, and any replacement has to happen at the toolkit level. It's not something that the apps would ever really want to handle, unless they're already built like firefox to be self-contained and not need IPC.
zxzax··on As a longtime BSD user, I have my doubts about our future
Those pieces can all be separated, but increasingly few people seem to be interested in putting in the work to do it. In particular, freedesktop is mostly just a set of standards for common protocols and file formats for an open source desktop -- I doubt anyone wants to get rid of that stuff just to have their applications all break.
zxzax··on As a longtime BSD user, I have my doubts about our future
>the vast majority aren't out to find people they can label as 'problematic' and chase them off the island.

To me that it always the problem that has faced any minority groups anywhere -- it's never obvious to the majority what the alienating behavior is. So they have to painstakingly explain it, and of course some of them will always get accused of overreacting and attacking the majority. What else can be done?

zxzax··on As a longtime BSD user, I have my doubts about our future
Practically speaking I don't think it's less loaded, for example if someone working on something decides suddenly that they're switching license to GPL, that has historically caused problems for BSD in the past (more than once).

It's really difficult to continue this conversation if you view the concept of justice to be alienating, what is open source if not a means to deliver code to large groups of people who would otherwise be alienated from working with that code? I don't understand. If you're not interested to help customers and be fair and just to them, I would think you would have a hard time working at any company. What is your real goal?

zxzax··on As a longtime BSD user, I have my doubts about our future
What is the issue with dbus? I've seen a lot of complaints about it but I have yet to see anyone bother to create a viable replacement for it, after several years.
zxzax··on As a longtime BSD user, I have my doubts about our future
You would probably see people using it any time a lot of people feel alienated by the behavior.

Usually I see good community managers as people who go out of their way to be agreeable to the whole community, helping to reach common ground and consensus. That's their job, to solve those people problems. The size of the circle is whatever your community defines it to be, for some communities it's obviously easier to find consensus than for others. Example from the reddit post: Linux people seem to be fine with both GPL and BSD license, but BSD people seem to view GPL as problematic. So practically speaking it seems it can be easier to reach consensus in Linux, around some particular code licensing issues anyway (Please don't start a flamewar about this, I personally don't take any sides here when it comes to licensing).

zxzax··on As a longtime BSD user, I have my doubts about our future
I hate to say it, but wouldn't a jail orchestrator essentially be the BSD version of systemd, docker, k8s and friends? The (admittedly few) BSD people I've talked to seem to be hostile to this concept because it's too much of a "Linuxism" but I don't think it has to be.
zxzax··on As a longtime BSD user, I have my doubts about our future
I didn't make that comment, I agree that comment could have been worded better. I'm assuming by the use of past tense they didn't mean to suggest that they are inherently problematic for life. Edit: I don't have any additional comments on this particular happening, I believe there was several other HN threads with more than 1000 comments where this was discussed extensively.
zxzax··on As a longtime BSD user, I have my doubts about our future
That's putting the cart before the horse -- in that context you would only see it used when the person's behavior already is super exclusionary. It's specifically used to describe that exclusionary behavior that has already happened. Of course people can get it mixed up but that's the job of the people doing the community management to make sure that doesn't happen.
zxzax··on As a longtime BSD user, I have my doubts about our future
For one, problematic refers to a behavior, not a person. If you find your behavior is causing problems for people, you can change that behavior (I encourage all employees/owners with a commitment to problem-solving to do this).

For two, when the word is used in the context of inclusivity, usually the problem is that someone is behaving in a way that's exclusionary -- it's not being nice to encourage them to continue that behavior.

zxzax··on Things you can’t do in Rust (and what to do instead)
It's not the same as C++ template errors. This is something that will directly cause a segfault in your code, that the Rust compiler is able to catch; AFAIK no C++ compiler would be able to catch that.
zxzax··on Things you can’t do in Rust (and what to do instead)
I just tried that in nightly and it seems to work? Not sure what the issue with that is.
zxzax··on Quake3e, a modern Quake III Arena engine
That's one of the reasons I won't do game development anymore, the industry as a whole is still very hostile to the idea of open source. I don't see that changing any time soon.
zxzax··on Guix 1.3
Again I don't think that's a correct assessment, Guix actually does have some overlap with systemd because they decided to put some containerization things there. In Nix, this would be delegated to systemd.

I also wouldn't say that that runs contrary to the GuixSD philosophy, as there are a lot of packages in Guix that are written in C and C++ and other compiled languages, and I don't believe they plan to replace them. Maybe I'm wrong about that? At some point it might be interesting to have a Lisp/Scheme-only distro. Of course the kernel would still pose a problem there.

zxzax··on Google Docs will now use canvas based rendering
I really doubt anyone is going to revive those old legacy widgets. That style of widget is flawed and predates MVC-style design, you'll find it becomes very impossible to present non-string data with that tree. Most applications now will want to show arbitrary widgets within the table, and for that they'll use the standard HTML/CSS. I would expect you can do something comparably fast by using a virtualized list in HTML, along with IndexedDB.
zxzax··on Guix 1.3
I don't know about other places, but here I don't agree that it wasn't for technical reasons. To me it seems like one of the key differences between them. Guix wants to have all the package and service definitions written in Scheme. Otherwise systemd would probably work well for them, judging by the usage in Nix anyway.
zxzax··on Guix 1.3
I can't say I agree with your assessment. As someone who has used both, there are a lot of nice things in systemd that aren't really present in GNU shepherd (yet?)
zxzax··on Use Alacritty instead of Termite
For Go, Rust, Haskell, autoconf, CMake, you would invoke the meson and ninja commands as part of your build process. You can't use them in the same exact way as meson subprojects, but these are just shell commands. It's the standard way to build any project with an external build tool. Am I misunderstanding a requirement? For a static build deployed in a specialized situation, you would likely need a customized gtk build to begin with.

I think it would be worth asking if they could keep that libgtk_static around, for users who know what they are doing. Make it very obvious you are not creating extra burden on them for just your use case. The problem with an option to build and install is that it makes it so they have to support static linking in lots of other use cases, which it doesn't seem they want to do.

I'd be interested to hear if static linking GTK even has that many benefits. From what I have seen, the library may not play so well with LTO.

← PreviousPage 10 of 14Next →