ell1e coding thingsIf you want AI slop free node.js, consider signing: https://github.com/indutny/no-slop-in-nodejs-core #fuckai #aislop #foss #llm #ai #antiai #node #nodejs #oss #opensource #linux #web #webdev #webdevelopment
Мейкпост@ell1e What are the stances of alternative JS runtimes about LLM patches, and of the engines powering them (V8 etc)? I was a fan of the SpiderMonkey-based GNOME JavaScript once, making a hack to have it run CommonJS modules from npm for my app's dependencies; an idea that @webreflection explored more thoroughly, making a better generic thing called cgjs. ES Modules and node-gtk eclipsed it unfortunately, though inevitably.
Andrea Giammarchi@makepost @ell1e node-gtk is a project too btw, but around this matter if it’s Matteo Collina submitting the PR I trust the PR good faith, review and intent … if it’s some OoenClaw randos filing a PR, I believe that’d be a waste of everyone’s time. Context matters in AI like in real life and a *no* as statement feels like a bad decision in the short to long term, imho
@webreflection @makepost I don't feel like there's any context that addresses copyright and moral attribution-violating concerns of having *any* LLM-written code or LLM-written text be part of your code base. (Studies suggest the productivity trade-off isn't worth it, anyway.)
So plenty of us think a universal "no" is reasonable until the dust settles.