[keenerd]

I've been doing that for years: http://kmkeen.com/c100p-tweaks/

Development doesn't require any more CPU than word processing. You're type stuff up, and there is a pretty strict grammar check. I don't get why people why people want to run huge things on a laptop. It is way more economical to shell into a beefy server when you need big iron instead of carrying it with you.

[ponco]

Some people still write code that is compiled.

[cozzyd]

And the people who do that tend to use super bloated Dev environments.

[imtringued]

I've had the opposite experience so far. Eclipse IDE that uses 1GB+ of RAM? Compiles java code to bytecode instantly everytime you save. Sublime Text + gcc for a C++ project? Well, you have to live with the fact that sometimes a rebuild is going to take more than 5 minutes.

In other words it has nothing to do with how bloated the dev environment is and more with the fact that some programming languages have features that can cause excessive build time.

[gmemstr]

> super bloated dev environments

Care to give some examples of this? I've been using compiled languages for a while now and I've never felt my environment had been "bloated".

[verhey]

That's a pretty massive assumption.

[ATsch]

and even if you don't, using a slow machine is still not a great experience.

Opening a shell, reloading a page, switching tabs, running git pull, decompressing an archive, linting, building etc.

All these things will take noticably longer to the point of being frustrating on a low-end machine.

[keenerd]

I'm one of those people.

[tedmiston]

> Development doesn't require any more CPU than word processing

Please tell that to my local k8s cluster.

[keenerd]

And how much horsepower do you need to shell into that cluster?

[tedmiston]

I'm not totally sure how to answer the question you're asking. The local dev cycle is much faster than deploying and running remotely.

Locally the cluster runs two main projects, both systems that handle user-defined tasks. One is a Kafka-based clickstream event processor, the other is an Airflow-based workflow ETL system built on Celery. Exact resource requirements depend on the requirements of the task of the moment and how fast you want it to run. Of course there is the related tooling and services as well such as ZooKeeper, Celery, Redis, Postgres, Grafana, Prometheus, etc.

I haven't tried this on a tmux type setup on a remote box for my "local" dev before. The cost to run it on a cloud deploy is non-trivial.