Ah a classic stack overflow flavored answer ala: do it differently so you don't encounter these issues
747 karma · joined October 17, 2018
The performance bottleneck is whatever resource hits saturation first under the workload you actually run: CPU, memory bandwidth, cache/allocations, disk I/O, network, locks/coordination, or downstream latency.
Measure it, prove it with a profile/trace, change one thing, measure again.
Classic rug pull though
Reason is: while these models look promising in benchmarks and seem very capable at an affordable price, I *strongly* felt that OpenAI models perform better most of the times. I had to cleanup Gemini mess or Claude mess after vibe coding too much. OpenAI models are just much more reliable with large scale tasks, organizing, chomping tasks one by one etc. That takes its time but the results are 100% worth it.
Yeah, they're ugly, but in practice the choice isn't between clean and hacky; it's between shipping and not shipping. Real-world software runs on constraints, not ideals.
I think hijacked NPM packages are just the tip of the ice berg.
> SPy is not a "compiler for Python"
I think it's funny how it's confusing from the first paragraph
also: reminder that someone wasted his precious time creating an account and writing this ragebait comment just for a little bit of internet visibility
> document.querySelectorAll('*[class]');
tons of elements with class