I remember having great fun in QuickBASIC. And my son enjoys Scratch.
Django code is much more fun to work with than Node, but I can't imagine developing something competitive in it in 2025 to what I'm developing in Node. Node is a pain in the butt, but at the end of the day, competitiveness is about what you deliver to the user, not how much fun you have along the way.
* I think the most fundamental problems are developer-base/libraries and being able to use the same code client-side and server-side.
* Django was also written around the concept of views and templates and similar, rather than client-side web apps, and the structure reflects that.
* While it supports async and web sockets, those aren't as deep in the DNA as for most Node (or even aiohttp) apps.
* Everything I do now is reactive. That's just a better way to work than compiling a page with templates.
I won't even mention mobile. But how you add that is a big difference too.
It's very battery-included, but many of the batteries (e.g. server-side templating language) are 2005-era nickel cadmium rather than 2025-era lithium ion.
I would love to see a modern Node framework as pleasant to work with, thought-out, engineered, documented, supported, designed, etc. as well as Django, but we're nowhere close to there yet.
You spell out a lot of examples, but all of them are purely technical. What is it that you can deliver to the user using Node that you cannot deliver using Django? This is a genuine question.
Man, the only true part is the async/web socket part (and it's most because of python and not django itself) ... you can do a lot, and by a lot I mean almost 99% of websites/apps out there, with django and it's 2005-era nickel cadmium features
The lithium-ion battery analogy seems fitting: When we're not careful about sourcing those modern batteries from a trustworthy supply-chain, they tend to explode and injure the user.
Amazon shouldn't sell returned products as "new," but as "open box."
The other way it happens is co-mingling. Some vendor sends an "open box" product to Amazon as new, or a fake product, and Amazon ships it out when sold by Amazon since it considers goods to be fungible.
I stopped buying anything which goes in my body from eBay, Amazon, and similar after receiving a premium food product with very clearly fake packaging.
Amazon broke in 2020, when most shopping went online. It never recovered.
I doubt it ever will. Trust takes a long time to earn, and a little bit of time to break. I had four or five incidents on Amazon, cancelled Prime, and I doubt it will ever make business sense for Amazon to get me back.
I do think there's a place for a competitor to Amazon right now which looks more like the old Amazon.
Starting one would be super-capital-intensive. It's not a lean startup. There's only a handful of organizations with the capital to do that, and I doubt any of them will, in fact, do it.
>I do think there's a place for a competitor to Amazon right now which looks more like the old Amazon.
If walmart plays their cards right, they can do it (I mean they did acquire Jet). Unfortunately they also seem to be OK with becoming a dropship frontend for aliexpress
Piracy -> Friendly ways to buy -> Unfriendly ways to buy -> Piracy -> ...
Unfortunately, giving money back to writers involves hopping through piracy. At that point, a new, consumer-friendly service will sprout up. Everyone will use it.
Over time, the service will want to profit-maximize, and will adopt anti-consumer techniques. Leading people to go to Pirate Bay. Leading to friendly services.
How many times has this happened, such that it can be called a cycle?
There are other possibilities, such as people simply not writing as much anymore, or higher quality writers existing the market due to lack of sufficient return.
Bad DRM led to Napster led to Netflix lead to a fragmentation of services led to a resurgence of piracy.
Similar thing happened with music, only rather than piracy, it landed on legal / free (e.g. Youtube). Youtube is just starting to do the consumer-unfriendly thing (but it's got a long ways to go before piracy comes out competitive).
Similar in books.
I'll mention: A lot of these are consumer-unfriendly in some ways (e.g. Netflix DRM), but friendly in others. $20/month for all the movies you can watch beats piracy.
Well, no. It doesn't. The comparison is to the A1000.
Toss in a 5060 Ti into the compare table, and we're in an entirely different playing field.
There are reasons to buy the workstation NVidia cards over the consumer ones, but those mostly go away when looking at something like the new Intel. Unless one is in an exceptionally power-constrained environment, yet has room for a full-sized card (not SFF or laptop), I can't see a time the B50 would even be in the running against a 5060 Ti, 4060 Ti, or even 3060 Ti.
> There are reasons to buy the workstation NVidia cards over the consumer ones
I seem to recall certain esoteric OpenGL things like lines being fast was a NVIDIA marketing differentiator, as only certain CAD packages or similar cared about that. Is this still the case, or has that software segment moved on now?
For me (not quite at the A1000 level, but just above -- still in the prosumer price range), a major one is ECC.
Thermals and size are a bit better too, but I don't see that as $500 better. I actually don't see (m)any meaningful reasons to step up to an Ax000 series if you don't need ECC, but I'd love to hear otherwise.
I'd be totally down with "content belongs to everyone."
The problem is when you steal my content, repackage it, and resell it. At that point, my content doesn't belong to everyone, or even to me, but to you.
* I'd have no problem with OpenAI, the non-profit developing open source AI models and governance models, scraping everyone's web pages and using it for the public good.
* I have every problem with OpenAI, the sketchy for-profit, stealing content from my web page so their LLMs can regenerate my content for proprietary products, cutting me out-of-the-loop.
The curve is getting steeper, yes. That's not a contrast to the "AI will replace programmers" rhetoric.
Steeper means: higher at the top. Lower on the bottom.
Right now, AI can do the job of the bottom large percentage of programmers better than those programmers. Look up how a disruptive S-curve works. At the end, we may be left with one programmer overseeing an AI "improving" itself. Or perhaps zero. Or perhaps one per project. We don't know yet.
Good analogue is automation. Mass-scale manufacturing jobs were replaced by a handful of higher-paid, higher-skilled jobs. Certain career classes disappeared entirely.
> If entire commit is generated by AI then it is obvious what created it - it’s AI.
This is not the case. The output of a compiler is 100% created by a compiler too. Copyright is based on where the creative aspect comes from.
I have had very little luck having 2025-era AIs manage the creative aspects of coding -- design, architecture, and similar -- and that's doubly true for what appears to be the relatively simplistic model in codex (as far as I can tell, codex trades off model complexity for model time; the model does a massive amount of work for a relatively small change).
However, it is much better than I am at the mechanical aspects. LLMs can fix mechanical bugs almost instantly (the sort of thing with a cut-and-paste fix in some build process from Stack Overflow), and generate massive amounts of code without typos or shallow bugs.
A good analogy is working with powertools versus handtools. I can do much more in one step, but I'm still in creative control.
The codebase I'm working on is pretty sophisticated, and I might imagine they could implement more cookiecutter things (e.g. a standard oauth workflow) more automatically.
However, even there -- or in discussions with larger models about my existing codebase -- what they do is in part based their creativity on human contributions to their training set. I'm not sure how to weigh that. An LLM oauth workflow might be considered the creative median of a lot of human-written code.
I write a lot of AGPL code, and at least in the 3.5 era, they were clearly trained on my code, and would happily print it out more-or-less verbatim. Indeed, it was to the point where I complained to OpenAI about it at the time, but never got a response. I suspect a lot of generated code will include some fractional contribution from me now (an infinitesimal fraction most of the time, but more substantial for niche code similar to my codebase).
So in generated code, we have a mixture of at least a few different pieces:
The entire mess isn't with data in databases, but on laptops for offline analysis, in log files, backups, etc.
It's easy enough to have a SQL query to delete a users' data from the production database for real.
It's all the other places the data goes that's a mess, and a robust system of deletion via encryption could work fine in most of those places, at least in the abstract with the proper tooling.
I remember having great fun in QuickBASIC. And my son enjoys Scratch.
Django code is much more fun to work with than Node, but I can't imagine developing something competitive in it in 2025 to what I'm developing in Node. Node is a pain in the butt, but at the end of the day, competitiveness is about what you deliver to the user, not how much fun you have along the way.
* I think the most fundamental problems are developer-base/libraries and being able to use the same code client-side and server-side.
* Django was also written around the concept of views and templates and similar, rather than client-side web apps, and the structure reflects that.
* While it supports async and web sockets, those aren't as deep in the DNA as for most Node (or even aiohttp) apps.
* Everything I do now is reactive. That's just a better way to work than compiling a page with templates.
I won't even mention mobile. But how you add that is a big difference too.
It's very battery-included, but many of the batteries (e.g. server-side templating language) are 2005-era nickel cadmium rather than 2025-era lithium ion.
I would love to see a modern Node framework as pleasant to work with, thought-out, engineered, documented, supported, designed, etc. as well as Django, but we're nowhere close to there yet.
reply