Eventually, painfully, slowly, we’ll move to memory-safe languages. It really is a good idea. Personally, though, I don’t expect it to happen this decade. In the 2030s? Yes, 2020s? No.
This. Unless the government starts introducing fines or financial incentives (like fines) to force the use of memory-safe languages, ain’t nothing gonna happen.
Maybe read the article…
Difficult? How so? I find compiling C and C++ stuff much more difficult than anything python. It never works on the first try whereas with python the chances are much much higher.
What’s is so difficult to understand about virtual envs? You have global python packages, you can also have per user python packages, and you can create virtual environments to install packages into. Why do people struggle to understand this?
The global packages are found thanks to default locations, which can be overridden with environment variables. Virtual environments set those environment variables to be able to point to different locations.
python -m venv .venv/ means python will execute the module venv and tell it to create a virtual environment in the .venv folder in the current directory. As mentioned above, the environment variables have to be set to actually use it. That’s when source .venv/bin/activate comes into play (there are other scripts for zsh and fish).
Now you can run pip install $package and then run the package’s command if it has one.
It’s that simple. If you want to, you can make it difficult by doing sudo pip install $package and fucking up your global packages by possibly updating a dependency of another package - just like the equivalent of updating glibc from 1.2 to 1.3 and breaking every application depending on 1.2 because glibc doesn’t fucking follow goddamn semver.
As for old versions of python, bro give me a break. There’s pyenv for that if whatever old ass package you’re installing depends on an ancient 10 year old python version. You really think building a C++ package from 10 years ago will work more smoothly than python? Have fun tracking down all the unlocked dependency versions that “Worked On My Machine 🏧” at the start of the century.
The only python packages I have installing are those with C/C++ dependencies which have to be compiled at install time.
Y’all have got to be meme’ing.
The bloody managers are the biggest problem. Most don’t understand code much less the process of making a software product. They force you into idiotic meetings where they want to change how things work because they “don’t have visibility into the process” which just translated to “I don’t understand what you’re doing”.
Also trying to force people who love machines but people less so into leading people is a recipe for unhappiness.
But at least the bozos at the top get to make the decisions and the cheddar for being ignorant and not listening.
This is a great initiative and I wish there were more orgs that did this. However, I’m now convinced that we need opensource licenses which stipulate remuneration when used for financial gain.
Even the creators of languages don’t know their own languages 100%. I wouldn’t even call them the limit. So, I’m good enough in my main language that a lot of code doesn’t surprise me. And I try very hard to write code that others can understand as well when in a team.
You know, if they used the PR workflow with a CI that enforced standardised commit messages, this could be quite easily solved? Forcing everything through a mailing list seems to create more work for maintainers…
You know that comment does nothing?
They can hire? I thought they were in danger of getting wiped out by legal costs. Have charges been dropped?
Is zig memory safe by design? If not, rust will “win”. Large companies aren’t going to hire for an unknown or unpopular memory unsafe language when they already have C or C++ - there’s just no contest.
Last I read, zig didn’t even have a standard string library. Unless that changes, it won’t even be a viable alternative to C/C++.
Edit: I checked and got this
the Zig language, like C, entrusts memory management to humans, placing full trust in human development. Zig then provides some memory safety checks to ensure memory safety. However, it still lacks the strict compile-time guarantees of Rust’s ownership system and borrow checker. Therefore, when writing Zig code, developers need to pay more attention to potential memory safety issues and ensure that errors and exceptional situations are handled correctly.
“Be nice”
No I want to be an asshole because I think they are assholes
“That’s not very nice”
don’t punch down
Wat?
Enjoy being rude on github then 🤷 I’m sure your reasons for being mean are justified and help the image of the opensource community 👍
Of course people are not happy with it.
Of course. I’m not happy about many things, but that doesn’t give me the right to harass somebody. Pointing out something politely is very different from jumping on a bandwagon and spamming an issue, or creating meme issues and meme pull requests. We should be better than that.
Is that really what we want? Anything slightly popular making a misstep to be hounded by an online mob?
You’re missing the point. I don’t really care about Winamp. It’s ancient and probably used by about 15 grandpas. The point is the behavior of the people in the issues and pull requests. It’s possible to be polite, but firm and bring a point across. Right now it looks like a pack of dogs barking around thinking they’re witty and clever for doing so.
Projects are not entitled to be received gratefully and respectfully if you treat open source devs like a disposable source of free labour.
Nobody’s forcing anybody to do anything. You’re not forced to contribute in any way shape or form. Winamp hasn’t hired anybody there to write code under bad conditions. Justifying bad behavior “because the other side is doing it” (which isn’t true btw) is just weak.
Have looked around lately? This isn’t github.
The open source community is really showing itself from the best side by harassing the devs of that repo. I’m sure the devs don’t regret publishing the code…
Sure, the license isn’t the best, but that’s no way to act. With such childish behaviour from contributors, I’d have just taken the code down again. Bunch of children.
Keyword being “shouldn’t”. C++ doesn’t care about that, it just hands you the loaded gun.
If an Arch linux user hasn’t told anybody they use it, are they really using it?
auto isn’t dynamic typing it’s just type inference.
I’m aware, but one of the big arguments I’ve heard about dynamic typing is “I don’t know which type it has when I read the code”. Well, auto looks just like var in that regard.
Lambdas are just a way of defining methods in place. It has nothing to do with callbacks.
Callback definition from wikipedia:
In computer programming, a callback is a function that is stored as data (a reference) and designed to be called by another function – often back to the original abstraction layer.
This is exactly what lambdas are often used for in C++.
The U.S destroying its own economy. Who could’ve asked for a better Christmas present? With Trump at the helm next year, it’s only a question of time before trade partners tell the U.S to fuck off and they stop ignoring decisions like these.
Anti Commercial-AI license