Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

This is not like IT where the Americans are completely dominant and clearly superior.

The European pharma companies are doing more than fine, despite their main market being heavily regulated and price-controlled.

The less charitable explanation is that US companies want to charge outrageous prices, and the American system let them to, so they do it.

That's what the USA are: a machine to prioritize profits over people. Sometimes it turns out fine, like for the startup scene. Sometimes it's terrible, like when lives at stake.

Other explanations sound like heavy copium to me.


Many of those European pharma companies do most of their work and make most of their money in the US.


While it's true that the exposure of top European firms can be often 50%+ of total revenue from U.S, that:

- Doesn't make them non viable without the American market, just less rich.

- Doesn't reflect the 5 to 10 times higher price Americans pay for the same drugs.

You can have a healthy industries with plenty of billions to be around and have decently priced drugs.

What you get in the US is uber profitable industries and people scrapping around.


Those European companies make most their profit in the US. They would be much smaller without access to the US market.


Maybe drugs, or these drugs, aren't the most efficient solutions. Shouldn't we direct resources toward more efficient ones?


There are a lot of bad health outcomes built into our society, yes, but by the time people are confronted with the health impacts of cars, agriculture subsidies, for-profit healthcare, etc. it is likely that drugs will be necessary to treat the very real, immediate problems which any given patient has. Reversing the subsidies for things like car-dependency would positively benefit millions of people but it’s a generational change, not something most individuals can do.


I agree about the significance of those large-scale changes; still ...

> Reversing the subsidies for things like car-dependency would positively benefit millions of people but it’s a generational change, not something most individuals can do.

Individuals frequently can chose to not use a car, of course. Still, it's not realistic for everyone or all the time, especially in a society built for automobile use.

> by the time people are confronted with the health impacts of cars, agriculture subsidies, for-profit healthcare, etc. it is likely that drugs will be necessary

My point is that there are other treatments for illness. I doubt it's a coincidence that this patentable technology is so relied on in a hyper-capitalist society; other countries with better health outcomes use far fewer pills, iirc. Who will fund the large-scale study that says a valuable pill is unnecessary?


> Individuals frequently can chose to not use a car, of course

To some extent, yes, but my point was that it’s not realistic for many people because we treat walkable neighborhoods like luxuries. If you wake up in your 40s with a bad back and cardio problems because you live in a suburb and drive everywhere, you can’t roll back the clock and build sidewalks, legalize density, or run decent transit and on average don’t have the money to move somewhere dramatically better.

I think a growing number of people, especially younger ones, realize this is unsustainable but it took generations to get here and it’ll take a while to change trajectories, too. If gas prices had stayed high in the seventies that might have gone differently but a huge percentage of American neighborhoods are designed to minimize physical activity and that’s often enforced by law.


That's what I meant by, it's not realistic for everyone and everywhere.

> I think a growing number of people, especially younger ones, realize this is unsustainable but it took generations to get here and it’ll take a while to change trajectories, too.

Urbanist movements, including walkable communities, are much older than this younger generation. I think within a certain segment - well-educated upper middle class, maybe - it's long had influence.

I think they need to bring those ideas to other segments of society, which they have a hard time doing.


I definitely don’t think that it’s new to the current young generation but I am optimistic that they might have enough political clout to actually make progress. My neighborhood narrowly avoided becoming a highway in the 60s so we have some older folks who have been fighting car culture since before I was born, but there were a lot of people who didn’t really care because it was more affordable in the past, but their kids are a lot more motivated because it’s so financially non-viable now.

In the United States, the other big factor was recognizing how much it wasn’t just car culture but racism driving things. Despite the current moment, I get the impression that a lot of people are more aware of how much avoiding sidewalks and transit was driven by racism and just hurt everyone.


>Maybe drugs, or these drugs, aren't the most efficient solutions. Shouldn't we direct resources toward more efficient ones?

Turns out all the low hanging fruit have already been picked, so the only "more efficient ones" left are stuff like gene therapy, which are absurdly expensive, but still theoretically cheaper than a lifetime of care. Unsurprisingly the high sticker price draws much backlash from the public and politicians.


> all the low hanging fruit have already been picked

What is that based on?

Also, I'm not talking about 'low hanging fruit' necessarily; only solutons that become cost effective for vendors if drug prices aren't so extreme.

There's reason to think there is low-hanging fruit: Research is incentivized for the most profitable solutions for the vendors, not the most cost-effective solutions for patients.


>Also, I'm not talking about 'low hanging fruit' necessarily; only solutons that become cost effective for vendors if drug prices aren't so extreme.

>There's reason to think there is low-hanging fruit: Research is incentivized for the most profitable solutions for the vendors, not the most cost-effective solutions for patients.

High drug prices also mean you can charge more for one-off cures. See, the gene therapy example above.


Can you tell us more? Espacially, how does they both fair with auth.


There is native middleware in Channels. I have it documented with a brief example in the documentation, and I also mention some security measures.


