SQLite predates most of the things you'd use instead. Given that in any case they'd be the ones left maintaining the wheels, long after everyone else has abandoned them, it makes sense for them to use their own wheels.
I do not accept that there were no editors, that there is no way to render $(diff -u) in those editors, and that there were no encrypted chat protocols available in the year 2000 (which is the frame of reference in the "17 year history" in that same section)
I'm aware that I am just digging a deeper karma hole for myself, but I stand by what I said: I'm glad it works for them, and I'm glad I don't have to use a hand rolled editor to send around hand rolled diffs via a hand rolled Tk chat client via a hand rolled protocol
Do you mean the part where they use a tcl script to extract comments and function signatures into documentation as opposed to using something like doxygen?
Shame, adding tests, or at least some experiments would actually improve vibe coding by several factors. But perhaps it depends on what you are coding.
Better alternatives in the year 2000? SQLites raison d’etre is to be stable and safe. Rewriting a working solution is anathema to that goal.
SQLite predates most of the things you'd use instead. Given that in any case they'd be the ones left maintaining the wheels, long after everyone else has abandoned them, it makes sense for them to use their own wheels.
I do not accept that there were no editors, that there is no way to render $(diff -u) in those editors, and that there were no encrypted chat protocols available in the year 2000 (which is the frame of reference in the "17 year history" in that same section)
I'm aware that I am just digging a deeper karma hole for myself, but I stand by what I said: I'm glad it works for them, and I'm glad I don't have to use a hand rolled editor to send around hand rolled diffs via a hand rolled Tk chat client via a hand rolled protocol
I sure am glad I don't work under those conditions
I think we're all glad you don't work on things that require long term stability.
would you be as bothered if they were instead using perl?
Do you mean the part where they use a tcl script to extract comments and function signatures into documentation as opposed to using something like doxygen?
Vibe coders don't do test coverage. That's for old people.
Shame, adding tests, or at least some experiments would actually improve vibe coding by several factors. But perhaps it depends on what you are coding.
I would add note that TCL has a very comprehensive testing suite which makes it very easy to add test units.
https://wiki.tcl-lang.org/page/tcltest
Off-topic and nitpick: I just wish people wrote it as Tcl. When I say it out loud, I do say TCL, but in writing it is Tcl.
It's a fair point. I agree. TCL is now a known TV brand. My iPhone auto corrects it to TCL in capitals.
Yeah, no worries. I tell people the same when they say ADA instead of Ada. :D