Live data from Hacker News

Instant dev environments for cloud-native apps

okteto.com

1–10 of 51 posts

Re: Instant dev environments for cloud-native apps

#2
Github codespaces is a step forward to eliminate local setup and have replicable dev environments running in containers. But for true cloud-native applications, you would need a kubernetes namespace to run other services, databases or access the kubernetes API. This blog post explains our vision of cloud-native development at www.okteto.com

Re: Instant dev environments for cloud-native apps

#3
post #2

Github codespaces is a step forward to eliminate local setup and have replicable dev environments running in containers. But for true cloud-native applications, you would need a kubernetes namespace to run other services, databases or access the kubernetes API. This blog post explains our vision of cloud-native development at www.okteto.com

What's the performance like with compiled languages? I'm using rust and compiling in containers always seems slow.

Re: Instant dev environments for cloud-native apps

#4
post #2

Github codespaces is a step forward to eliminate local setup and have replicable dev environments running in containers. But for true cloud-native applications, you would need a kubernetes namespace to run other services, databases or access the kubernetes API. This blog post explains our vision of cloud-native development at www.okteto.com

What's the performance like with compiled languages? I'm using rust and compiling in containers always seems slow.

I haven't tried rust, but I usually work with Go. The performance really depends on the resources assigned to your container. Okteto Cloud gives you 4 CPUs and 8Gi RAM. Also, it is important to persist dependencies and cache information using volumes to take advantage of incremental builds.

Re: Instant dev environments for cloud-native apps

#6
post #5

Don't you tell me I'm living in "the dark ages" mister, I'm fully serverless. It's you who's grasping for a world soon to be gone.

I just find it to be patronizing, and it made me not want to read further. We have developers using Emacs and Lisp, we have Python devs, we have people using browser IDEs all under the same roof. There are any number of capabilities in the former that are missing in the latter, not least of which is "more complete control", something none of these products offer me in a convincing way.
Post reply on HN