undefined | Better HN

0 pointsAvalaxy11y ago0 comments

I still don't see the necessity... Develop locally, test remotely.

0 comments

3 comments · 2 top-level

ghgr11y ago· 1 in thread

Some examples that just come to my mind:

- You need software/dependendencies/licences you don't have in your local machine.

- You need to edit a config file (/etc/hosts or whatever) in your server

- You are in a Windows computer (that's not yours) and you need to make a quick change in your Ubuntu development server.

- You need to edit some files when deploying (databases are no longer in localhost, /home/myname/ is /home/servername/, etc.)

- You launched a large script in your server and need to (view or parse logs | edit the code and re-launch it | check why it didn't work)

- etc.

joshka11y ago

software deps - this is a possible fair point. I've always managed to solve this by bringing the deps local though as a general sanity rule. config - why not source control it? quick change - why would you do a quick change differently to a non-quick change? edit while deploying - why wouldn't you script / source control this for repeatability / maintainability? log parsing - it sounds like you've got an edit, verify loop going on. Why wouldn't you want to formalize this so that you can see which changes align with which results?

scott_s11y ago

It's not necessary, it's just extraordinarily convenient. I don't have to ever say, "Oh, wait, I'm on my laptop now, I can't run an application with 100 processes without causing my system to grind to a halt."

Even the sequential performance of the remote systems is much higher than my laptop. The system in front of me is a means to interface with the real system, and has been for a long time. Granted, I have worked on parallel and distributed languages and runtimes for most of my professional life.

j / k navigate · click thread line to collapse