Wait until you learn about debhelper.

If you use a debian-based system, unless you have actively looked at the DH source, the one thing that built virtually every package on your system, you do not get to say anything about “bloat” or “KISS”.

DH is a monstrous pile of perl scripts, only partially documented, with a core design that revolves around a spaghetti of complex defaults, unique syntax, and enough surprising side effects and crazy heuristics to spook even the most grizzled greybeards. The number of times I’ve had to look at the DH perl source to understand a (badly/un)documented behavior while packaging something is not insignificant.

But when we replaced a bazillion bash scripts with a (admittedly opinionated but also stable and well documented) daemon suddenly the greybeards acted like Debian was going to collapse under the weight of its own complexity.

ls -l /proc/xxx/{fd,syscall}

Camera pans down to resource locks hiding under the floorboards

You’re describing proper incident response but I fail to see what that has to do with the status page. They have core metrics that they could display on that status page without a human being involved.

IMO a customer-friendly status page would automatically display elevated error rates as “suspected outage” or whatever. Then management can add more detail and/or say “confirmed outage”. In fact that’s how the reddit status page works (or at least used to work), it even shows little graphs with error rates and processing backlogs.

There are reasons why these automated systems don’t exist, but none of these reasons align with user interests.

To be annoyingly nitpicky, how is “unnecessary” defined in this context? Whitespace is usually “unnecessary” but I quite like it for readability.

I broadly agree with you though, the W3C spec changes things.

> Clicks on <br>
> Example is <br />

The actual thing that matters is that the / is ignored so (unlike with XML I believe) you can’t self-close a non-void element by adding a trailing /. But “void elements should not have trailing slashes” is extrapolation on your part; the trailing slash improves readability and is kosher since it doesn’t act as a self-close.

I wouldn’t recommend sway to someone who isn’t actively looking for a tiling WM, I would recommend finding a good spotlight equivalent to use on KDE as that will still be less customization work than it would require on barebones sway (which is hardly usable).

It’s not as bad nowadays that apps yielded to GNOME’s bullshit. Back when GTK2 apps were still common… Urgh. Plenty of apps were broken without it for no good reason.

I like opinionated UX - I use sway - but GNOME’s approach is incompatible with “general use” and only works (for now) because of canonical’s weight and ability to impose their vision as the only vision.

Also they didn’t replace the tray with a better way to manage background apps, so they can suck a dick on the UX front.

The fucking system tray. Which literally every other DE and mainstream OS out there supports because some apps depend on it and break if it doesn’t exist.

Last I checked GNOME devs said “no, we will never support it, because we’ve DePRecATeD the tray in GTK”.

It’s functionality so basic I have 3-6 apps which depend on it at any time on my work machine. Anyone saying it doesn’t fall under “basic functionality” is either a GNOME dev or a troll.

The kind of farming that makes any money isn’t slow work.

It is, however, tangible work with tangible results. Unlike spending months changing the polarity of nanoscopic silicon structure for the non-appreciation of an utterly clueless salesperson whose braindead ideas will have left the world in a worse state than you found it despite anyone’s best efforts.

I should seriously get into woodworking. Kidding. Sorta.

Hahaha that’s what frontend devs think, but the backend requirements are just as vague: “Just make this button work”. In my example all the requirements would actually be figured out bit by bit over months, nevermind the prescience required to foresee future architecture-breaking features or scaling requirements. At least you can make a mockup and get instant feedback, flawed as it is.

On either side it takes experienced engineers to suss out actual requirements from customers/PMs. The main difference is that the backend (especially on the infra/devops side) is only accountable to itself if everything goes well, but ironically that means no-one knows or cares about the amount of engineering that goes into keeping PMs blissfully ignorant of the risks and complexity.

I love shitting on Fullstack devs as much as the next guy. However, sometimes it really just does make sense for an (often internal) product maintained by a one-person team, and it doesn’t have to mean that the organization doesn’t value them. I’ve seen it happen.

