431–436 of 436 posts
Earlier quoted context omitted.
where does tailwind stand on this? you can use it without a build step but it's strongly recommended in production
A build step in your pipeline is fine because, chances are, you already have a build step in there.
Earlier quoted context omitted.
A build step in your pipeline is fine because, chances are, you already have a build step in there.
no, having a build step kills the magic of interactivity when developing for the web.
Earlier quoted context omitted.
"Imagine you are in a rubber raft, you are surrounded by sharks, and the raft just sprung a massive leak - what do you do?". The answer, of course, is to stop imagining. Most people on the "just use bash scripts and duct tape" side of things assume that you really don't need these features, that your customers are ok with downtime and generally that the project that you are working on is just your personal cat photo…
You know that you can scale servers just as well, you can use good practices with scripts and deployments in bash and having them documented and in version control. Equating bash scripts and running servers to duct taping and poor engineering vs k8s yaml being „proper engineering„ is well wrong.
Earlier quoted context omitted.
I would buy the book. Just translate all "new language" concepts into well known concepts from networking and system administration. It would be best seller. If I would only have a penny for each time I wasted hours trying to figure out what something in "modern IT" is, just to figure out that I already knew what it is, but it was well hidden under layers of newspeak...
This[0] is my take on something like that, but I'm no k8s expert -- the post documents my first contact with k8s and what/how I understood these concepts, from a sysadmin/SWE perspective. [0]: https://blog.davidv.dev/posts/first-contact-with-k8s/
This is what I wish I had before I started learning.
https://www.linkedin.com/pulse/kubernetes-before-you-start-d...
By the way how much malice can we attribute to cloud vendors? >Moreover, Kubernetes’s slow autoscaling meant I had to over-provision services to ensure availability, paying for unused resources rather than scaling based on demand. A typical Linux instance on AWS starts up in about 8 seconds from the asking to start to command line, so lets double that. You could start up and shut down instances in 15 seconds. Why the…
TL;DR someone didn't learn to plan capacity.
If I write a program and decide to start a new thread, I don't need a dedicated ThreadOps professional moralizing about how I should've configured my app in the yaml file to use 2 threads instead of 1.
I have long held the belief that the clowning around that happens in IT nowadays is the opposite of engineering.
Earlier quoted context omitted.
Nope.
It's not as much mentioned in the docs these days, and Google might have built a more optimized version, but it's still using knative APIs and originally was essentially KNative deployed on GKE just managed by Google.