I think another ace up Django's sleeve is that it has had a remarkable stable API for a long time with very few breaking changes, so almost all blogposts about Django that the LLM has gobbled up will still be mostly correct whether they are a year or a decade old.
I get remarkably good and correct LLM output for Django projects compared to what I get in project with more fast moving and frequently API breaking frameworks.
Companies have been doing that for a long time now. You're not a person, you're an ID number in the payroll database, that needs to produce more profit than you cost the company.
When you emigrate to another country, you're viewed much the same way as a non-citizen by the system.
Well, although this particular quote is from a book from 2010, Terry Pratchett had been writing about these kinds of problems for decades at that point too, so that fits. For example, in Reaper Man from 1991 shopping malls were invasive parasitical life-forms from another universe.
Even in your own country you’re viewed the same way, it’s just that your database entry has higher privileges. I mean this universally, no particular country in mind.
I relate completely. I usually solve it by sticking a post-it note on the screen so it covers my face in the call. It makes the calls feel a lot more natural and less awkward.
Probably, but I fail to see how that's relevant here.
This is not a "dataclass heavy" library in any sense, they just used dataclass in the examples to make them shorter.
Based on everything I see in the documentation, you should be able to use Pydantic models as well, or standard python objects, or anything else, as long as it has a method `def htmy(self, context: Context) -> Component`.
I can say without a doubt that I've had more touchscreens fail on me in my life than buttons. This is despite buttons being far more common for most of my lifespan.
YouTube deliberately tries to prevent background playback by using web APIs to detect when the page is no longer visible and pausing the video. The extension prevents YouTube from doing that.
They (or someone they hired) actually rewrote their whole app about a year ago, I remember seeing lots of people complaining about how much worse and buggier it got after the rewrite.
I have no idea if the back end was also replaced then or if the vulnerabilities were present in the previous version as well.
Not if you are on a phone or similar device, which lots of people are. Important info like that should never be only accessible by hovering a mouse pointer that may or may not exist.
I get remarkably good and correct LLM output for Django projects compared to what I get in project with more fast moving and frequently API breaking frameworks.
reply