However I would not recommend it as a career path because it’s essentially impossible to tell what you’re getting into when you get hired. Could be what I just described, could be that you inherit the full responsibility for a 20 year-old perl+php5+xhtml+angularJS mess.
I think it can only truly make sense if you work independently and get to build projects to your own quality standards, assuming you manage to find a “scope is small enough that specialization doesn’t make sense” niche. This is very hard which is why in practice “full stack” tends to mean “master of none but good enough to get a product out the door cheaply”.

Real back-end requirements: when x, y goes in (in JSON-as-an-XML-CDATA-block because historical reasons), I want you to output x+y+z+æ+the proof to P=NP.

æ will require you yo compile x+y in CSV, email it to Jenny, who will email back the answer. She doesn’t quite know how to export excel sheets though so you’d better build a robust validator. No, we don’t know what æ is supposed to look like, Rob from Frontend knows but he’s on vacation for the next 8 months.

The request must be processed under 100 ms as the frontend team won’t be able to prioritize asynchronous loading for another 10 sprints and we don’t want the webpage to freeze.

And why does your API return a 400 when I send a picture of my feet? Please fix urgently, these errors are polluting my monitoring dashboard and we have KPIs on monitoring alerts.

COL is not anywhere near $50k/y ($4100/mo!) except maaaybe in some very narrow parts (basically just SV an Manhattan, assuming you want a decently large apartment). But in either of those places an engineer makes up for it by making $150k/y instead.

Also rich Americans have good insurance, I’m sure you could find an example of someone who had this happen but it’s basically a non-risk.

And if healthcare was the only problem, then Canada would be an option as well. Engineers there still make a shitload more than German engineers. Watch out for the real estate market tho.

Even then it’s a pay cut. I know some people who moved to NA, and egotistically it’s a sound decision because engineers there are on the right side of the wealth disparity ravine. Money’s good enough that you don’t need social safety nets. And if push comes to shove, someone making $100k/y can definitely afford health insurance and the occasional trip for medical tourism.

Now personally I believe in income redistribution so I’m happy to pay a lot of taxes in one of the most income-egalitarian countries in the world. But I’d make a shit-ton more if I lived&worked in Luxembourg or Canada.

I agree with what you’re saying, but you’re shifting the goalpost.

Everyone is cheering Wayland on, no one believes it’ll succeed

That parent comment (and other comments like it in these threads) are what I take issue with. You can make the exact same argument why people should stick with Windows and not bother with Linux.

This software has been in development for a long time and still doesn’t work for my niche usecase and this therefore UNUSABLE and DOOMED TO FAIL

• Actual Linux users, completely oblivious to the irony of that sentence

The fact that you had to explain this is the reason why tabs are inferior in practice. People just don’t get it and then in collaborative projects you get a completely misaligned mess because not everyone has the same tab size.

Why do you insist that my primary objective should be “culture and acceptance”? People, many/most of whom presumably queer, find the meme enjoyable.

Who are you to tell us to stop having fun in the name of conformity and that we should instead work to “win” the favor of the out-group?

This is a joke BY queers FOR queers. The goal is NOT to make cishets comfortable, or to teach them anything, or generally to cater to their feelings at all.

Is it so hard to understand that sometimes people want to feel seen? Why does it matter that “society” will take it badly because of tokenization or whatever the fuck? Are you even queer yourself or just projecting what you think queer people should want? Because I’m queer and I appreciate “haha non-queer thing but now queer” humor.
It’s not very high brow, but that’s just the nature of shitposting and I don’t go off on the tens of supposedly relatable dead horses that get beaten every day in meme communities either.

Boomer is a mentality, and “ok boomer” is a joke. No need to get so worked up lmao

I’m just pointing out that Gen Z is much more proudly queer and especially GNC (unlike millennials whocame to age in a world where the overwhelming majority of developed countries did not even allow gays to get married!) and we not care how funny you think the joke is since it literally does not apply to you (presumably). Did it even occur to you that those “gay pride jokes” of the 2000s you deride so easily were your generation’s queer people’s way of finding acceptance and community? That “pure comedic value” (as if that was a chemical element you could distill out of memes somehow) is not the only value some people find in memes?