sgt
Joined 7,850 karma
Segmentation fault (core dumped)
- sgtNote this comment: ... The stuff open source maintainers have to deal with.
- At this point I'd consider a cluster of top specced Mac Studio's to be worth while in production. I just need to host them properly in a rack and in a co-lo data center.
- Looks much better, thanks for that tip
- But inside that shit, tiny little gold nuggets
- I see. I'm quite impressed you were able to block those video ads in the first place. I thought they originated from the same domain as the regular videos.
- I don't think you can easily block those ads as they are part of the video...
- Interesting concept but kind of unintuitive to figure out without reading about it first. Maybe you can tweak it?
- Maybe you're just using the cached Sonnet.
- What's the cheapest eInk display one can get, like phone sized or tablet sized? I mean just for experimentation.
- Even in a lot of direct sunlight or leaving it out in the heat?
- Is Uber using Zig for other things by now?
- Such a legend! I bet he still has his Amiga somewhere in his Hollywood hills mansion.
- Mmmm, nothing like a crispy fungus burger!
- And they've been very safe, as far as I've heard. I think generally you can use common sense and be extremely safe all around the world.
Unfortunately there are some exceptions and I believe the highest risk area is India. A lady vlogger on motorcycle was recently gang raped there by 7 men.
- An extremely common thing to do. Also great with materialized views. I bet it's documented somewhere in Django's docs.
- Yes, absolutely. It's still pretty much that way. Especially if you want to make changes to a running installation, add nodes etc.
- I stayed away from Jinja2 ... was under the impression it has lower performance. But I could have been wrong all these years.
- Although we could say the same thing about Kafka, couldn't we? It's made for much higher throughput and has usually other use cases, but it's also great until it's not great.
- Also don't underestimate setting up e.g. views or materialized views even that you can use through the ORM to query. It helps a lot and allows you to combine fine tuning SQL with ease of use through Django, and get a lot of performance out of it. Just remember to create them in the migration scripts.
- Good to know. So no need for Django Q2 or Celery anymore either. I guess unless one has a specific reason.
Has there been discussion about adopting/embedding django-tasks into Django 6.x?