Better? This is absolutely awful if you have more than a handful of directories and files. It just shows the top directories and excludes everything that doesn’t fit. Directory names are truncated if they don’t fit so it’s difficult to know what “ti[…]e/” is… And you get this weird XXXXX lump for small files.
gdu is a slightly “nicer” looking ncdu and much faster than this.
That was goddamn amazing.
I never found it that hard… But I also never expected to just know everything. Coding is life-long learning. People who see it as “a thing to learn once” struggle a lot more I think. They also start to fall behind at some point.
What exactly are you expecting to happen? Have you written code before?
God, this old argument… Careful, it’s an antique.
The idea is to minimize memory management and have people who are experts on it deal with it.
I did - it says he’s supporting rust in the kernel.
Why the swipe at Linus? He’s been supportive of rust in the Linux kernel.
The main use of wsl is often for things like docker, not as a “Linux desktop”. Microsoft has been getting killed by Linux in server environments. This lets developers stay on windows and build containers.
What reasons? They gave reasons? They just said that windows fixes the flaws Debian has which is quite the “compliment”.
ChatGPT - give me an example of what an insufferable Linux elitist would say about wsl.
“This article is not for Linux experts. If you are one and have a Windows machine (main reason is gaming), I hope you are using Debian for WSL and not Ubuntu.”
With all the hype surrounding Python it’s easy to forget that it’s a really old language. And, in my opinion, the leadership is a bit of a mess so there hasn’t been any concerted effort on standardizing tooling.
Some unsolicited advice from somebody who is used more refined build environments but is doing a lot of Python these days:
The whole venv thing isn’t too bad once you get the hang of it. But be prepared for people to tell you that you’re using the wrong venv for reasons you’ll never quit understand or likely need to care about. Just use the bundled “python -m venv venv” and you’ll be fine despite other “better” alternatives. It’s bundled so it’s always available to you. And feel free to just drop/recreate your venv whenever you like or need. They’re ephemeral and pretty large once you’ve installed a lot of things.
Use “pipx” to install python applications you want to use as programs rather than libraries. It creates and manages venvs for them so you don’t get library conflicts. Something like “pip-tools” for example (pipx install pip-tools).
Use “pyenv” to manage installed python versions - it’s a bit like “sdkman” for the JVM ecosystem and makes it easy to deal with the “specific versions of python” stuff.
For dependencies for an app - I just create a requirements.txt and “pip install -r requirements.txt” for the most part… Though I should use one of the 80 better ways to do it because they can help with updating versions automatically. Those tools mostly also just spit out a requirements.txt in the end so it’s pretty easy to migrate to them. pip-tools is what my team is moving towards and it seems a reasonable option. YMMV.
“personalized”
Yeah inheritance isn’t always the best solution. But even Java, the much maligned example for this, doesn’t do it for the i/o example you give.
Yeah. You’re talking about 0.0001% of the users though. For everyone else it’s “I don’t want to pay for this”.
That’s the oss model.
“Toxic” was the correct word choice, thanks.
deleted by creator
You know how many editor plugins I need to work with json? None.
Fuck Java, seriously
Toxic…
You can find a lot of good work doing Java.
I don’t look for apps based on what language they’re written in.
And I sure as hell don’t install apps that use “curl” to fetch an install script and pipe it to a shell. This practice needs to die in a fire.