There’s varying takes on why folks prefer Gemini:

• HTML browsers are too complex. It is virtually impossible to implement a new one. We’ve got 2½ implementations, i.e. Blink/WebKit and Gecko, and that’s it. Yes, you can use Dillo or w3m, links and lynx to view simplistic webpages, but anyone, who actually wants to use the web with these, will quickly run into webpages they cannot view.
  With Gemini, you can use tons of clients, some of them even written in Bash, because it’s so simple, and you will not run into pages you cannot view.
• Burn the web. Some folks hold the opinion that the modern web is beyond saving, because advertisers control many central parts of it. Presumably, these days folks are also glad to be spared from AI-generated garbage. And again, you can create your own webpage that’s all smallweb with pure HTML and whatnot, but anyone who actually wants to browse these pages has an easier time finding them on Gemini.
• An own community. Of course, using a different communication protocol cuts off communication with most of humanity. But as a result, many folks on Gemini know each other and bother reading blogs that they might not have read on the HTTP side of things.
  Well, and through survivorship bias, folks on Gemini tend to be nerds who care about permacomputing and the like, so that also helps with finding folks that have similar interests, even if you might end up reading their gardening blog, due to the aforementioned point.

Yeah, expected this to happen sooner or later. If it takes close to 0 effort to generate something that people believe might earn them some money, then of course, they’re going to do it in droves.

Lots of simpler editors gained tab completion support over the last few years, thanks to the LSP protocol. I have it in Kate, for example.

I mean, I do have several years of experience, but I’m still curious to see what others think. 😅
Obviously, someone cares for these changes, otherwise they would not have been made.

But yeah, the larger headings seem like niche changes, which most devs will only see the advantages of indirectly, i.e. when a library makes use of it.

In terms of the stabilized APIs, .as_array() seems like it will come up at times, because you might have an API that demands an array (so with a fixed length, e.g. [u32; 4]), but you only have a slice or a Vec.

And fmt::from_fn() seems like it could be really convenient when you need different string formatting for a type in one particular place.

Alright, yeah, I guess, I should’ve formulated that differently. Basically, this map, which is also in the linked Wikipedia article:

Lactose intolerance isn’t an allergy. The body just lacks lactase in the small intestine for breaking down the lactose. Which means the lactose goes off into the colon unprocessed, where bacteria will gladly ferment it, which causes tons of gas to be released, which is what causes bloating and pain.

Additionally, to quote Wikipedia:

The unabsorbed sugars and fermentation products also raise the osmotic pressure of the colon, causing an increased flow of water into the bowels (diarrhea).

https://en.wikipedia.org/wiki/Lactose_intolerance#Causes

And really, lactose intolerance during adulthood is kind of the default. It’s only mostly just humans in Europe that started evolving towards adult lactose tolerance.

Hmm, they might’ve scrambled to add Recall et al, because those other features you named don’t particularly need to be offloaded. Except for maybe TTS, you’re not gonna run these in the background all the time. And if you need the occasional translation, it’s fine, if it takes a bit longer.

At least, I would’ve absolutely seen headlines à la “Microslop wants you to buy an expensive new PC – to do things your current PC can perfectly fine”.

They’re nonsense words used specifically for the rock paper scissors game. We do primarily call it “Schere, Stein, Papier”, though (“scissors, stone, paper”).

That’s the name of the comic series. 😅

I 100% understand the frustration. It can easily feel like you’re doing the maintainers a favor and they’re making this harder than it needs to be.
The thing is, though, from the maintainer side, it very often feels like you’re asked to do those contributors favors. You may not care for whatever feature they want to contribute, but then are supposed to put in work reviewing their contributions and possibly having to patch up their work, if it doesn’t meet quality standards.

And then, yeah, you start requiring quality gates to ensure you don’t have to put in extra work for something you don’t care about. But then may also end up putting hurdles in place, so that effectively fewer contributions show up asking for reviews. It’s an ugly solution, but frankly, it’s better than having contributors put in actual work creating a pull request and then you not having time to review it.

!dcss@lemmy.ml

The devs keep updating it with cool stuff. In the next update, there’s gonna be an orb, which you can hold in place of a shield and which auto-flashbangs your enemies when you get hit.
There’s also gonna be an orb which sets off explosions around you when you kill an enemy without attacking them…? Have not worked that one out yet, but it sounds rad as hell.

On the Linux side of things, I use KDE’s “Activities”, which are basically OS-level workspaces on steroids.
I set a differently colored wallpaper for each Activity and I have a translucent panel to make this wallpaper color visible even when windows are covering the screen and KDE can also set the application theme to use the wallpaper color as the highlight color.

So, long story short, I can group whole sets of applications windows into different colors, which is pretty cool. Although I can certainly also see the merit of using colors at a more detailed level.

Ah, did not know, it was also referred to as Soya Wadi. I know them as “soy chunks” or well, Wikipedia calls it TVP: https://en.wikipedia.org/wiki/Textured_vegetable_protein

Yeah, always found that weird as a junior. I basically never touched the main-function, because well, it set up some fundamentals and then called some other function or created some objects and then I was tweaking things somewhere below that.

Now that I’m a senior and taking over the lead of projects, I’m the person that touches the main-function and others generally do not. 🥴

It was implemented as part of the X11 standard, so the concrete program would’ve been X.org…

I believe, that needs to be turned off in KDE.

I’m not sure, if this actually turns of the copying or if it just turns off the pasting, but you could try turning off this setting:

Well, in case you need it in the future:

!linux4noobs@programming.dev

!linux4noobs@lemmy.world

They may have entered the profession thinking they wouldn’t have to talk to people, but I just want to point out that this is not at all what the profession actually looks like. You have to constantly talk to people, to work out the requirements that the customer actually needs and exchange knowledge with your team mates. If someone is not a team player, that is the absolute quickest way to get thrown out.

Dachte zuerst, so viel Geld ist das doch gar nicht. Dann ist mir aufgefallen, dass es nicht um eine Million, sondern 1000 Millionen geht. Was zur Hölle. Wollen die ihre Office Suite nochmal von Grund auf neu entwickeln oder warum brauchen die so viel Geld?

Yes, tarragon = Estragon in German.