Perhaps we should start making LLM- open source projects (clearly marked as such). Created by LLMs, open for LLM contributions, with some clearly defined protocols I'd be interesting where it would go. I imagine it could start as a project with a simple instruction file to include in your project to try to find abstractions which can be useful to others as a library and look for specific kind of libraries. Some peopl…
Give Django your time and money, not your tokens
21–30 of 184 posts
Re: Give Django your time and money, not your tokens
#22I love Django. Ive been using it professionally and on side projects extensively for the past 10 years. Plus I maintain(ed) a couple highly used packages for Django (django-import-export and django-dramatiq). Last year, I had some free time to try to contribute back to the framework. It was incredibly difficult. Difficult to find a ticket to work on, difficult to navigate the codebase, difficult to get feedback on a…
That ticket now just sits there. The implementation is done, the review is done, there are no objections. But it's not merged.
I think something is deeply wrong and I have no idea what it is.
Re: Give Django your time and money, not your tokens
#23[flagged]
> Django in particular is optimized for LLMs Meanwhile, a different take: Now, what we’ve been told about models is that they’re only as good as their training data. And so languages with gargantuan amounts of training data ought to fare best, right? Turns out that models kind of universally suck at Python and Javascript (comparatively). The top performing languages (independent of model) are C#, Racket, Kotlin, and…
Re: Give Django your time and money, not your tokens
#24Incredibly milquetoast. I would not like to work with anyone who goes against these points.
Re: Give Django your time and money, not your tokens
#25[flagged]
In that case I encourage you to build Django with your LLM of choice. Do what the Django team does, and be of service to the public! I challange you to prove that Django is sloppier than your LLM-Version
Re: Give Django your time and money, not your tokens
#26I love Django. Ive been using it professionally and on side projects extensively for the past 10 years. Plus I maintain(ed) a couple highly used packages for Django (django-import-export and django-dramatiq). Last year, I had some free time to try to contribute back to the framework. It was incredibly difficult. Difficult to find a ticket to work on, difficult to navigate the codebase, difficult to get feedback on a…
I picked up a change that had broad consensus and quite a bit of excitement over even by some core devs. That ticket now just sits there. The implementation is done, the review is done, there are no objections. But it's not merged. I think something is deeply wrong and I have no idea what it is.
Re: Give Django your time and money, not your tokens
#27Re: Give Django your time and money, not your tokens
#28Re: Give Django your time and money, not your tokens
#29Perhaps we should start making LLM- open source projects (clearly marked as such). Created by LLMs, open for LLM contributions, with some clearly defined protocols I'd be interesting where it would go. I imagine it could start as a project with a simple instruction file to include in your project to try to find abstractions which can be useful to others as a library and look for specific kind of libraries. Some peopl…
Moltbook meets GitHub? Sounds like a billion dollar valuation (sarcasm tag deliberately omitted).
Well let them put their money where their mouth is. Let's see what happens, see what the agents create or fail to create. See if we end up with a new OS, kernel all the way up to desktop environment.
Re: Give Django your time and money, not your tokens
#30I love Django. Ive been using it professionally and on side projects extensively for the past 10 years. Plus I maintain(ed) a couple highly used packages for Django (django-import-export and django-dramatiq). Last year, I had some free time to try to contribute back to the framework. It was incredibly difficult. Difficult to find a ticket to work on, difficult to navigate the codebase, difficult to get feedback on a…