Why, because it's free?


And kill many apps, maybe even OSes.

When most of what a user can do can be done from one single UI, the low friction will win.

And since all the data must be sent to the service, and that a super intelligent AI analysis all this data, the spying that is already considered outrageous today will reach unprecedented level.

Now, associate that with the fact the last year people in charge of said systems kissed the ring of the power that be in the most disgusting way. Add what we learned about surveillance from 3 letters agency.

You get your dystopia. It's not an if now. It's a when.

We need to solve that problem now. Once we hit it, we will lose the ability to solve it.

And I'm not sure where you could go on earth to escape it.


The golden rule to understand the success of uv is to remind yourself how big and diverse the python community is. Your context is only a tiny fraction of the contexts in which python is going to be executed.

E.G: if you compare it to your machine, it's a different thing that if you compare it to a locked down corporate machines.

I have clients that have Python setup so bad installing all deps for a project takes... 18 minutes. Those are not crazy projects either. It's just the context that is bad. And you won't be able to change the context. But we are in talk to change the package manager to uv.

There are so many different setups that are different than yours. If you are a professional trainer, and you get a new group every week, having 12 people installing their env in a blink is a win. If you are a researcher and you want to download the top 100 pypi packages and attempt to install them, speed is a bliss. If you are a blogger and try a lot of new stuff for an article, it's great. If you are working at repl.io and you get millions of venv created every day, boy does that matter. If you are sysadmin in charge of deploying kub pods, you might be looking at serious savings. Etc.

Speed affects many things:

- CI runs

- AI iterations

- docker builds

- isolated builds over multiple versions of python

But it also unlocks some use cases.

E.G:

- uvx is great only because uv is fast. Because uv calls are virtually instants, using uvx feels like magic.

- "uv run --with" exist only because overlaying a new venv on top of the other is basically free. And it's a killer feature.

- You never create lock files in uv. Because the operation is transparently done in the background since it's so fast. I can't recall the last time I ran uv sync. Because uv run automatically call it, since it's so fast you don't notice. So you just skip the middle man and go straight to coding.

I was a big proponent of "speed is not that important". Until I got speed.

And then I realized I missed a lot, because they are things you just can't do if you are slow.


Without the sci-fi, if you take people with 10 to 12 kids, you have great accidental, natural, objective experiments here.

You can study those kids and compare them to the reported lifestyle of the parents at the time before their conception.


That's decent value considering the price of a vps is close for much more work.

The only difference is the bandwidth: vps in europe givr you 10 tiles that, unmeterred.

Very cool for training: I can make people log into those vm and deploy nginx just for learning.


Other design decisions that made uv fast:

- uncompressing packages while they are still being downloaded, in memory, so that you only have to write to disk once

- design of its own locking format for speed

But yes, rust is actually making it faster because:

- real threads, no need for multi-processing

- no python VM startup overhead

- the dep resolution algo is exactly the type of workload that is faster in a compiled language

Source, this interview with Charlie Marsh: https://www.bitecode.dev/p/charlie-marsh-on-astral-uv-and-th...

The guy has a lot of interesting things to say.


> real threads, no need for multi-processing

parallel downloads don't need multi-processing since this is an IO bound usecase. asyncio or GIL-threads (which unblock on IO) would be perfectly fine. native threads will eventually be the default also.


Indeed, but unzipping while downloading do. Analysing multiple metadata files and exporting lock data as well.

Now I believe unzip releases the GIL already so we could already benefit from that and the rest likely don't dominate perfs.

But still, rust software is faster on average than python software.

After all, all those things are possible in python, and yet we haven't seen them all in one package manager before uv.

Maybe the strongest advantage of rust, on top of very clean and fast default behaviors, is that it attracts people that care about speed, safety and correctness. And those devs are more likely to spend time implementing fast software.

Thought the main benefit of uv is not that it's fast. It's very nice, and opens more use cases, but it's not the killer feature.

The killer feature is, being a stand alone executable, it bypasses all python bootstrapping problems.

Again, that could technically be achieved in python, but friction is a strong force.


> Maybe the strongest advantage of rust, on top of very clean and fast default behaviors, is that it attracts people that care about speed, safety and correctness. And those devs are more likely to spend time implementing fast software.

people who have this opinion should use Rust, not Python, at all. if Python code does not have sufficient speed, safety, and correctness for someone, it should not be used. Python's tools should be written in Python.

> The killer feature is, being a stand alone executable, it bypasses all python bootstrapping problems.

I can't speak for windows or macs but on Linux, system pythons are standard, and there is no "bootstrapping problem" using well known utilities that happen to be written in Python.


For the latter point, you are blinded by your own competence.

Bootstrapping a clean python env is the single biggest problem for people that are not daily coding in python.

That's half of the community in the python world.

When you write sqla that's not obvious, because you know a lot. But for the average user, uv was a savior.

I wrote a pretty long article on that here:

