Oh no!
Oh no!
The standard library is where project go to die.
Computer programming, regardless of language, is hard. The computer does exactly what you tell it to.
So are they really mammals?
Part of it might be that I’m often having similar arguments with the team I run about introducing dependencies.
Engineers have a tendency to want to use the perfect tool for a job at the expense of other concerns. It could be ease of maintenance, availability of the skill-set, user experience, or whatever. If there’s pushback it’s normally that they are putting their own priorities above other people’s equally valid concerns.
Often I’m telling people to step-back. Stop pushing, listen to the resistance and learn from it. Maybe I’m on a bit of a crusade when I see similar situations in open-source.
That’s where I assumed it was going.
Unlikely. You probably will injest the poison and die, and depending on if the poison also acts as a venom they may / may not.
It’s probably more accurate to say "Venoms are injected. Poisons are injested. "
I think for python tooling the choice is Python Vs Rust. C isn’t in the mix either.
people like and want to program in rust
I think there’s a survivor bias going on here. Those that have tried rust and stuck with it, they also like it. Far more people in the python community haven’t tried it, or have and not stuck with it. I like and want to program Haskell. I’m not going to write python tools in it because the community won’t appreciate it.
Tools should be maintained by those that use them. Python doesn’t want to rely on the portion of the venn diagram that are rust and python users because that pool of people is much smaller.
Those languages bring different things though:
Python is the language the tool is for
C is the implementation language of Python and is always going to be there.
Cython is a very similar language to Python and designed to be very familiar to Python writers.
Fortran is the language that BLAS and similar libraries were historically implemented in since the 70s. Nobody in the python community has to write Fortran today. Those libraries are wrapped.
Rust is none of the above. Bringing it into the mix adds a new barrier.
I don’t think it’s a dream of “everything in python”, but “python tools for python development”. It means users of the language can contribute to the tooling.
How about “To learn it to that level will take 10,000 hours I don’t have”? Does that make more sense to you?
“learn Rust” in this case is learn it to a level where all of the little behaviour around cross language integrations are understood and security flaws won’t be introduced. Expert level.
It’s not “I did a pet project over the weekend”.
…and people worry about the name of a git branch.
I’m trying to understand Git, but it’s a giant conceptual leap.
To start with, start with just using git locally. Don’t worry about GitHub or similar. Then git and SVN will work very similarly. The main difference is that you need to git add
files with changes inside before you commit them.
Once you’re comfortable with using it by yourself, then I suggest running something like forgejo
locally to be your own code server. Then you can play and learn how the two parts work together.
Generally, you need to give yourself a little time. You need to do the work. Be efficient…sure, but don’t try to force it to be quicker than the time you need to learn.
Right, so you just have a single step and then hand over to a proper script. I’ve seen many people try to put much more complex logic in there before handing over to a proper language.
Config is fine, but Yamls biggest problem is people use it to describe programs. For example: playbooks. For example: CI steps.
If YAML wasn’t abused in this way it would have a lot less hate.
I don’t view free-use models as open-source. Open-source means I can rebuild it from scratch and I can’t because I don’t know what the training data is, or have access to it.
The scale is the difference and who is harmed.
Billion dollar company losing $100. Who cares?!
Billion dollar company stealing from all artists in the world. We care.
Points 2 and 3. Basically make restrictions on normal user accounts which are fine for humans but that will make bots swear and curse.
Unless you mean “what should the registration process be” I think API keys via a user account would do.
Now now. Be a good little lemming and follow the crowd.