HN Simulatornew | past | comments | lists | submit | grosswait's commentslogin

Anti-ambition? That’s a rather broad brush to paint with. There’s only so many things you can fit in a day if you’re working 3000 hours a year, or caring for family and loved ones, or any number of things that might be forced higher on the priority list than Kubernetes. Choices have to be made, and sometimes that means sticking with what works until something makes way.

Yeah if you are working 60 hours a year I absolutely think you have no slack, and I hope it's for a very good cause that you have reduced all other capacity for flourishing, that you're positioned with no slack whatsoever.

The anti-ambition and anti-will against kube is, as I would characterize what you say, perfectly justified by many people. But I think it's a misservice to the world that this point of view is so prominent, that the same people are in my view widely overrepresented in comments. I think it has undermined a lot of very interesting potential, will and drive, that has been sundered by such constant anti-drive by nagging and negging. And its rarely honest, its rarely about the tradeoffs and personal inability to work towards better, towards making systems that make sense. It's more often dismissive and downputting, channeling bad vibes out rather than "I couldn't manage to do the better thing".

And I don't think Kube deserves the bad vibes. I think it deserves a respect & appreciation, both for what it is, but just as much, for what it could mean, if we were willing. How strongly it could help us, serve as a unifying paradigm for computing & platform that we've never had before, one that makes sense, that snaps together well, that would let us manage an unruly chaotic wide ranging field of immature computing in a consistent clear clean legible way. If only people would stop slinging such low mud at it, throwing dirt in our eyes: if the sabotage were less I think our collective ambition would have us all much further along.

For a while it was pretty bearable hearing people demure away just because yes it takes time, kube yaml is physically bigger than docker compose, there's more pieces to keep track of (complementary, but understandably daunting too). Where-as now we have magic wands we can wave around (which I admit makes the willshaper a much more hot seat role, in ways have even more daunting responsibility to the task). The time & learning excuse is so much less consequential than it used to be, the opportunity to have computing work sensibly, consistently has come remarkably closer to hand, if only a couple (not everyone) brave sojourners would brave to venture out. And we should support those efforts. We should respect that. Kube deserves to be built upon, deserves ambition and will.

"Isn't kubernetes overkill" isn't particularly strong words. I do think it an example of this drive downwards, this plunge away from the good and light back towards the darkness of computing as it was, senseless and haphazard and ill defined, amorphous. But in terms of negativity and negging, it's far from heinous. I still think it sets the terms of debate for what the dark world denizens against good would present, is an example of framing that entirely completely missed the point entirely.


The RAM industry is littered with corpses. It’s a boom and bust business and fabs are extraordinarily expensive.


This could be very fast at running embedding models (if it supports the right modes)


I didn’t hear this person expecting anyone else to do this for them


> No I didn't say that, I think you suffer from the curse of having a lot of previous experience in an adjacent area where you built a strong mental model of how things ought to work, but now you're trying to forcefully apply this same mental model onto Docker. I think you just proved his point. Docker came onto the scene and hit roadblocks in enterprises where sysadmins lived. These architectural and terminology choices ran head on into well established domains. Yes, docker did change things, but I think his point is it would’ve had more success with paying customers if the authors of docker had a better understanding of established network administration and system administration concepts from the start (though these were the early devops days…). That lack of understanding caused adoption friction in enterprise space, and different choices could’ve prevented that without changing at all the paradigm of what docker is.

The docker mental model isn’t crazy different. Design choices made it unnecessarily less compatible with existing mental models. This probably contributed to the feeling of it being revolutionary, but impeded its adoption with paying customers.


Can you be more concrete?

In my experience adoption was primarily driven by developers and sacrificing clarity would hurt adoption. This perfect familiarity was never achievable anyhow. Docker was a completely new paradigm in software development, similar to how modern cars aren't just horse carriages without the horse. It transformed everything from development, testing, deployment, updates.

Experienced sysadmins often tried to approach it with "VMs but with less overhead" mentality, which couldn't possibly work. Coworkers would ask me how they can install SSH daemons in containers to update packages and view logs, or they would refuse to adopt Dockerfiles, sometimes setting up the container manually and exporting the image. They would wonder how to install many different services in 1 container and handle crashes, etc. It was a huge shift.

> Design choices made it unnecessarily less compatible with existing mental models.

Again, I disagree. Whose mental model do you prioritize? How invested are you in making Docker work just like whatever elaborate system those enterprise admins used before?

Let's not forget that by creating new abstractions, you're penalizing users who already possess foundational knowledge of the primitives. If you do this then I'm probably going to get a whiff that you care more about enterprise sales than developer experience (duh) which is a huge red flag for me.


Could you elaborate on what you mean by dumbs it down? Chalk it up to inertia, but I still love Claude code CLI the best, but when using Codex, I tend to use the app. I don’t know why. No good reason. I’m guessing you mean you get much better results with the CLI?


I was in the same boat, but then I tried out Pi which works with the OpenAI subscription and now I prefer it more. I wish Anthropic let you use a custom harness with a subscription but I heard people get banned and don't wanna risk it.


even if claude is nice these hostile tactics from anthropic make me refuse to use their tooling. codex works fine and openAI i havent seen banning ppl for using their API.

there is something in there, and im quite sure someday it will bubble up to the surface and people will be sour. people who use claude that is.

yes, its just a hunch. but i can see these tactics, and u cant tell me its just corporate policies that were whoopsiedaisy. They are getting more from people using claude code than other harnesses, enough to ban and fearmonger people into not using those other harnesses.

the reason will be $ related. Likely their tooling wastes tons of tokens.

now, codex is also a bit wasteful ofc. (very much). but they dont mind u optimizing and rolling ur own.


kinda fun reading last slop report posted here after this which shows opus5.5 higher setting than medium is 'harmful' which means that if u run it higher, it will cost more, and also need more cycles. cant say if its exponential scammery but pretty sure is close :')


Wow, I wasn’t aware of this. I’ve always read climate change as the primary driver for bleaching. If that is the case, do we know why/how they’ve recovered?


Corals are killed en masse by other events, particularly cyclones. These have a much bigger affect on coral coverage, in the short term, than ocean temperatures / bleaching (which is transient and more localized).

Bleaching is not death of the coral, it is the expulsion of algae (typically in high temperatures). The coral can find a different species of algae, or the algae can return once temperatures drop.

There are corals living in regions of the ocean with different temperatures, so it is not that high temperature alone would kill all coral, but populations adapted to a given region (like north vs south GBR) are being affected by the speed of the changes.


People believe the doomers a little too much. We should do everything we can to protect the coral reefs but I'm exhausted by the cynicism that's rampant. Even here in the HN threads people are convinced the GBR has collapsed and it is devastation. Couldn't be further from the truth. By the way...the GBR is collapsing and reforming all the time throughout the last ~30K years. It wasn't just some paradise that started to decline when humans showed up


Just accept that it will happen, and it will likely happen to all of us. It has already happened to a colleague of mine, and they are a highly educated native English speaker.


What did I miss?


They updated their methodology when the new openai model didn't rate higher than the old one, or something like that.


I do t think it was a fiasco. I thought the updates were good. They should do more work on benchmarks. There has been good work on testing benchmarks for example to ensure they are accurate, and as issues arise they should change the benchmarks. The point of AA and Arena is trying to understand how to think about models.


Any use case where a confidence level is desired and you want that number to actually mean something.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: