Readit Newsayjay_t commented on Jeff Bezos' revamp of 'Washington Post' opinions leads editor to quit npr.org/2025/02/26/nx-s1-... · Posted by u/layer8
Do you think Bezos has it in mind to take on those oligoplies when he changes the editorial focus to promoting free markets?
It's not the worst reach
ayjay_t commented on Users don't care about your tech stack empathetic.dev/users-dont... · Posted by u/merkmoi
This argument always feels like a motte and bailey to me. Users don't literally care what what tech is used to build a product. Of course not, why would they?
But that's not how the argument is used in practice. In practice this argument is used to justify bloated apps, bad engineering, and corner-cutting. When people say “users don’t care about your tech stack,” what they really mean is that product quality doesn’t matter.
Yesterday File Pilot (no affiliation) hit the HN frontpage. File Pilot is written from scratch and it has a ton of functionality packed in a 1.8mb download. As somebody on Twitter pointed out, a debug build of "hello world!" in Rust clocks in at 3.7mb. (No shade on Rust)
Users don't care what language or libraries you use. Users care only about functionality, right? But guess what? These two things are not independent. If you want to make something that starts instantly you can't use electron or java. You can't use bloated libraries. Because users do notice. All else equal users will absolutely choose the zippiest products.
Said it better than I could. It's always a deflection from the fact that whoever is saying doesn't know anything about their industry.
ayjay_t commented on A year of uv: pros, cons, and should you migrate bitecode.dev/p/a-year-of-... · Posted by u/bertdb
Can someone explain a non-project based workflow/configuration for uv? I get creating a bespoke folder, repo, and uv venv for certain long-lived projects (like creating different apps?).
But most of my work, since I adopted conda 7ish years ago, involves using the same ML environment across any number of folders or even throw-away notebooks on the desktop, for instance. I’ll create the environment and sometimes add new packages, but rarely update it, unless I feel like a spring cleaning. And I like knowing that I have the same environment across all my machines, so I don’t have to think about if I’m running the same script or notebook on a different machine today.
The idea of a new environment for each of my related “projects” just doesn’t make sense to me. But, I’m open to learning a new workflow.
Addition: I don’t run other’s code, like pretrained models built with specific package requirements.
`uv` isn't great for that, I've been specifying and rebuilding my environments for each "project".
My one off notebook I'm going to set up to be similar to the scripts, will require some mods.
It does take up a lot more space, it is quite a bit faster.
However, you could use the workspace concept for this I believe, and have the dependencies for all the projects described in one root folder and then all sub-folders will use the environment.
But I mean, our use case is very different than yours, its not necessary to use uv.
ayjay_t commented on Uv's killer feature is making ad-hoc environments easy valatka.dev/2025/01/12/on... · Posted by u/astronautas
I never used anything other than pip. I never felt the need to use anything other than pip (with virtualenv). Am I missing anything?
Yeah, I switched from pip to uv. uv seems like its almost the perfect solution for me.
it does virtualenv, it does pyenv, it does pip, so all thats managed in once place.
its much faster than pip.
its like 80% of my workflow now.