DEADMINCEDOS

I don't think the difference is that great. More like Paint.net.

Adding in python seems like it's a needlessly more complicated setup.

> My personal take on this subject is that Rust turns experts back into beginners and some devs react with hatred because of the fear this induces.

Those people are probably poor devs. Anyone who doesn't have the attitude and mindset to continue learning in something like software development which keeps advancing isn't cut out for that field.

I think you're right. The same way people have strong preference for Systemd, MacOS, KDE, Gnome, I3, Nix, Debian, Gentoo, Arch, etc.

So many different solutions. Most are preferred because of subjective reasons (although sometimes just poor reasoning period), because people think so drastically differently.

It's still amazing there is just no all in one solution for viewing and sharing media between people. Having to hook Sonarr/radarr whatever into something to track indexers than a client then some kind of all in one interface that might not even be a media player....

It's nothing to do with LaTeX. Anything you can make in Word you could make in LaTeX.

Or I just didn't have the issues you or others did. Tex distribution can make a point, also editor most likely.

> I probably would rule out LaTeX unless I had a reason to want to learn it.

The reason is that it's one of the best tools suited to this kind of work.

I've made sure all the most commonly used ATS systems can read the produced PDF without issue.

Typist looks interesting, although I've had no issues with LaTeX so no reason to change to something more niche.

There is no reason to mention it, though. It's like mentioned Ubuntu as being necessary for having made a resume.

It's not 100% spyware, but there is an unacceptable amount of advertising and telemetry, and trying to seize control from users.

You can learn to wrangle and beat it into submission, which is very doable, and make the compromise and switch to a purely open OS.

I don't know that this is the right way to solve the resume 'problem' - I think LaTeX is a far superior choice, yet the author pretty much dimissed it as a possibility.

For me personally, I found LaTeX to be the perfect solution. I have my resume tex setup so I can set toggles to define what gets output. E.g. applying for a manager position, I might keep it brief and more technical.

The resume is modular and can be updated by updating external txt files and not the LaTeX itself. It looks nice, is always consistent, has nice links, etc.

It's optimized for all the ATS nonsense it inevitably gets run through, it generates a PDF, and I've made it near impossible for recruiters to copy and paste and repurpose it without retyping much of it, and I have a tone of tech tricks in their like invisible text that automated systems might see.

If LaTeX itself is sufficient, I can't imagine needing to add in something like Nix and a webserver or how that would be better in any way.

Help change that by supporting open platforms over closed platforms. It's that simple. Put your money towards fairphones and pinephones and not iphones.