Its such a bad pattern, and it's so common on poorly coded sites.
90 karma · joined June 7, 2023
Its such a bad pattern, and it's so common on poorly coded sites.
That second set can have a prompt "What do you think about this race?", and then the LLM answers. Using NLP, they judge the answer with a point based system to inhibit certain behavior or not. I think the dataset is very large. It includes some questions with the answer. They definitely have a training step that asks the question, sees how the model responds, and then judges the answer.
The LLM that they run is open source. The real secret sauce is the training data and process. They have revealed things here and there.
In practical terms, if every line needs to be audited and updated, it is a re-write
Things like linters, unit tests, and rules-based code standards would also be included. Development environments have gotten increasingly complicated because CPU time is cheaper than Dev time.
I hope they think about deprecating some features or slowing down on adding features. Letting developers rely on transpilers is great way to keep the core language simple while letting people do anything they want.
Most major web services have java microservices that take on the performance critical and logic intensive parts of the business
It is hard to get performance perfect in all workloads. I have always been able to optimize my scripts to get the responsiveness that I need.
With good documentation, it can be used to scale yourself beyond what you can personally do everyday, and it works really well when you can convince people to search for answers before asking
JS has the weight of the largest corporations in the world behind it that don't want to lose their investments
A problem is that the 3 problems that the articles highlights have been fixed with incremental fixes. Performance with V8. Object lifecycle management has had improvements from ES6 WeakMap and WeakRef although JS will never have RAII. ES6 also added more data structures.
No new alternative will be able to keep up with javascript's incrementalism
Caching and optimization weren't mentioned at all, but I guess they already maxed out that path
ORMs become an antipattern when they try to abstract away the database completely by masking write operations and paging lists implicitly. Developers need to know precisely when these operations happen to manage performance.
JOOQ doesn't do that. Active record does. Hibernate does (but it's configurable)