HNHacker News
TopNewBestAskShowJobs

lavabiopsy

77 karma · joined September 4, 2021

submissionscomments
lavabiopsy··on Why Firefox has been in decline for 12 years
I'm sorry I don't understand. Is the problem that modifying computer code takes effort? If so then sure, that's true, but Firefox (or any other browser) can't be blamed for that.
lavabiopsy··on Why Firefox has been in decline for 12 years
I don't see how that's a problem, you can just modify the CSS. If you too decide that's too much work and consumes too much of your resources for not enough gain, well then now you know why Mozilla made the decision.
lavabiopsy··on What they don’t tell you when you translate your app
This is what the gettext contexts and the pgettext macros are for: https://www.gnu.org/software/gettext/manual/html_node/Contex...
lavabiopsy··on SystemE – A lightweight systemd replacement written in Emacs Lisp
>Regular initd + rc scripts are simple enough to be understood by everybody, which systemd is too complex to understand in the limited time we have

On a modern distro, I wouldn't say so, there is so much you would need to add on top of an rc script to get it to work correctly. Once you start trying to make use of the same capabilities it becomes just as complex as systemd, if not moreso. This is beyond just turning it into perl or javascript, I'm talking about OS-level features: for example even a basic Linux feature like mount namespaces is non-trival to do in an rc script and have everything get mounted and cleaned up correctly with all the right settings, whereas this is one or two lines in a systemd unit, and you know it's always going to work. It doesn't help much if you implement it in a shell script or in python versus having it in a systemd unit, this is code someone has to write, and if you say "it's too complex I don't understand it" then that would be limiting you because you're not using the intended security features of the OS. Does that explain it?

lavabiopsy··on SystemE – A lightweight systemd replacement written in Emacs Lisp
I'm not sure what you mean corruption, journald logs should actually fare better in terms of dealing with corruption and tampering versus text logs, if you use the log sealing feature. You could also already easily plug any of the syslog implementations in.
lavabiopsy··on The operating system: should there be one? (2013) [pdf]
This is the way these platform APIs are designed, you could theoretically make a screen reader that doesn't need that and just asks the app to recompute its state every time, but they don't currently work that way.
lavabiopsy··on The operating system: should there be one? (2013) [pdf]
The thing is those are likely to be simple GUIs. Those are a great use case for immediate mode. But try it with something that has a lot of:

- Wrapping text labels

- Widgets that are similar to CSS flexbox where the size of elements depends on other elements

- List/tree widgets or text editor widgets with large datasets in them

And then you will notice performance tanks. Think of trying to build a text editor that way, if you opened a 5MB text file, you would have to rescan the whole 5MB and compute reflow for it every time.

lavabiopsy··on Revolt: Open-source alternative to Discord
I believe mumble/teamspeak have a similar model to Matrix though, in that every room is both a voice channel and a text channel?

Maybe there should be another feature request to auto join voice comms when entering a channel?

lavabiopsy··on The operating system: should there be one? (2013) [pdf]
Maybe you want to help this person who is trying to integrate harfbuzz: https://github.com/ocornut/imgui/issues/4227

The other major thing missing in relation to that is input method support.

The problem with those type of APIs and accessibility is that implementing screen reader support basically means making it retained mode in some capacity, because accessibility APIs expect you to export a tree of objects and push state updates.

