Valve is generously providing backing for two critical projects that will have a huge impact on our distribution: a build service infrastructure and a secure signing enclave.

What is Tails?

and Tails, a portable operating system that uses Tor

I think using display: grid; as your default is the better default, so you’re all set. :)

You are going to get lots of downvotes, and this comment will too.

👀

Hahahahahahahahahahaha

(Pause for breath)

Hahahahahahahahahahaha

Was that tone really necessary? I would have liked your comment more without this part.

It baffles me when people use flex layout when it’s clearly visually a grid layout. Nothing here is flexing with varying element sizes and auto-fill-wrap-break of items.

A colleague of mine prefers flex too. But to me, grid is so much more intuitive and simple.

https://css-tricks.com/quick-whats-the-difference-between-flexbox-and-grid/

For me that’s the wrong way around.

I want to be able to fix the issues I see. I hate it when I can’t.

I’m thankful I am full stack and can do my stuff across borders. I hate the interfaces, waiting for stuff, or being hindered by dissatisfactory (to me anyway) stuff from them. So I’m glad when I have control over the entire stack - from talking to the customer to running production.

Anything I don’t have control over - most if it doesn’t get done, the rest can be okay or bothersome.

I hate that I don’t see what the admin set up and does on the infrastructure. It makes it harder to assess issues and potential issues and how they could correlate with infrastructure changes and activities…

so you put up a front?

I’ve tried out Linear (only peeked into it) and it’s the perfect contrast of performance against Jira.

I feel like Jira is not enabling me to use Jira either.

Jira Server is the on-premise Jira, right?

We had to change to Jira Cloud. (Vendor lock-in, mainly because of time-tracking appendix tools of that.) It’s horrendeous. UI and UX is horrendeous. The DOM is horrendeous. Performance is horrendeous.

My CSS Hacks to fix the UI to a degree I can reasonably work with it are a lot more work now with the generated DOM class and ids. Sometimes they at least have test IDs which can be used.

Some things, like the board component quick filter, are not even available anymore.

The interactivity functionality is irritating and annoying most of the time.

The browser extension we use further fucking up doesn’t help either of course.

Don’t even get me started on Confluence. Which can’t even find pages when I type the exact page title, or ranks them low. And editing tables is a hassle beyond belief now that responsive tables (self-sizing) are gone. It’s wasteful on space too of course, with huge spacing.

hard to compete against sunshine

I’m using Sunshine and Moonlight to stream my PC to my TV too

German-based SUSE just extended long-term support for Linux Enterprise 15 until July 2037. […] 13 years from now […] that’s […] 19 years after 2018, which is when Linux Enterprise 15 was first released.

pretty good

Time to migrate to Funnertoo

They wrote they’re using . as placeholder commit messages.

I use f for such [f]ollowup/[f]ixup commits, and a for [a]dditional code/components/changesets. Both keys are trivial to enter. When cleaning it up after, f commits are typically squashed into previous ones, and a commits get a description and/or serve as a base for squashing.

I can see . working well as well, but having a more obvious character (with vertical height/substance) seems preferable.

You don’t see the point of making use of shortcuts?

It’s just them with shortcuts, they didn’t see the point of m

😏

I haven’t seen information on that. Only speculations in comments here on Lemmy. I didn’t and don’t follow SUSE or this news closely though.

A commenter mentioned how SUSE has core business in hosting and business environment, while OpenSUSE userbase is more desktop and [non-paying?] end-user.

There wasn’t (to me anyway) strong arguments for why they do. Maybe they just want to get rid of the investment, and don’t see enough gain in the good publicity and it as an entry point to them anymore.

After years of support and collaboration, SUSE asked OpenSUSE to drop “SUSE” - their [SUSE] branding - from their [OpneSUSE] name.