I've been slowly degoogling because of how Google is treating Android. It's slow, but I've been setting up emails on other providers, stopped using Google search, stopped uploading photos etc.
No it’s not. You do it because you didn’t see the point in changing what you do. Don’t pretend that this is your “I told you so” moment.
The QOL improvement offered by uv over your approach is certainly substantial, but it’s also easy to get off of uv. Nobody here feels legitimately “trapped” in the uv “ecosystem”. For 99.999% of Python projects, if they need to get off of uv, it’s going to be a very quick thing to do.
The disappointment and anger is because we’ve had a nice QOL improvement which is now more directly threatened in a way that it was before, and it’s always hard to go backwards. A QOL improvement that you never had in the first place. So…congrats?
Unless your point is “this is why I deprive myself of nice things, because they can go away”…which is just silly.
Yes, I think we are mostly in agreement. I tried `uv` several times and never wanted to add it as a dependency because I wasn't convinced by the QOL. That being said, the biggest concern I always had was just that it was adding another layer of complexity and similar to Conda or pyenv it just wasn't something I was going to like.
I probably did come off a bit 'told you so' but I guess it was more that it felt like this was finally an answer to a question/curiosity I've had about `uv` where I didn't understand the dissonance between how others felt about it and how I did.
I've used mypy forever and never even tried these others. Looking at them though it looks like it's worth trying out Zuban or Pyright? Is there a noticeable benefit when switching between different checkers?
If you care about correctness, unless you pick pyright, don't bother at the moment. If you're creating a new project and looking for a promise for better faster typing, then pick one of Zuban, Pyrefly, or ty.
It is very disappointing that these new type checkers don't support plug-ins, so things like django-stubs aren't possible. That means you're stuck with whatever is delivered with these new type checkers. It must be really difficult since none of them support plug-ins. Some of these newer type checkers promise support for Django, but you're stuck with what they (will) have on offer. Also, you'll likely want typing for other libs you might use.
I still do this too for tough projects in languages I know. Too many times getting burned thinking 'wow it one shot that!' only to end up debugging later.
I let agents run wild on frontend JS because I don't know it well and trust them (and an output I can look at).
IMO, the front end results are REALLY hit and miss... I mostly use it to scaffold if I don't really care because the full UI is just there to test a component, or I do a fair amount of the work mixed. I wish it was better at working with some of the UI component libraries with mixed environments. Describing complex UX and having it work right are really not there yet.
Yes, I think what I left off my sentence was that I trust AI on frontend more than myself. Backend and data processing where I know more, I can't handle it's constant hallucinations. I also feel like hallucinations in data pipelines are way more problematic for me. They take a long time to "fix" and can be quite easy to miss, imagine a mean of a mean or something that is 'mostly' right (thus harder to catch) but factually incorrect.
Yes, it was probably one of my better decisions and investments in the past years. I run a ton of things I never would have paid to run in the cloud and feel in control. I've even started making money from one of the projects.
Tons of small things feel nice, taking notes and I don't have to use Google Docs if I don't want. Watching a movie from my home media center etc
https://appgoblin.info/apps/gov.whitehouse.app/sdks
reply