4 ms·
> Shows what's really missing from these old projects Well that's kind of the opportunity there, right? Usually there are more modern solutions: - use GH acti
by barfbagginus 3y ago
> Shows what's really missing from these old projects
Well that's kind of the opportunity there, right? Usually there are more modern solutions:
- use GH actions to do multi platform / multi-compiler tests
- use modern packaging solutions (eg, convert setup.py to a Pep 518 style pyproject.toml)
- publish to package repos (eg, many python projects are not on pypi)
This kind of work was baffling to me before I started working with gpt4 - my main struggle was understanding existing solutions, reading the documentation of existing build and packaging systems, and troubleshooting complex error logs.
At first gpt4 simply helped me when my own reading inabilities kicked my butt. But then I got better at understanding existing solutions and proposing new work. Now I can describe things at a high level and give GPT the right context it needs to propose a good first draft solution. And I understand things well enough to manually validate the solution. On top of that we also go ahead and test the solution, and fix issues that come up.
As a result I'm simply not scared of build systems anymore, no matter how byzantine or poorly documented. I'm vastly more capable of completing improvements then I was a year ago, and have half a dozen major upgrades under my belt.
I don't think that this will ever work automatically given that even gpt4 still hallucinates and lacks big picture thinking and awareness of up to date best practices.
However I do see it as a huge Force Multiplier for our loose community of volunteers.
We'll have to break down the assumptions that GPT always hallucinates uncontrollably. That's simply not true - GPT4 usually hallucinates in ways that are easy to fix by checking documentation and running tests. It usually introduces less errors than I do if I'm new to a system, and with its help I can correct more errors than I can on my own.
I see it as a huge win, if we can educate people in the community.
- pas 3y agoYes, ChatGPT is a great learning resource, great for fearless exploration, and is available 0-24 and scalable (whereas the usual maintainers are, unfortunately more often than not, the diametrical opposite of these). The big elephant in the room problem is that software/tech/opensource is this Schroedinger's safest cat. Because on one hand we have 3-redundant hardware and independent implementations and we can go to the moon and back with it, and let it drive our cars, and we have LetsEncrypt, and browsers pushing for TLS1.3 everywhere, and Civil Infrastructure Platform with all the extended lifetime, Jepsen tests, and TLA+ and rewriting the world in Rust ... and on the other hand billions of people blindly download/open anything on their Android 6 device with expired root TLS certs and running unpatched Linux checks notes 3.18.10 ... WTF. Sure, that might not be the most apples-to-apples comparison (or maybe it's apples v2 to v42), but this is mostly the reality everywhere ... I have very good friends working in ITsec (from managers to bugbounty-reapers), and ... things are highly comical. It's the whole culture that's lacking. Sure, it's relatively new, a mere decade basically, so we'll see. (And incidents like this are definitely raising awareness, maybe even "vindicating" some people who boldly said fuck this shit upon seeing autoconf/automake/make/configure and started to write yet another build system.) All in all, the pressure is rising, which will probably lead to some phase transition, and maybe - if we are lucky - systems and platform with top-to-bottom secure-by-default engineering mindset will start to precipitate out of this brewing chaos. (And this might make it even less fun to do open source maintenance.)