https://www.bitecode.dev/p/why-not-tell-people-to-simply-use

We also discuss it with brett cannon there:

https://www.bitecode.dev/p/brett-cannon-on-python-humans-and

But the most convincing argument is to teach python to kids, accountants, mathematicians, java coders and sysadmin.

After 20 years of doing that, I saw the same problems again and again.

And then uv arrived. And they disapeared for those people.


> And then uv arrived. And they disapeared for those people.

I'm not arguing against tools that make things as easy as possible for non programmers, I'm arguing against gigantic forks in the Python installation ecosystem. Forks like these are harmful to the tooling, I'm already suffering quite a bit due to the flake8/ruff forking where ruff made a much better linter engine but didnt feel like implementing plugins, so everyone is stuck on what I feel is a mediocre set of linting tools. Just overall I don't like Astral's style and I think a for-profit startup forking out huge chunks of the Python ecosystem is going to be a bad thing long term.


> uncompressing packages while they are still being downloaded

... but the archive directory is at the end of the file?

> no python VM startup overhead

This is about 20 milliseconds on my 11-year-old hardware.


HTTP range strikes again.

As for 20 ms, if you deal with 20 dependencies in parallel, that's 400ms just to start working.

Shaving half a second on many things make things fast.

Althought as we saw with zeeek in the other comment, you likely don't need multiprocessing since the network stack and unzip in the stdlib release the gil.

Threads are cheaper.

Maybe if you'd bundle pubgrub as a compiled extension, you coukd get pretty close to uv's perf.


Why are you starting a separate Python process for each dependency?


Real thread are very recent and didn't exist when uv was created. So you needed multiprocesses.


No, I mean why are you starting them for each dependency, rather than having a few workers pulling build requests from a queue?


At least one worker for each virtual cpu core you get for CPU. I got 16 on my laptop. My servers have much more.

If I have 64 cores, and 20 dependencies, I do want the 20 of them to be uncompressed in parallel. That's faster and if I'm installing something, I wanna prioritize that workload.

But it doesn't have to be 20. Even say 5 with queues, that's 100ms. It adds up.


Using the -S (“isolated”) flag can maybe cut startup in half.


From the perspective on somebody who lived it:

- the first and MAIN reason is excellent windows support. Nobody wants to say this, but it was the first unix friendly community for a good scriting language to not shit on windows users.

- batteries included is frawn uppon today, but it was a BIG deal back then

- python had the best c integration system after lua and got the Numric lib because if that. It became numpy.

- it was dynamically typed, but strongly typed. No ===.

- optional parenthesis for ruby and symbols from perls were a repellant to many C and java users.

- the error messages were better than the competition.

- lisp shell without lisp

- docstrings and help()

- the packaging ecosystem that everybody craps on today was actually the best at the time. Ruby's was AWFUL at the time.

- one of the first scripting language with good namespace. Ruby could have been that but killef it with monkey patching for years.

- python found ground outside of the web unlike php, js and ruby very early

- python devs were willing to work with os devs to improve integration, and so linux and mac got system tools written in python

- django and twisted were amazing at the time. The dev server without apache was a killer feature

- google advertised they used python for the search engine and youtube. Then HN successes like reddit znd dropbox. It became so famous.

It was not inevitable at all. Just a collection of random stuff.


I just tried to match a URL against about a hundred patterns of various types (thanks to Claude code), expecting it to be a non-issue.

A hundred regex tests, for example, is generally very fast. A quick Python script made them run in 0.85ms. A hundred Flask router tests is 2.64ms.

So I had no reason to think this API would be slow. Surely matching a URL is a subset of generalized regexes and can only be fast? And given that routing is not an activity you do a lot, why would it matter anyway?

But the performances were atrocious: it took 8 seconds to resolve the worst-case scenario on Firefox, and it locked the entire browser UI.

Ok, note to self, stay away from the URL Pattern API.


For what it's worth, quite a lot of libraries don't use NFA/DFA style regexes and instead use something like PCRE, which aren't not necessarily linear in the worst case. I'd hope that URL pattern matching wouldn't need recursive backtracking or whatever, but probably quite a lot of the time people use libraries with the less performance implementations they're not intending to use those features either, so it probably wouldn't be the first time anyone accidentally make their matching way slower from this if that's what happened here.


...Eight seconds for a hundred matches? What does your code look like?


My bad, I should not read AI generated code while drunk at a xmas party. That's the total run time for 10000 iterations.

Average time for 100 tests is hence 0.8 ms. Completely normal, and absolutely acceptable, especially for an operation as rare as routing.

Letting my previous comment as-is for historical purposes. And to remind myself I'm a dumbass.


In the near future I fear there may be laws about “LLMing while drunk” after enough rogue LLM agents vibe coded while drunk cause widespread havoc. You know folks harassing exs or trying to hack military depos to get a tank.

Actually that’d be a fun sci-fi book.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: