Unless you need to work on a solution with more than a few projects, such as Unity games. Then the LSPs go haywire and eat 20+Gb of memory, while not actually working.

Which, ofc, is Microsoft’s fault, since it’s their analyzer that has had the bug for years now. Rider didn’t have that problem, but it shits itself when you change branches. You can’t win :(

Please, whatever you eventually choose to do, make sure to continually reference this amazing website whenever you are implementing any interactable part.

https://cheatsheetseries.owasp.org/

It has cheat sheets for securely implementing everything from login forms, preventing common vulnerabilities (at least look at sheets for Top 10), forgoten password flows, storing passwprds and more.

From the top of my head, If you are building it from a scratch without a framework, you will definitely want to at least look into cheat sheets about input validation, injection prevention, password storage, session management, file upload and authorization with authentication.

They are not that long, and should prevent the most critical and common vulnerabilities you will probably have, where the prevention isn’t too difficult, once you know about it.

The issue isn’t whether you can get a good results or not. The issue is the skills you are outsourcing to a proprietary tool, skills that you will never learn or forget. Getting information out of documentation, designing an architecture, understanding and replicating an algorithm, etc.

You will eventually start struggling with critical thinking, there are already studies about that.

Of course, if you use it in moderation and don’t rely on LLMs too much, you should be ok.

But how did that work for everyone with short-form content and social networks in the last ten years? How is your attention span doing? Surely we all have managed to take short-form content in moderation, since we knew the risks to our attention span, right?

I’m on mobile and youtube hates my VPN lately, so I can’t link it, but I highly recommend for everyone to go watch how does an exploding/penetrated battery looks like.

I kind of knew they are a fire hazard, but seeing one actually explode was way way worse than I thought. Exploding batteries are no joke, and everyone should see it at least once.

I really enjoyed my time with Nobara, and it was what made the switch to Linux stick for me, so I am grateful for the project.

But, I don’t get why would anyone consider Brave, with the many scandals they had, their failed attempts at extorting content creators for their own advertising crypto-scam and other advertising stuff? Plus, it’s chromium when we need to push firefox more, either Mullvad or LibreWolf.

Either it’s a really negligient research, or they got paid. It’s a shame. I already switched to Bazzite, so it doesn’t really affect me, but it’s sad to see decisions like this. I wonder what happened.

EDIT: I should have clicked the link instead of wildly speculating :D

Brave was not our first or immediate choice, however the decision to change to Brave comes after a long period of testing with various browsers failing in some way or another.

Firefox and firefox based browsers (such as floorp and librewolf) would incur a GPU crash when scrolling live videos (things like youtube shorts, tiktok, etc) with VRR enabled: https://gitlab.freedesktop.org/mesa/mesa/-/issues/12528

Chromium and Vivaldi both would break google meets with hardware acceleration enabled (however their flatpaks were fine)