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.
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.
I’m actually surprised there is no specification. It’s how I thought languages were written: spec first, implementation later. Do RFCs serve this purpose?
That’s pretty cool, but terrifying as well. Can’t wait for somebody to go a step further and start writing proc macros (call it rusht
) to replace bash scripts with rust scripts. Actually, now that I think about it, not so terrifying. They can probably be debugged better, could be safer (unless someone starts publishing malicious proc macros), allow dependencies to be added to compose better scripts without relying on they system’s package manager, and so much more.
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.
Is that a problem with java? In fact, is it even a problem on github where repos are namespaced by user or org?
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.
I’d very much welcome a crates.io alternative that doesn’t require github and supports namespacing by username or org. The dependency on a proprietary platform rubs me the wrong way.
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…
Not sure I understand this. Is it a watch clippy
? Or a completely new tool? If it’s new, what does it provide over clippy?
Your post is nearly the epitome of Chesterton’s Fence. You don’t seem to understand why Rust looks the way it does, works the way it does, why it exists, what it’s used for, and what problems it solves, but you’re very happy (or not, which is probably why you wrote this post) to trash it.
There are many responses to your comments that explain things quite well, yet, from what I see, you do not seem to concentrate on those.
And what I quoted is just the icing on top. It looks very much like you have one style of programming and approaching problems (the PHP style of “if it runs, it’s good”) and apply it to every problem. You have used a hammer your whole life and every problem looks like a nail. You can build a good many things with duct tape, nails, and a hammer. It might all do the job well enough for your standards or purposes and at times it might even be the perfect tool for a task.
But now you’ve discovered a screw driver, tried to hammer in a nail, and gotten quite frustrated that it didn’t work well. Instead of considering using a screw, you have tossed aside the screwdriver and decided to yell expletives into the ether.
The ether has responded with explanations, but you have chosen to ignore them all and staunchly hold on to your “screwdrivers are shit” conclusion. Had you said “I’m just blowing off steam, don’t take this seriously”, that’s what it would’ve been. However, you seem quite serious. Or, as I said before, you’re just trolling.
Oh but in rust you learn more about computers/low level concepts, you’re just not good at coding”
Who cares? Coding is a tool to get shit done and I think devs forget this way too often, like if one works easier than the other why does learning lower level stuff matter?
This is pure junior energy. Or trolling, I honestly can’t tell.
You know that comment does nothing?
What did you actually do?
They can hire? I thought they were in danger of getting wiped out by legal costs. Have charges been dropped?
I bet this won’t have an impact on memory safety and interop means C++ compilers have to be stricter about memory layout and reduce unspecified edge cases.
Anti Commercial-AI license