lavabiopsy··on The operating system: should there be one? (2013) [pdf]
This affects all GUIs, if you have a lot of elements then you have to be careful not to propagate complex updates through the whole tree because it kills your performance. There are various tools to deal with this, one of them is making it retained mode, but I would say basically all of those tools come with more footguns in that the GUI can easily end up in an inconsistent state. That's what you trade for performance.
lavabiopsy··on The operating system: should there be one? (2013) [pdf]
IMO, Dear ImGui is great for its original purpose (debugging GUIs, simple demos), but once you start adding complexity, custom layouts and custom widgets on top of it the state tracking gets to be just as bad as retained mode if not worse. Unless there was some best practice that I missed, one has to take great pains to avoid re-running the layout multiple times per frame, whereas a retained mode GUI would be able to handle that easily.
lavabiopsy··on The operating system: should there be one? (2013) [pdf]
That's true for "Linux", but "Linux" on its own is not a desktop OS. If you target KDE then Qt is the ubiquitous standard with decent performance and a predictable look, same goes for GNOME with GTK. Both of them I would say are less "bloated" than win32 or cocoa at this point. And I don't have any comment on whether it's "ugly" or not :)
lavabiopsy··on SystemE – A lightweight systemd replacement written in Emacs Lisp
Journald doesn't actually parse the log strings. Any parseable entities are stored in separate fields (see `man systemd.journal-fields`)
lavabiopsy··on The operating system: should there be one? (2013) [pdf]
If you actually look at the commits, it's mostly fixing the build and tweaking it to work on modern platforms. My personal opinion after trying it, I would not suggest use of Motif or CDE for anything besides nostalgia, it has some serious usability issues. But if you enjoy it, more power to you.
lavabiopsy··on The operating system: should there be one? (2013) [pdf]
>Unix generally has the correct basis for the design.

I can't disagree with this more, Unix is broken in so many ways and its designs continuously cause me pain. I would not describe a modern Linux or BSD as "simple", maybe the core of it is, but to actually build a modern OS there are so many layers on top of it. And when you do that, the crumminess of the foundation really starts to stand out.

lavabiopsy··on SystemE – A lightweight systemd replacement written in Emacs Lisp
>I'd prefer it to be a separate independent component [...] with a different internal architecture [...] and a separate governance

Not sure I understand this, do you mean you would use something that had the exact same feature set, if the internal architecture was different and if someone else was maintaining it? What would be the point of that? Are there some performance or security improvements to the architecture that were suggested upstream that they aren't doing?

>narrower scope

Not sure I understand this either, the scope of journald is actually quite small, there are many syslog implementations that are bigger and have a lot more features.

lavabiopsy··on SystemE – A lightweight systemd replacement written in Emacs Lisp
>Text logs are easy to get at, I don’t need a special program to read

I've seen this type of comment a lot on reddit and I don't understand why people say this. You do not really need a special program to read the systemd logs either, in the event that journalctl doesn't work you can easily use `strings` to read the logs. Feel free to try it right now just for fun, the binary format of journald is actually extremely simple and well-documented and just stores the logs sequentially, it's not "encoding" the strings at all. Why would it need to? It's all fulltext data.

lavabiopsy··on Switching to the i3 window manager
I would take that person's opinion on smithay/anvil with a grain of salt as they are not a dev there. They are making steady progress so you can just check the code there. Maybe ask one of those contributors for their opinion?
lavabiopsy··on SystemE – A lightweight systemd replacement written in Emacs Lisp
It is trivial to disable systemd-resolved on any distribution, as well as making systemd-journald disable its logging to forward everything to syslog. I wonder what the GP post's difficulty was?
lavabiopsy··on Revolt: Open-source alternative to Discord
> By having a separate voice channel, it's implicitly broadcasting "these people want to talk".

Is that significantly different from making a new channel and labeling it "voice channel"? To me it doesn't seem to be, but I haven't tried it.

>It's also broadcasting who -is- talking

That sounds like a legitimate feature request, if it's not in the issue tracker already?

On the rest of your comment: thank you for the context, it was an interesting read, but I think I got what you meant with the first three sentences... maybe edit out some of that that if you file a github issue :)

lavabiopsy··on Notcurses 2.4
>Can OpenGL work in Notcurses?

Yes, this is quite easy to do with OSMesa, or with EGL_KHR_surfaceless_context. With the latter it will be hardware accelerated too.

lavabiopsy··on Notcurses 2.4
There are reasons for the changes in GTK, though you may not agree with them, if you are confused about some then feel free to check the release notes. Or you can ask and I may be able to explain.

But if you don't have any issues with motif and it works for you then that's great.

lavabiopsy··on Notcurses 2.4
I'm not sure what you mean? I would suggest to take a look at the release notes for the newest Qt or GTK for example, if you want to see what the purpose of various changes are.
lavabiopsy··on Revolt: Open-source alternative to Discord
I am not using any Matrix clients right now but I was referring to this GP comment by the Element CEO: "in Element, you can hit the voice or video call button in any channel (not just voice channels!) and it will spin up a voice/video conference in that channel"
lavabiopsy··on Revolt: Open-source alternative to Discord
I'm sorry, I don't understand why you are saying this? This would not be about me copying something or you using something, this would be if you had a feature request to Matrix or to Discord.
lavabiopsy··on Malware found preinstalled in classic push-button phones sold in Russia
>KillUserProcesses only makes sense in a single-user environment, where logging out is an active decision from the user.

