This topic comes up every month or so, and there's always this catch: > we need to first create a remote workstation which we can start using as our main development machine. A dumb terminal isn't a development machine. That's like saying "Using my DEC VT100 terminal to develop in Go", let me just hook it up to an actual computer
This is not a very good argument. I do my development work on my company issued macbook, but its not like I'm doing my work locally. My several thousand dollar macbook pro acts as a terminal interface for me for a HUGE proportion of my work. All my code is developed/built/run/tested on remote machines and my laptop is just a fancy interface to them.
i assumed OP is talking about "development" machine implying some code writing.