Hacker Newsnew | past | comments | ask | show | jobs | submit | ohNoe5's commentslogin

We will never fundamentally get rid of thinking; it's coupled to navigation of 3D reality we live

And we don't need words to think; cognitive problem solving and language processing are separate processes [1]

We will shift the problems we need to think about. Same as always; humanity isn't really solving building stone pyramids. Did we stop thinking? No just thought about a different todo list.

[1] https://www.scientificamerican.com/article/you-dont-need-wor...


We also never run out of fuel. There will always be some energy left here and there to tap into.


Thems the breaks when all the politicians trend towards 60+ and went their entire lives believing the giant foot will smash us if we raise taxes

GenX was the first generation raised on "science" first education And the transition period was uneven in effort with many educators also peddling their personal religious views with the content.


Hardware is important to operation of computers and software as we know them

A bunch of config management DSL startups, and web scale data storage solutions, not so much


Right, and Google owns 25% of the hardware.


Ephemeral user accounts were agreed upon before that. The OG container

Docker and k8s are just wrappers around namespaces, cgroups, file system ACLs, some essential cli commands, which can also be configured per user.

We may be headed back there. Have seen some experiments leveraging Linux kernels BPF and sched_ext to fire off just the right sized compute schedule in response to sequences of specific BPF events.

Future "containers" may just be kernel processes and threads... again. Especially if enough human agency looks away from software as AI makes employment for enough people untenable. Why would those who remain want to manage kernels and k8s complexity?

Imo its less we agreed on k8s specifically and more we agreed to let people use all the free money to develop whatever was believed to make the job easier; but if the jobs go away then it's just more work for the few left


> Docker and k8s are just wrappers around namespaces, cgroups, file system ACLs, some essential cli commands, which can also be configured per user.

Docker, yes, but kubernetes is way more than that the instant you have more than one physical machine node. (If you only have one node in any deploy, sure, it's likely overkill, but that seems like a weird enough case to not be worth too much ink.)

If you silently replaced all my container images with VM images and nodes running containers with nodes running VMs, I think the vast majority of all my Kubernetes setup would be essentially unchanged. Heck, replace it all with people with hands on keyboard in a datacenter running around frantically bringing up new physical servers, slapping hard drives in them, and re-configuring the network, and I don't think the user POV of how to describe it would change that much.


> nodes running VMs,

huh, but how would bursting work then? Do VMs support it nowadays?


I've seen some places advertise it but I have not tried it.

But, honestly, more generally in my head I wasn't thinking much about it since I consider that as a "cost optimization" thing than a "core kubernetes function." E.g. the addition (or not) of limits is just a couple lines, compared to all the rest of the stuff that I'd be managing specification of (replicas, environment, resource baseline, scheduling constraints, deployment mode...) that would translate seamlessly.

(And there are a lot of parts of kubernetes that annoy me, especially around the hoops it puts up to customize certain things if you reaalllly actually need to, but it would never cross my mind in a hundred years to characterize it as just a wrapper around cgroups etc like the OP.)


Something often underappreciated is that, in the possible future you're describing, you can use all of these new fangled "what's old is new again" approaches by continuing to just use Kubernetes. Kubernetes is, in a way, designed to replace itself.


Kubernetes is software. It cannot do anything "itself" let alone "replace itself". Don't anthropomorphize software

Inevitably it will be a human replacing it with what they define is the best method


Yeah it's that lack of perfect recall, imo, that gives rise to intelligence and progress.

If we humans just did exactly what we did yesterday, what progress?

It's baked into the immutable constants of the universe for us; entropy, signal attenuation over distances... information breaks down over time.

Because of this all human social statistics trend towards zero with intentional conservatism. Progress is or collapse is all the universe affords. It doesn't seem interested in conservatism at all.


Oops I meant "without intentional conservatism"

And

"Progress or..." not "is or"


Oh no, a couple thousand people, largely engaged in little more than modern conservatism, might leave the rest of us 300+ million alone for a change rather than demand fealty to their personal story and personal autonomy (fealty to which actually distracts us from our own lives); people who do nothing to assure the rest of us have food and shelter and healthcare may take their ball and go home!

How tragic.

End of the day we all have the same freedom to not care if Sergey has food shelter or lives in his car as the billionaires give themselves

End of the day we all have the ssme right to select ourselves and tell Sergey Brin "your needs aren't my problem."


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

Search: