HNHacker News
TopNewBestAskShowJobs

zxzax

603 karma · joined April 19, 2021

submissionscomments
zxzax··on Use Alacritty instead of Termite
>it's been a long time I've felt such an enormous disgust at the amount of neglect and arrogance that is being displayed there.

Please do not assume bad faith. Type-ahead has some confusing usability issues, such as that it only matches against the beginning of the filename, which from my reading is why it probably will not be brought back. The way forward is to help get the current solution up to par. I feel your pain, but giving up and reverting to old type-ahead behavior will only ensure that the issue never gets a proper fix. It's very hard to have a conversation about this when people assert that the real cultural problem is that a particular feature they want isn't implemented.

>Another point is that their Alt-Tab has a strange auto-grouping behaviour that totally breaks my workflow.

Has this been reported?

zxzax··on Use Alacritty instead of Termite
>They'll be taking similar stance as gnome devs and start telling users "it's not our bug", "report it to gnome devs".

I'm not sure I understand where that happened, the issue you posted is closed, and mpv has since implemented client side decorations.

>Surely zero code in client is the "simplest".

There aren't any zero code solutions, implementing xdg-decoration in the clients is more than zero lines of code. If you violate the spec and ignore the protocol requirement that the client must provide a CSD fallback then it's not a lot of code but again, you could also provide a library that allows clients to draw a prefab CSD around themselves in a very small amount of code.

>it also makes sure the decoration always works and behaves the same way in every application. It also won't stop working if the application freezes. Sure with a magical library that you managed to force on everyone at least the consistency and "not buggy" could be solved. But why is this necessary when others don't need it?

I've seen other ways those can be achieved without SSD. Implementing a good looking and good behaving SSD that works well with every app is not simple either, and it's always going to be necessary to solve that because the core problem of making good decorations is always the same.

>And I surely don't want to see, libkde-decoration.so, libgnome-decoration.so, libwhatever-decoration.so

The idea I suggested is for the library to load the relevant kde and gtk symbols with dlopen, so there would not need to be multiple libraries. This I believe is how SDL already operates under the hood for some things.

zxzax··on Use Alacritty instead of Termite
>Why would games, or non-gnome apps care about decoration?

I don't think they would which is why the low level toolkits like SDL are the ones that have to handle it. Unfortunately that's the way it is, libwayland is very barebones and doesn't have a way to draw decorations.

>this is not the only case where gnome devs just decide to be jerks.

Please do not assume bad faith and suggest that someone is being a jerk to you personally because they didn't implement a feature that you were interested in. This is a sure fire way to cause burnout and stress to open source developers.

>wlroots and sway developers are doing good work to try to bring wayland and its tools to same level as X11, but then we have these other groups that just actively reject anything that doesn't go along with their "vision".

I have seen wlroots and sway developers reject patches and features that don't go along with their vision too, so I am not sure what distinction you're trying to draw.

zxzax··on Use Alacritty instead of Termite
>I believe GNOME doesn't want normal users, but rather users that will always do what they want them to do, aka the Apple mentality.

I would not say this is true, GNOME just handles extensibility differently. If you want to help with this, please consider working on this issue: https://gitlab.gnome.org/GNOME/mutter/-/issues/1053

That would pave the way for GNOME shell extensions to implement window decorations (and other wayland extensions) in a way that doesn't burden upstream maintainers and make them have to support every custom wayland protocol that is only used by a handful of apps.

>I guess this is the kind of end user experience gnome devs want?

I can't speak for them but I think they would suggest that those low level libraries all collaborate on a shared library to implement nice looking CSD, that way there is no code duplication and no dependence on GNOME libraries. Another option would be for them to copy the approach used by firefox, and use dlopen to access gtk functions and draw the CSD that way when it's detected they're running in a GNOME environment. Such functionality could be put in a library and wrapped up in 1-2 function calls, to make it easy to use. SSD might be the approach used by other desktops, but it is not the only way to achieve this functionality, and it may not even be the simplest.

zxzax··on Use Alacritty instead of Termite
> I'm a lot less sure, and the lack of clear requirements makes me even less certain.

If you are interested to work on this patch, it wouldn't hurt to ask the maintainer for clarification.

>as evidenced by tilix showing interest in this patch set.

That's two of them, there are other terminals that use VTE.

>I think that the termite developer explained very clearly why the approach suggested by the VTE maintainer wouldn't actually solve the problem they were having

I don't think so, the termite developer is making that assumption before the new patch was even completed. Additional options could be added with the suggested approach.

zxzax··on Use Alacritty instead of Termite
> The issue is that Electron and SDL will fix this 10 years later, old apps will still not work.

The SSD in GNOME still works for X11 apps. For now the only path for old apps that need SSD is to continue using the X11 backend in Electron and SDL.

For GNOME, SSD was never in the plan with wayland, so this is not breaking compatibility with apps there because it was never supported.

zxzax··on Use Alacritty instead of Termite
Again this particular cultural problem was resolved a long time. Ubuntu and XFCE and GNOME have since all aligned on this matter. I see what you are trying to illustrate, maybe it was true 10 years ago, but it's not now. Cultures can change you know.
zxzax··on Use Alacritty instead of Termite
It doesn't look like it, I'm sure they would be open to patches to help out there.
zxzax··on Use Alacritty instead of Termite
I don't follow all the Wayland compositors but Enlightenment doesn't, and Weston matters here. If somebody really wants this to become standard, implementing it in Weston should be priority.

Every compositor library I've looked at also considers this optional, e.g. mir, qtwayland, wlroots.

zxzax··on Use Alacritty instead of Termite
Your first link is an issue that was posted over 10 years ago and was long resolved in other areas. It's not an illustrative example. I really wish people would stop trying to revive these ancient flamewars without acknowledging the current state of things (not saying this is your fault, but a little diligence always helps).

The second two links you're posting are again, the exception, not the rule. The vast majority of patches are accepted, you just happened to stumble across two of the contentious ones that got a big outrage response on reddit. Please go look at the other thousands of issues and MRs against GTK if you don't believe me, it's not just GNOME people filing those.

I would say I thoroughly agree with the last article you posted. There has never been a "Linux platform." It was always Motif versus KDE versus GNOME versus Enlightenment versus all the rest. Historically they only cooperated with each other on certain things. If none of them refused to cooperate, we would still probably be using Motif. We can come up with various reasons for why this fragmentation happened but placing all the blame for that on GNOME for going its on way doesn't make many sense when this fragmentation always existed.

zxzax··on Use Alacritty instead of Termite
Again if you actually read the bug report, it contradicts what you're saying. This patch was rejected because it created unnecessary work for terminals outside the GNOME project. The favored solution would help all terminals using that widget.
zxzax··on Use Alacritty instead of Termite
>Gnome is one of those projects that should be considered "free in license only". While the project is free to hack on as you wish for your own purposes, your chances of being able to influence the development of the main project are minuscule.

That's not been my experience at all. The outrage machine on social media tends to spread around the small handful of patches that do get rejected so they can get angry about it, but they never talk about the other thousands of patches that do get accepted. Go look through all the other MRs on the gitlab if you don't believe me. Yes sometimes patches get rejected, it happens in any open source project.

zxzax··on Use Alacritty instead of Termite
I don't see why you are saying that has something to do with some attitude from GNOME. There are several Wayland compositors that don't implement that feature.
zxzax··on Use Alacritty instead of Termite
I know it's fun for people to hate on GNOME but if you actually read the bug reports, the feature was not rejected. The patch was rejected in favor of a different way to implement the feature.
zxzax··on Why People Feel Like Victims
Walter, please don't say these things. I get what you're trying to communicate but there is such thing as a victim. You can be doing everything right and still have harm brought to you and your loved ones by circumstances beyond your control. People who lost their families in 9/11 or Hurricane Katrina didn't end up that way because they didn't have a plan or weren't busy.
zxzax··on Deep Diving into the Strengths of FreeBSD
>it was Karen Sandler who really pulled the strings

