kross

I have been using ksonnet but that is now officially dead. Working with jsonnet seemed unnecessarily painful when coming from coding typescript. This information is quite timely and welcome, I'll look further at the ts example.

- The goal

- Running lean

> This is beautiful in its simplicity and still has a piece of truth.

It will likely always be true. It is human nature.

I'm not sure you understand the value k8s proposes based on your comments throughout this entire thread.

Managing many nodes is the reason orchestration software exists. Your suggestion to "put some effort into configuration management" is effectively naive, homegrown orchestration.

Build or buy? That's the same argument - except k8s is free and available from many providers.

I get the sense that the naysayers outweight the supporters, simply because the headline alone is not news. Don't let them deter you, spend a few hours and decide for yourself.

Polyglot (multiple tech/languages), unknown scale, dramatic flash traffic or potential thereof.

Really your next step in general is understanding containers and where they might be useful. K8s consideration is probably after that.

> What keeps people highly coupled with could provider is not where their code is running but rather other "here only" solutions like custom DBs or infrastructure.

I agree, and the advent of k8s adoption is one less thing that locks you into a provider.

What are the alternatives of which you speak?

Which part of kubernetes is "developed with the intention to eventually get you to use the hosted version"?

Offering software for free, software that is widely adopted cannot be based on the motivations you propose, unless there is a grand conspiracy of cloud providers for which I am unaware.

Use k8s exactly for the reason of either being federated across cloud providers or simply portable across cloud providers. You can't do that with vendor specific solutions e.g. elastic beanstalk

That's effectively anti-globalization. Adapt and overcome. Good developers will always have a job in the forseeable decades to come, weak or stagnant developers will be at risk, it is a maturing industry. White knuckling tech by resisting change/momentum is no more effective than starting a trade war with tariffs.

> forward thinking engineer

Yes. Based solely on your desire to be on top of tech and given the broad adoption by every major provider, you probably want to invest at least a couple of days.

That doesn't mean there is any impetus to transition your current production, only that it is most definitely worth a cursory understanding for the future.

All major cloud providers have/will have managed kubernetes and they are free to use the name, therefore I doubt it could be regarded as direct marketing for GCP. I would expect many to consider GCP but I just don't perceive this as a backdoor way of Google getting your apps, given the broad buy-in by the cloud provider community.

Myself and many others are using typescript styling with success. If you have a specific problem, please file an issue so we can take a look.

React in it's stated goal IS quite easy, but I agree, to become a master, you should learn a few patterns quickly.

I don't feel like react's docs are misleading - like anything - mastery requires investment.