I agree that some public discussion place for patches is an absolute necessity.

No idea what that would look like for the blogger though, maybe Lemmy isn’t even that bad? You don’t even need a Lemmy account to interact, he could use Mastodon to respond.

But yeah the overall vibe of the blog is very much luddite and boomer.

100%! Often integrates better too.

I mostly mean from an advocate perspective, if a closed-source app developer doesnt want to build for Linux because the Linux desktop landscape is diverse and complex, you can tell them to just build a Flatpak and it will work and be installable everywhere.

That is a path of least resistance for developers which, I think, is leading to better app availability and compatibility for the Linux desktop.

I understand your perspective, but i am very happy that all these isolation options exist.

All those companies saying that developing a Linux app is too complex can just shut up and build a Flatpak.

Off-topic, but I recognise your name. Thank you for the Daily Diary App! I’m a huge fan, I use it every day for my gratitude routine.

Still, for those very hard bugs that everyone just hovers around and procrastinates, this is perfect advice!

This should be much more wide-spread. The hardest part of programming is reading someone else’s code.

More people should learn to do git rebase -i, it’s a simple way to re-organise your commits to make sure that they tell a story to someone going through the PR commit by commit. It only takes a minute and can save your colleagues so much time and increase the quality of the review process.

https://learngitbranching.js.org Is a very accessible browser game that I found useful on my Git journey to start to grasp the underlying structures and operations such as rebase.

I know my Pop!_OS install pulls Nvidia drivers and modules using flatpak. I don’t know the pros and cons of this method, but I’ve assumed it’s more robust due to decoupling of dependencies.

What is your opinion on flatpak vs pacman for proprietary Nvidia drivers?

This looks incredibly powerful and cool… but also like the kind of thing that may be a bit too niche or experimental for me to learn after just 2 years of the occasional casual Bash scripting and 4 weeks of having used zsh as my terminal.

I am trying to resist

Larger projects in Python (like homeassistant) tend to use type-hints and enforce them through linters. Essentially, these linters (with a well-setup IDE) turn programming in large Python projects into a very similar experience to programming a statically typed language, except that Python does not need to be compiled (and type-checked) to run it. So you can still run it before you have satisfied the linters, you just can’t commit or push or whatever (depending on project setup).

And yes, these linters and the Python type system are obviously not as good as something like a Go or Rust compiler. But then again, Python is a generalist language: it can do everything, but excels at nothing.

Not OP, but I very recently switched from bash. Autocomplete with suggestions is a way better exeperience on zsh than bash. The way you can choose between options of the autocomplete/suggest interactively feels way better than bash. I set it up to be case-insensitive, so I can type cd dow and it will become cd Downloads. Gettig autocomplete for both kubectl and its alias k is seamless in zshrc but requires an extra line with a weird dunder function in bashrc.

This is just what I found in a few days of using it. There was no learning curve at all, everything just felt easier.