I would be interested to hear a source for that because I never heard of such a thing. I heard the exact opposite, that GNOME is still open to keeping things working on BSD. The latest version in FreeBSD is GNOME 3.36.

zxzax··on Facebook's Trump ban upheld by Oversight Board, for now
>The answer to [less knowledgeable people] misinterpreting words literally isn't to [simplify] our speech.

Yes, it is? For the biggest example, Have you ever done child care? Kids may not understand whatever complex metaphor you're trying to use, they're not "idiots" for being that way, that's your responsibility as the adult to explain what you mean to them or use a simpler phrasing. Some kids may not even be ready for the explanation and you'll have to wait until they're older to use the complex phrasing. Yes it's unfortunate that for some this pattern continues into adulthood but they're also not "idiots" for being that way, not everyone can be an English major.

zxzax··on Facebook's Trump ban upheld by Oversight Board, for now
Isn't that just proving the point? Powerful figures should absolutely be more careful when using words like "fight" out of context because a certain percentage of people may very well misinterpret that as a call to violence. The platform evaluating it in a certain way doesn't change what the rest of the audience is going to evaluate it as.
zxzax··on The Honest Troubleshooting Code of Conduct
>It combines the bad parts of an ad hominem attack with the bad parts of personal arrogance and negativity. Don't think your other teammates won't realize you've "blocked" a teammate. Some of them will react badly, and potentially see you as arrogant.

You are saying this as a senior engineer who is in a better position to do something else about being on the receiving end of those personal attacks. I respect that and I hope you are able to keep doing it. But that isn't the case when the abuse is continuing over a long period of time, that means no other senior person stepped up to do anything about it, and the people on the receiving either have to quit, or risk getting fired for "insubordination" because they filed a complaint against a senior employee. Playing the office politics game and trying to avoid the abusive employee is not sustainable, as you've acknowledged.

zxzax··on Will Linux phones stay around this time?
Just my experience, three people is not a big enough sample size for most projects. You will get very biased opinions if you go with that. That may be ok if you have a very niche project and you only ask some people in that niche.
zxzax··on Will Linux phones stay around this time?
If you're suggesting that this is done out of selfishness or intellectual fervor then I don't think that's true. I wouldn't say they "prefer" it but it's certainly easier and more economical for a skilled person to contribute to those tools because the developers and the users are the same group of people.

Once you decide you need to do user testing and hardware testing, the cost shoots up. You need to start procuring hardware and finding a place for it to live so automated tests can run on it all the time. That costs money. You need to bring in a lot more testers which requires project management and/or volunteer coordinators. Usually that costs money too. Everything you do needs to go through more stages of design review which also requires extra coordination and project management. These are real things you can have but someone's got to foot the bill.

zxzax··on Will Linux phones stay around this time?
>In a typical OSS project, no one can give orders. The programmers ignore any good design suggestions because they don’t recognize those, and implement their own crappy ideas instead. Sometimes while arrogantly dunking on the designer who tried to make a contribution. Consequently, UX quality is abysmal, and anyone who could fix that is driven away. I don’t see a solution to this.

Generally, going into an open source project as a stranger and suggesting to make architectural changes without expectation of pushback is not a good idea. Any change there is going to trample on someone else's workflow. You have to build up trust first before people see you as an authority, that is the solution and it's often the only one. It's worked for some projects such as the recent post about Audacity, even though it's a bit of an extreme example because the person was already established as a well-known designer: https://news.ycombinator.com/item?id=26995610

I don't blame the programmer for dismissing suggestions they don't understand but it's also not cool if you were "dunked on" so I'm sorry if that was your experience. Keep in mind that's still better than some, a lot of projects will just ignore suggestions completely if they figure you're just not part of their target audience, and they don't have the budget to expand that audience.

zxzax··on “Shared libraries are not a good thing in general”
I don't mean modules installed from cpan, this is specifically for things like Perl and Python modules packaged in Debian. On purpose, there is usually no way to install more than one version of those with the system package manager. Maintainers seem to be doing a fine job of keeping them up-to-date. One of the major reasons to do this is so packages that depend on those libraries actually DO get tested with updates and don't get neglected and stuck on some old buggy version.

