Exactly. I’ve seen so much data destroyed silently deep in some bioinformatics pipeline due to this that I’ve just become an anti CSV advocate.
Use literally anything else that doesn’t need out of band “I’m using this dialect” information that has to match to prevent data loss.
No:
Just user Zarr or so for array data. A table with more than 200 rows isn’t ”human readable” anyway.
I think the “controversy” is just tribalism. I’ve never once witnessed a case of any of the negative adjectives thrown at the Rust community. They’ve always taken exceedingly fair and good-faith approaches to discussing any critique of the language.
Their snark is reserved for the weird “anti-woke” crowd that hates Rust for some reason.
I just use nushell’s builtins instead of wrangling with IFS and bash idiosyncrasies. It’s been years since I’ve corrupted data by parsing text wrong.
But even if someone doesn’t want that: apart from using it in legacy scripts, grep is just a strictly less useful ripgrep these days, no?
Nushell is pretty nice. It’s the good parts of “what Microsoft is doing”, i.e. real structured data in a shell-like language and real error handling.
It doesn’t. read the first words behind the link you posted:
Page Status: Outdated
Here is the actual one: https://packaging.python.org/en/latest/tutorials/packaging-projects/
Uv and pip do the same thing, uv is just faster.
Hatch has the same role as Poetry or tox: managing environments for you.
Applications should be packaged properly, in a self contained installer for exactly this demographic. It’s not Python’s fault that this isn’t common practice.
Sure, there was some hyperbole. Some people need some specific setuptools plugin or something. Almost nobody.
It’s not a standard, it’s built on standards.
You can also use Poetry (which recently grew standard metadata support) or plain uv venv if you want to do things manually but fast.
It’s fixed, and the python version had nothing to do with it. Just use hatch
No it’s not. E.g. nobody who starts a new project uses setup.py anymore
Because they just have their own brain chemistry as the basis of it whereas the above comment clearly states:
Rust has proven empirically that the tradeoff between performance and safety doesn’t need to exist.
Which is truth. And it’s much easier to base a coherent argument on truth rather than vibes.
He works on Linux where he controls the whole stack down to the metal and I love that for him, but other people have to call library code, and them debug that if it doesn’t work as they thought it would.
You’re right, of you have compete freedom, do that. If the place you want or need to go to is most comfortably reachable via rattlesnake road, bring boots.
In other words, if you don’t think the wasm landscape is mature enough to build a web thing with it, you are stuck with JavaScript, but you don’t have to rawdog it. I haven’t run in a single weird thing like this in years of writing typescript with the help of its type system, ESLint and a formatter.
That’s why they make sense in code and config files. JSON is neither, despite the insistence of far too many people to write configuration in it.