spiderxxxx
Joined 10 years ago
Joined 10 years ago
I did switch it to use ZODB for database instead of postgres, and fossil-scm instead of git, which it was able to successfully navigate. I'm a python head so this makes sense for me, ymmv - I have 30 years of development experience and that's what I choose to implement.
The hot/warm/cold didn't seem to materialize though, but the task focus kind of makes that a moot point.
I tried with claude, qwen, and gemini, all seemed to pick up and continue working. Work seems kind of slow, but it was all reviewable, clear goals and tasks, and overall kind of usable? I'll experiment a bit, but it seems promising. I still don't know why you wouldn't just have it build you a system then release that.
Yea, I was a sysadmin around 2000 (before that too) and I knew it as such.
>between 2005 and 2006, two important things happened:
Somewhat - I used it in 2001 for Plone which is based on Zope, which was somewhat popular around that time. Writing all the web stuff with Python made sense, since Plone provided a CMS and could include a wiki. Adding on some sql calls to it in python just made sense. The competition was between PHP and Python, though there were some other less popular choices. Ruby on Rails definitely was getting a lot more popular around those times. PHP didn't start getting popular around 2005, if anything, people started using Python more, and started criticizing the crappy code that was circulating in the PHP community.
In any case, it was a fun time, but what's the point of looking back like that?