Some HNers already mentioned that the internet has not been a safe haven for a long time. All these vulnerability scanners and parsers were pinging my localhost servers even in mid 2k. It has just become worse, and even OSS and usually captcha-free places are installing things like Anubis [1].

All of this reminds me of some of Gibson's short stories I read recently and his description of Cyberspace: small corporate islands of protected networks in a hostile sea of sapient AIs ready to burn your brain.

Luckily, LLMs are not there yet, except you can still get your brain burnt from AI slop or polarizing short videos.

[1] - https://anubis.techaro.lol/

Did you forget the "\s" marker?

Russia is a one way step ahead here, with mandatory pre-installed apps, full-scale internet censorship (still catching up with China, though), mandatory DPI, etc.

Mind sharing why do you consider Java tooling to be good (and largely, what is good here)?

The reason I ask is that I recently had to join a Java project at my company, and having a background in Node/Rust/Perl/Lua and some C++, I found the Java tooling to be extremely unsuitable for my taste.

A simple example: there is no standard LSP server, and the amount of jumps required to have a working setup with FOSS tools and make it IDE-independent is just horrendous. In every other ecosystem I've worked with so far, it was pretty easy in the last 5 years: if you don't like IDEs, you can keep using your vim/emacs/helix or whatever and just embed a plugin or two, with LSP integrated -- and you're ready to go.

Java world felt complete the opposite, like you had to use/buy some commercial tools to start doing something.

Tooling goes way beyond the editor/IDE. Eclipse is a very good free option. As is IntelliJ CE. I personally have the all products pack and use the ultimate version.

Beyond the IDE you also have to consider the build tools, package management, debuggers, profilers, static analysis tools, etc.

It’s honestly too much for an HN comment. But as an example, if I do open one of these awful projects at work and it uses gradle for example, intellij will understand that, import the project, get all dependencies, let me run any target with debugging or profiling, give me code coverage, etc.

Thanks for sharing your experience.

It's a fair note about tooling in general, I started with the code editing because it's the first thing before you can taste and judge the rest.

I think my frustration comes from the fact that in most other ecosystem I can use the tools I like, but in Java I have to use things like Intellij.

Intellij CE may be open source, but it is entirely owned by a private business whose primary goal is to sell their product - which affects how well are the integrated, open to accept community feedback, etc.

There are several open source tools for Java (Eclipse, Visual Studio plugins, Netbeans and others).

The reason I don't use them is not because they are bad, but because IntelliJ is so much better.

I even use IntelliJ Ultimate for non Java code like React, even though Visual Studio Code seems to be de-facto standard for React developers and guides.

I guess it's just a given that everyone uses IntelliJ Ultimate. If you don't, I guess you're right, the tooling is lacking outside of that. But it's so worth it...

The eclipse language server works perfectly fine in vim/emacs/vscode/editor-of-choice.

I often notice that Linux (and maybe some BSDs) can accommodate two extremes on the tech competence spectrum especially well: the least opinionated users may treat their computer as a black box and just enjoy web browsing / chatting / media with some help, while the most savvy can extract value from tailored and private setups (like stability of Debian or power of Nix).

At the same time, Linux on the desktop fails often for everyone in between: the learning curve is still higher (especially for people coming from Windows), and some very specialized professional proprietary software can be missing.

Luckily, as mentioned in the article, Microsoft tries to make the balance more equal.

Writing this as a person who has used Linux for the last 15 years with a 2-year break for macOS and back.

> the learning curve is still higher (especially for people coming from Windows)

I don't think the learning curve is higher at all. It's roughly the same as with Windows. But if you're coming from Windows, the fact that you have to mount a learning curve for the new OS can be a real friction point. When most people learned Windows, they did so over time, without pressure. If you're switching operating systems, you likely want to become competent in it very quickly. That can make it seem like the learning curve is higher when, in fact, it's just that you're trying to run up that hill faster.

I agree with you per se that the learning curve in many ways is a function from your past experience, but there's no contradiction with what I previously stated in the context of this article - since émigré from Windows will obviously have some experience with Windows, they have this learning bias already, and potentially a different mindset/expectations (the most famous - why can't I just download an .exe?!)

Some [1] Linux distros were even trying to emulate this experience (which is a dead end obviously)

[1] Like Linux XP https://distrowatch.com/table.php?distribution=linuxxp

Thanks for sharing, I'll check it out! Lighthouse seems to go much further in extracting the feeds and even finds some likely variants by brute force or crawls for links.

For this browser extension I aim to have a small but curated list of ad-hoc derives instead of one-fits-all solution. This makes me wonder: if RSS is supported by a website but is not accessible at all, perhaps the right approach would be to simply ask the owners to provide access to it.

That all depends on how much time you have. Also, WordPress and other software create RSS feeds by default, so many people don't even know their website has a feed.

Pretty cool. I re-discovered RSS last year after getting tired of the usual mdoern "smart" feeds. For me, the only problem with independent small blogs is the discovery stage: you need to somehow to find out about an interesting blog, which is even harder if you want go out of your usual info-bubble.