Wonder if that’s more of a language thing. You got a handle on English so presumably get more news about the English speaking world. If I read Arabic maybe I’d have more exposure to Iraqi goings-on.

Presumably it loads comments when you visit a page. That would send a request with the URL to whatever service they’re running.

Sounds to me like an extension that by design tracks every Web page you visit.

That reminds me, I gotta restart.

Believe it or not, jail.

9 times out of 10 I prefer reading, but there’s some videos that are absolutely worth watching over reading. That said, I don’t really want to see talking heads. And I think people should include the channel/creator name in the title.

But as a reality check, I’m looking at the first page of this community and only see one YouTube link. Doesn’t really seem like a problem worthy of a rule.

Thanks for the info. For others curious, here’s a decent short intro to K3s.

Now I’m kind of wondering if this is light enough for integration tests.

So does this setup like a one-node kubernetes cluster on your local machine or something? I didn’t know that was possible.

You SWOT m8?

Basically just a pitch for Gemini. The problem with Gemini is that we could do all that now with the web. They’re just stripping features to enforce what they think the Web should be.

I kind of get it. I like the idea of a simplified protocol. No JS engines to be exploited. I like building small static sites and wish more people would.

But also, there’s a million reasons we moved away from plain rudimentary HTML and terminal browsers. Not least of which is interactivity and writability. You couldn’t create a Lemmy frontend, forum, or any kind of database UI using this protocol.

Shy of reading documentation like man pages, I don’t really see the value.

Shutdown is one word though.

That’s… what they’re looking for.

So where is the line drawn? What about the teens who want to lookup how to do an exercise correctly without getting injured?

From the article:

The platform will still allow 13- to 17-year-olds to view the videos, but its algorithms will not push young users down related content “rabbit holes” afterwards.

Libertarians about to get off on having gold mines in their garages.

It’s a well-documented fact that as people get older their fluid intelligence declines.

I’m quickly approaching grey beard status. I recognize that I’m nowhere near as fluid as I was 20 years ago but I make an effort. You have to continually practice fluidity and actively learn things lest you solidify and lose that skill like any other. It’s important to stay fluid because things change and change faster than we all expect.

At the level of organizational architecture, a culture of emphasizing fluid intelligence as the strategy for attacking problems and adaptation causes serious losses of efficiency, and hence fluidity at a higher scale.

Ensuring compatibility with greybeards’ brains is key to long term success, and that means respecting an upper boundary on the rate of tools change.

There’s some truth to that. PHP is still in use and Wordpress is still somehow a behemoth. But the fact is that PHP has fallen out of favor, isn’t used by new projects, and there’s less demand for people with that skillset. So as a dev, it’s important to recognize that tools come and go and be flexible.

This example doesn’t work as well with C/++ since that’s older than most people here (though the language has also gone through iterations) and likely won’t be going away any time soon. But still, in most cases you probably don’t want to use that language for general work. So you’ll probably have to pick up other things for your toolchain (and higher level) work which of course has changed a lot.

The good news is though, that it’s relatively easy to transfer core skills between most languages. Especially the ones with C-like syntax, which is most languages.

employment potential and learning are generally problems if you are young. if you are old, the time investment to learn a new language is generally not self beneficial as your time of employability starts to dwindle.

Middle age software engineer here. Very disagree. Hoping to code until arthritis gets me. My point wasn’t only for employment (more of a perk), but primarily self-improvement and improvement on your craft. The day I can no longer do that, that may be the end for me.

That said, I don’t know what Linux community should do about Rust adoption. I just wanted to point out that I think it’s very important for all devs to be able to embrace learning new things and expand and refine their skillset.

I never said anything about someone’s usefulness as a person. Their usefulness as a software developer was the topic at hand. Maybe it’s not your profession but a hobby but the point stands.

I think the very phrase ‘my usefulness’ is dangerous. Are we only worth something as drones?

And yet it’s drones that do one thing and only one thing their entire lives, never learn and grow.

Learning is key in this field. Being able to learn new things allows you to move from one thing to the next as needed. You also learn a lot from experiencing different things. Other ways of doing things, other points of view, other concepts that you may have not been exposed to before.

It also expands your employment potential and general usefulness. Knowing only one thing will severely limit your abilities.

“Learning something new” does not mean the thing you are learning is new. It just means it’s new to you. One of the best things you can do for yourself as a dev is to learn to be fluid and be able to adapt to new languages, protocols, and technologies.

+1 for LVM on LUKS