It has been nearly 2 x 52 x 604800 U.E., i.e. 2 times 52 weeks or 2 years, that Doughnut embarked on the development journey on a Chromebook. So, why it took so long to complete this two-posts journey?
The answer, no IDE was matured enough. Yes, there was Eclipse Che but there was a lot of hoops to jump through just to make it work. Yes, there was gitpod but it caters mainly to javascript folks (not Java and Python, which are Doughnut's bread-and-butter languages). It was a pretty hard experience to replace Eclipse with something Chromebook can provide. Also, vim is also quite limiting.
But again, Microsoft's Visual Studio Code came to the rescue. Microsoft in 2010s is completely different to itself back in 1990s. It embraces open-source culture -- to the extent that it bought github in 2018. The Redmond giant also enable linux programs run natively (well, not 100% native but you know) on Windows 10.
However, VSCode was not officially ported to ChromeOS yet. And Doughnut's version of Chromebook is using an architecture VSCode is not built officially for. Thus, we went through the route of VSCode for Chromebook. Well, these builds were late (no offence to maintainer) and Remote Development Using SSH extensions I intended to use was not available for these builds until lately. Wow, ... what a journey.
But, all said and done. Viola, python development and java development is 95% similar to local development now (thanks to Google Cloud and the magic of public/private keys). There are still some gotchas in Java development but Doughnut aims to solve it himself when he has some free time.
Now, let me pronounce:
The answer, no IDE was matured enough. Yes, there was Eclipse Che but there was a lot of hoops to jump through just to make it work. Yes, there was gitpod but it caters mainly to javascript folks (not Java and Python, which are Doughnut's bread-and-butter languages). It was a pretty hard experience to replace Eclipse with something Chromebook can provide. Also, vim is also quite limiting.
But again, Microsoft's Visual Studio Code came to the rescue. Microsoft in 2010s is completely different to itself back in 1990s. It embraces open-source culture -- to the extent that it bought github in 2018. The Redmond giant also enable linux programs run natively (well, not 100% native but you know) on Windows 10.
However, VSCode was not officially ported to ChromeOS yet. And Doughnut's version of Chromebook is using an architecture VSCode is not built officially for. Thus, we went through the route of VSCode for Chromebook. Well, these builds were late (no offence to maintainer) and Remote Development Using SSH extensions I intended to use was not available for these builds until lately. Wow, ... what a journey.
But, all said and done. Viola, python development and java development is 95% similar to local development now (thanks to Google Cloud and the magic of public/private keys). There are still some gotchas in Java development but Doughnut aims to solve it himself when he has some free time.
Now, let me pronounce:
Chromebook can Dev.
Logged on Doughnut I/O. U.E. 1587600028.
Comments
Post a Comment