I can't agree, IMO processes left over after a network connection terminating could be considered a security hole. That's up to the sysadmin how to set it up. I certainly don't suggest getting into the habit of launching long running tasks in an ssh session, a remote sysadmin could already very easily end your processes if they find you AFK launching things on a sensitive machine. Systemd just gives some standard tools to do that.

>Typically, logging out (intentionally or through dropped connection) sends SIGHUP to the active process, then recursively to all children. [...] The short-term drawback is that programs that correctly request to be long-lived are killed.

This is incorrect, traditionally SIGHUP only means that the controlling terminal was disconnected. What you are describing is only correct for a single login shell with no sub-reapers, on a modern setup there are other things besides logging out that will send SIGHUP, such as for example if you run your program in an xterm and then close the window, or if you are operating within a sub-shell, etc. SIGHUP provides no way to differentiate those conditions, plus some programs will overload SIGHUP to be a "reload config" command, etc. SIGHUP is just not a reliable way to do it, I would not describe that as correctly requesting to be long-lived. SIGKILL is unfortunately the only method the kernel provides to do a reliable cleanup.

>The long-term drawback is increasing dependence on systemd internals, code complexity, and lack of portability. In both short and long term, the drawbacks massively outweigh the benefits.

AFAIK there is no portable or simple way to do this, please enlighten me if I am missing something. Using daemon(3) and SIGHUP is not adequate here for reasons described above. Of course other init systems are free to create their own simplified implementation of systemd scopes, while skipping the Linux specific directives if they want. So it's not clear what your actual complaint is and what you mean the drawbacks are. Do they need help doing this? If so I would be happy to advise.

>in both cases, programs can persist, so there isn't a security benefit.

This is also incorrect, in the case of systemd scopes, you can further restrict the ability to create them with polkit or SELinux or similar. So you could make it so only tmux is allowed to start one for example. That would be one of the big benefits of having a real API for this versus just sending a signal and hoping the program is well behaved.

>The vitriol received in those threads was in large part due to systemd developers not recognizing those drawbacks.

I don't think that is warranted, systemd developers can decide for themselves the trade offs of their program. The vitriol is not needed and is in fact likely to weaken the argument. In any case there are several other inits to choose from with their own set of strengths and drawbacks, I suggest focusing on what choices you have rather than agonizing over the small decisions of just one of them.

lavabiopsy··on Malware found preinstalled in classic push-button phones sold in Russia
>Linux owners, were crying when trivial initd and trivial shell scripts, which are easy to read and understand in about an hour or two, were replaced by Systemd, which may take days just to read source.

Not sure I understand why you would cry about that, systemd is actually not a very complex project if you're used to low level C daemons. The most complicated part is the d-bus portions, but those are mostly a lot of boilerplate, and you should be understanding it anyway if you use a modern system with d-bus. Trivial initd and trivial shell scripts are also lacking in quite a bit of functionality compared to systemd, at least in my experience those would tend to grow until they became brittle and unmaintanable.

lavabiopsy··on Revolt: Open-source alternative to Discord
Ok but just for me as an observer, it's not clear what the actual UX difference here is. The discussion seems to suggest that the actual capability of the UX is in fact worse in Discord, and maybe not worth copying exactly if it causes a feature regression. It would help to specify exactly what you would like changed around, i.e. if there is a button that could change to make it more clear what is happening when you join a voice room, or something like that. It could turn out that this could just be a matter of some small cosmetic changes.
lavabiopsy··on Revolt: Open-source alternative to Discord
I don't understand, is there some reason you cannot idle in a Matrix room? Again I don't know, but for the sake of discussion it would be good to mention that.
lavabiopsy··on Revolt: Open-source alternative to Discord
I think that just elaborates on what was said previously, it's up to you how to set it up if you want the coupling or not.
← PreviousPage 4 of 5Next →