HN user
In my experience, having worked at several large PSPs, it is Mastercard and Visa who are the morality police. Stripe are just enforcing the rules insisted on by them, and PayPal forgot about them 3 layoffs ago.
Your tells, are just someone’s good writing now in the training set. It’ll be a moving target with each model.
I use the humanize skill to clean up AI written work before handing it over to colleagues.
For me quickly scanning over the article, the fact that floating points were even presented as a possibility was an immediate red flag. And I pretty much stopped taking the rest of it seriously.
Sure but I would expect an exit of like 20b or just list and go public…
What the hell? That is so cheap? I would value this at least as much as cursor? What gives?
I don’t know if this take is just naive or dishonest…
building something people love can make you a billionaire, but most billionaires did not build something people love, and most people who’ve built something people love are not billionaires.
This makes me never want to work on large engineering teams ever again.
Makes the Framework Desktop look like a bargain.
Golang is an amazing runtime with a bad language, one that conflates simple with easy. I view it the same way I view Java: a fine choice for a corporation, but nothing to love. Although Java’s gotten a lot better lately.
Opencode has really bad cache stability issues that they seem uninterested in fixing at the moment.
Also when most of you income comes from your wealth, your income tax rate is effectively 0%…
So complaining about having to contribute to the society that gave the conditions for your vast wealth is going to get you 0 sympathy
But if you look at the node compliance tests, deno has better compliance now days…
What do you mean? The whole point of Ruby on Rails is the rails way? Also the problems you are describing are not new and the community settled on adding some sort of service layer
https://shopify.engineering/shopify-monolith http://sporto.github.com/blog/2012/11/15/a-pattern-for-servi...
I’ve always found Ruby to be way more readable, what keeps me using python is the depth of libraries is unmatched.
So unless you’re into burning tokens having AI generate untested libraries, I’d stick to using the most idiomatic tool for the problem you are tackling.
Tbh that is some engineering teams I’ve worked on…
These models are open and there are tons of western providers offering it at comparable rates.
I can not find a description of how it works on the site, magic hands daemons !
Cool story, but what runs when?
Fix them if needed, the OP’s point is that for a lot of applications it is not needed.
For most cases you will still be comfortably in the JVM/golang performance window.
Rust is great language, fighting the borrow checker sucks, don’t do it if you don’t need to.
Do you not value your time? Paying a 100 bucks for a Claude max subscription is well worth it
AI is pretty good at following existing patterns in a codebase. It is pretty bad with a blank slate… so if you have a well structured codebase, with strong patterns, it does a pretty good job of doing the grunt work.
I mean sure… but to me that is as likely as the official ui misrepresenting the info.
The read-only hesitation seems overcautious. If you’re genuinely using it read-only, what’s the failure mode? The tool crashes or returns bad data - same risks as the AWS CLI or console.
The “middleware layer” concern doesn’t hold up. This is just a better interface for exploring AWS resources, same as k9s is for Kubernetes. If you trust k9s (which clearly works, given how widely it’s used), the same logic applies here.
If you’re enforcing infrastructure changes through IaC, having a visual way to explore your AWS resources makes sense. The AWS console is clunky for this.
The fakes vs mocks distinction here feels like a terminology debate masking violent agreement. What you’re describing as a “fake” is just a well-designed mock. The problem isn’t mocks as a concept, it’s mocking at the wrong layer. The rule: mock what you own, at the boundaries you control. The chaos you describe comes from mocking infrastructure directly. Verifying “deleteUserById was called exactly once with these params” is testing implementation, not behavior. Your HashMap-backed fake tests the right thing: is the user gone after the operation? Who cares how. The issue is finding the correct layers to validate behavior, not the implementation detail of mocks or fakes… that’s like complaining a hammer smashed a hole in the wall.
Google had a good 10 year run, where the ads were genuinely useful, until the need of the public markets required and lack of competition allowed them to enshitify the experience to the current state.
I hope the same fate does not await ChatGPT but in the mean time I expect it to be a pretty good experience at first.
Comments it seems taken in bad faith
I mean the sort of user you are describing sounds like they’d struggle with PC gaming in general.
I've always maintained that microservices are more for scaling people than scaling systems.
But then they’ve not reviewed it themselves?
The lady doth protest too much. People see every AI limitation crystal clear, but zero self awareness of their own fallibility.