←back to thread

uv: An extremely fast Python package and project manager, written in Rust

(github.com)
741 points chirau | 8 comments | 23 Jun 25 16:27 UTC | HN request time: 0.002s | source | bottom
Show context
theLiminator ◴[23 Jun 25 17:43 UTC] No.44358222[source]▶
uv and ruff are a great counterexample to all those people who say "never reinvent the wheel". Don't ever do it just for the sake of doing it, but if you have focused goals you can sometimes produce a product that's an order of magnitude better.
replies(7): >>44358352 #>>44358435 #>>44358583 #>>44358604 #>>44360352 #>>44361046 #>>44362201 #
mort96 ◴[23 Jun 25 18:27 UTC] No.44358604[source]▶
Honestly "don't reinvent the wheel" makes absolutely no sense as a saying. We're not still all using wooden discs as wheels, we have invented much better wheels since the neolithic. Why shouldn't we do the same with software?
replies(5): >>44358832 #>>44358840 #>>44358965 #>>44361544 #>>44363481 #
simonw ◴[23 Jun 25 19:04 UTC] No.44358965[source]▶
When asked why he had invented JSON when XML already existed, Douglas Crockford said:

The good thing about reinventing the wheel is that you can get a round one.

https://scripting.wordpress.com/2006/12/20/scripting-news-fo...

replies(1): >>44359814 #
1. idle_zealot ◴[23 Jun 25 20:37 UTC] No.44359814[source]▶
You can get a round one. Or you can make yet another wonky shaped one to add to the collection, as ended up being the case with JSON.
replies(2): >>44360171 #>>44360730 #
2. simonw ◴[23 Jun 25 21:12 UTC] No.44360171[source]▶
What makes JSON wonky?

Personally the only thing I miss from it is support for binary data - you end up having to base64 binary content which is a little messy.

replies(2): >>44360686 #>>44362261 #
3. idle_zealot ◴[23 Jun 25 22:07 UTC] No.44360686[source]▶
Quoted keys, strict comma rules, very limited data types, are the main ones. There are a host of others if you view it through the lenses of user-read/write, and a different set of issues if you view it as a machine data interface. Trying to combine the two seems fundamentally misguided.
replies(1): >>44379739 #
4. psunavy03 ◴[23 Jun 25 22:12 UTC] No.44360730[source]▶
Insert the xkcd about 15 competing standards . . .
replies(2): >>44361001 #>>44396654 #
5. oblio ◴[23 Jun 25 22:50 UTC] No.44361001[source]▶
Standards do die off, up to a point. XML is widely used but the last time I really had to edit it in anger working in DevOps/web/Python was a long time ago (10 years ago?).

At this point XML is the backbone of many important technologies that many people won't use or won't use directly anymore.

This wasn't the case circa 2010, when I doubt any dev could have really avoided XML for a bunch of years.

I do like XML, though.

6. Myrmornis ◴[24 Jun 25 02:10 UTC] No.44362261[source]▶
Lack of comments seems like a big one seeing as it's so widely used for "configuration". It's a big enough downside that VSCode and others have violated it via ad-hoc extensions of the format.

The comma rules introduce diff noise on unrelated lines.

7. collinmanderson ◴[25 Jun 25 17:21 UTC] No.44379739{3}[source]▶
I consider JSON's very limited data types to be part of what makes it so good.
8. mort96 ◴[27 Jun 25 13:28 UTC] No.44396654[source]▶
Probably the world's most over-used and misused comic strip. JSON wasn't created as a response to a situation where there were too many data interchange standards.