There are a lot of reasons to prefer static linking, but to me the argument of "it means you don't need to keep your package up to date with bug and security fixes" never held up, from a distro point of view anyway.

zxzax··on “Shared libraries are not a good thing in general”
That is going back to the same issues with containers, where everything works just fine... as long as you build it from your own statically-configured repo and you rebuild the whole system every update. It's useless once you try to install any binaries from an external package source. And IMO, a world where nobody ever sends anyone else a binary is not a practical or useful one.
zxzax··on “Shared libraries are not a good thing in general”
>If one program on your system depends on a quirk of libfoobar-1.0.3, and another program on your system depends on a quirk of libfoobar-1.0.4, you're fucked. You can't have both programs on your system, and Linux distributors will simply stop updating one of them until the author magically fixes it, which happens approximately never.

I've not experienced that. If the package is maintained at all, then it will get updated. People are still somehow maintaining Perl 5 libraries and putting out bugfix releases, which are functionally equivalent to dynamic linking.

If it's not maintained, then of course it will get removed from the distribution, for that and for a number of other reasons.

zxzax··on Audacity Aquired by Muse Group
Again, musescore may already be involved with the CCP for contractual reasons. Basically all companies who do business in China are involved with them in some way. These things happen for reasons beyond their control, e.g. an investor sells everything off to foreign investors who then change the terms. If you're being careful, you have to assume they are already compromised. I don't apologize or make excuses, it's just basic safety. My view is that if this person is really worried about threats coming from a government, it would be wise to take those threats seriously. Github profiles are public, so it's not exactly hard for them to find this information.

Edit: I agree with you that if this musescore developer is lying about that, then that would be wrong of them. But I don't think I have enough information to make that judgement. So I think that's where we're disconnected. At least for open source projects, my view is to take any and all potential legal threats seriously until the matter is resolved with the lawyers.

zxzax··on Audacity Aquired by Muse Group
Again, they may be under a non-negotiable contract with a government to say that. The replies further down the issue seem to suggest that is the case. I don't defend the actions of the parties responsible -- But the fact is if there are no Chinese laws being broken, I don't believe you or I are in the position to make that judgement, or at least that case hasn't been made so far. If your concern is with an oppressive government, please don't attack people who are also being oppressed by that government, and please don't suggest people ignore potentially real threats that could get them arrested by that government. I agree with you, I don't want the author of this software to get in legal trouble.
zxzax··on Audacity Aquired by Muse Group
If the complaint is as easily dismissable as you say it is, without apparently even needing the consult of a lawyer experienced in Chinese law, then it seems no harm was done. The repository is still up months later, so that's where I'm giving credit to the repository owner. And obviously if the person is not a citizen of China then talks of investigation by the Chinese police wouldn't really be relevant, so again no harm done. The letter can be dismissed without needed to post it on Github and make an issue of it.

However I would still encourage open source authors to be educated on Chinese law and to avoid telling Chinese citizens to do things that could potentially get them arrested in China. If there is a real legal threat there it's irresponsible to ignore it. So in the end it's probably good that it was posted on Github.

Edit to respond to your edit: That's not my view. The issue is that the police have already been called by a different party. (or the equivalent of it, i.e. the company is contractually obligated to contact the government in the event of a violation, under threat of legal action from that government) The email appears to just be informing them of that fact. In my view, that is the only responsible thing to do. The only other option is to just not inform them, and have the police show up anyway.

zxzax··on Audacity Aquired by Muse Group
Maybe the company has more information than you do, we don't know that. I certainly hope anyone in open source feels safe to call the police when a criminal violation is happening, regardless of what it is. Again we can debate individual laws and individual enforcement actions, but comparing any laws or police anywhere to the mafia is nonsensical. Let's focus on the facts.
zxzax··on Audacity Aquired by Muse Group
This may have been an accident where the legal notice was sent out before taking the API offline. If that's the case I agree they messed up. The DMCA may not apply here.
← PreviousPage 12 of 14Next →