No, it's never promised unlimited — it's always had usage limits: 20× the usage of their regular Pro plan, with a limit of 50 sessions per month (a session being a 5-hour window), although I don't know if they ever enforced this.
I can’t find any indication it was ever sold as unlimited.
It always had limits and those limits were not specified as concrete numbers.
It’s amazing how much of the internet outrage is based on the idea that it was unlimited and now it’s not. The main HN thread yesterday was full of comments complaining about losing unlimited access.
It’s so weird to watch people get angry about thinking they’re losing something they never had. Even Anthropic said less than 5% of accounts would even notice the new limits, yet I’ve seen countless comments raging that “everyone must suffer” due to the actions of a few abusing the system.
Yeah the outrage is a little artificial and definitely premature.
Some facts for sanity:
1- The poster of this blog article is Kilocode who makes a (worse) competitor to Claude Code. They are definitely capitalizing on this drama as much as they can. I’ve been getting hit by Reddit ads all day from Kilocode, all blasting Anthropic, with the false claim that their plan was "unlimited".
2- No one has any idea yet what the new limits will be, or how much usage it actually takes to be in the top 5% to be affected. The limits go into effect in a few days. We'll see then if all the drama was warranted.
This is a rebuild of the antithesis of Tailwind on Tailwind. Bootstrap had this for decades (Daisy even copies the same semantic class names in some cases). Tailwind was supposed to break away from this, to specific actual styles directly, but looks like we're coming back full circle again. Why not just use Bootstrap?
Tailwind is already a full circle. It is essentially a toolkit for using CSS to emulate the pre-CSS era approach of putting styling info inside attributes on the markup (remember the HTML2 days of bgcolor and cellpadding?).
Yeah it's turning the crank another half turn. It's insane to me how the webdev ecosystem keeps reinventing itself over and over and over again, trying to solve their previous mistakes without ever reflecting on and learning from why those issues existed in the first place.
It's not a full circle, because you don't end up back where you started. Inline styles have many well-known missing features, like pseudo-classes and media queries.
Don’t forget it adds the “feature” of a build step that literally greps the source code to see which style shortcuts you used, or seemed to use, so it can render them into CSS definitions so they can be turned back into inline styles.
And why is that a bad thing? It might be the case that bgcolor and cellpadding stopped being used because they didn't support media queries for example, not because they were inline styles.
There was a 10 to 15 year gap between people ditching bgcolor and cellpadding for CSS1 and widespread browser support for CSS3 media queries (2011, when IE9 got support and Chrome broke 25% market share). So I strongly disagree that the migration was about media query support.
How does the version of Tailwind itself make difference? The look depends on what styles are applied using Tailwind, not the ability to specify styles. Think the problem is the most tailwind sites have a similar set of styles applied, most likely copies of the docs or examples. TailwindUI is a paid system, but yeah, could be a case of most of the defaults copying that.
I'm sorry. Brain fart. Replace Tailwind V4/V5 with DaisyUI V4/V5.
After re-reading double brain fart.
I misread the comment as complaining about DaisyUI. I then responded as if they were complaining about DaisyUI but ALSO accidentally used "Tailwind" in my comment.
If a human meeting had lot of silence (assuming it's between words and not before / after), I would consider it a very efficient meeting where there was just enough information exchanged with adequate absorption, processing and response time.
Please ask the agent to help write a workflow script (GitHub Actions yaml or makefile or similar) instead of using it as a runner - if you do that the release pipeline changes with each execution. You do not want a non deterministic release pipeline that's mostly correct. You want one that's checked in to version control and always does exactly the same thing, with all logs and artefacts recorded.
By all means use whatever AI agent you have to help set that up.
This is context based dichotomy, not a person-based one.
In my personal life, I’m curiosity-oriented, so I put my blog, side projects and mom’s chocolate shop on fully self hosted VPSs.
At my job managing a team of 25 and servicing thousands of customers for millions in revenue, I’m very results-oriented. Anyone who tries to put a single line of code outside of a managed AWS service is going to be in a lot of trouble with me. In a results-oriented environment, I’m outsourcing a lot of devops work to AWS, and choosing to pay a premium because I need to use the people I hire to work on customer problems.
Trying to conflate the two orientations with mindsets / personality / experience levels is inaccurate. It’s all about context.
I’ve only ever heard these sequentially so was interesting to read they need not be.
“while in the original system presented in the early Dharmasutras the Asramas were four alternative available ways of life, neither presented as sequential nor with age recommendations.”
Almost everything in Hinduism is not prescribed strictly because Hinduism is really an amalgamation of many separate beliefs systems / traditions / ritual / books, etc. which were followed by local cohorts.
That's why many books contradict each other. Some books prescribe an age and order for such steps, others don't, etc. They weren't meant to be all collected, all studied, and all chosen piecemeal by one observer. But over time it has evolved into a much different thing than when it started
I hope more people read comments like these and ask themselves: "What warrants these life suggestions? Are they justified? What would make them justified? What alternatives are there?"
There's an argument to holding on X money will let you make more money, therefore making your actual contributions larger / more valuable
You can more easily invest your second million than your first (Because you probably need that (Or at least a portion of that to live)
There's also no significant reason to start earlier (or later), unless you factor in dying as your stopping point, worthwhile causes aren't going anywhere
In my case with this load balancer, I think it's just badly written. I think it is set to hold ALL data until the server ends the connection. I have tried leaving my SSE open to send over a few megabytes worth of data and the load balancer never forwarded it at all until I commanded the server to close the connection.
The dev who wrote that code probably didn't think too much about memory efficiency of proxying HTTP connections or case of streaming HTTP connections like SSE.
There is a case to be made that they sold a multiple and are changing x or rate limiting x differently, but the tone seems different from that.