4 ms·
Well, yeah. But it's still a snowflake, a dev environment with build/deployment configuration and needs that are significantly different from production cloud e
by beat 8y ago
Well, yeah. But it's still a snowflake, a dev environment with build/deployment configuration and needs that are significantly different from production cloud environments. And it requires a lot of setup, and a lot of knowledge to do it well (which I actually have). Writing a bunch of automation to hide the fact that I'm working on a snowflake is not the same as not working on a snowflake.
Or, I can do my development in the cloud, in an environment explicitly more similar than my desktop environment. Other than aesthetics, I don't see why this is a Bad Thing. It's making my setup easier and more consistent, and it's making my development environment portable to whatever system I want to work from, rather than binding it to a piece of hardware.
- pjmlp 8y agoAh, memories of those DG/UX X Windows terminals accessed for the very first time in 1994 and VT 100 green phosphor telnet terminals, followed by the freedom of having Slackware 2.0 on my PC a year later....
- beat 8y agoThank Dog it isn't 1995 anymore. (Memories from the same era - hand-rolling TCP stream protocols in lexx and yacc, because XML didn't exist and http was a toy)