3 ms·
I wasn't sure which was the better link to post but I've written about exactly this here: https://headmelted.com/visual-studio-code-for-arm64-67c19625ba2c http
by headmelted 8y ago
I wasn't sure which was the better link to post but I've written about exactly this here:
https://headmelted.com/visual-studio-code-for-arm64-67c19625ba2c https://headmelted.com/visual-studio-code-for-arm64-67c19625...
Basically it's the ARM and ARM64 support that's new. For anyone who has a device that supports the official Linux apps containers I steer them down that route, the Crouton method is kept around for older kernel devices (as their out of luck wrt official Linux support, sadly)
- Theodores 8y agoThanks for your efforts, as a long time Chromebook user I am truly impressed particularly with the Crouton build for those of us with the original Pixel and no Android apps. Currently I am not in Developer Mode and I have a linux box for running a different IDE. I am okay with my Pixel being for testing and non-dev things. So, before I powerwash the thing and get Crouton working again (which I am slightly loathed to do since the five year support period is over), could I please have a few screen shots? I hope I am speaking here not just for myself but for others with a loved but dated Chromebook and questions about how this would work in the file-less world of ChromeOS where I am not so likely to be able to sync my files to a remote server. If I am to swap over to a different IDE then I need a few pictures to persuade me that the efforts are worthwhile. The Pixel (original vintage) has the best screen/keyboard/trackpad/speakers/design of any laptop ever made even if the CPU is a bit lame by today's standards and the battery doesn't last all day. So it would be nice to code on.