[deleted]
Chrome OS: Ready for Web Development [video]
21–30 of 228 posts
Re: Chrome OS: Ready for Web Development [video]
#22Ready for web development just as it starts to achieve price parity with a macbook. I'd argue that this is largely a failure of the initial vision of a lightweight OS that can run very well on low cost hardware.
Re: Chrome OS: Ready for Web Development [video]
#23Interesting. Any advantage of using Chrome OS for Web development compared to just any plain Linux distro (e.g. Ubuntu)? Or, even more interesting, compared to MacOS? Because from the video, it feels as if Crostini is a second-class citizen on Chrome OS (all that talk about Linux in a container). Why choose Chrome OS at all?
Containers are fairly lightweight abstractions on Linux, there is effectively no runtime cost. I use a Chromebook as my mobile work machine (I use full desktop Linux on my workstation at home) because it is disposable, low-risk, and easy to wipe. It takes about 20 seconds for me to destroy all the data on the machine and lend it to somebody with a great deal of confidence, and the Chrome OS part synchronizes on its own. I use Syncthing to sync my mobile desktop Linux configs and a handful of other things. So between those two I can set up any old random Chromebook to work as a workstation in a matter of minutes. If I have a good internet connection, chrome remote desktop makes a good interim solution if I can't wait for Crostini to install.
Generally I do most of my productive work in desktop Linux, but Chromebooks are also good consumer machines. The mid to low tier ones are totally usable, have great battery life, and can be bought easily in any developed country except China.
The Chromium team has a great track record for security, and having (in a very small way) worked with their security folks, I can tell you that they take the business and community of improving and maintaining Chrome's security very seriously. If you are using an unmodified Chromebook with the most recent stable release of Chrome OS, and not in dev mode, then you can be reasonably sure that it's going to reliably carry out its promise of security.
Re: Chrome OS: Ready for Web Development [video]
#24Been using edge releases on my Pixelbook i7 for a few months. Much of this is pretty baked. I wish USB support was here so I could use my Yubikey 5c to do SSH, but otherwise it's fine. From my experience Docker works fine. VS Code works well. You can install your own Terminal if you want. Note for the demo in the video they ran Chromium inside the VM so localhost would work. Otherwise you need to use the penguin.linu…
You can use Secure Shell for SSH with your Yubikey in the meantime: https://chromium.googlesource.com/apps/libapps/+/HEAD/nassh/...
Re: Chrome OS: Ready for Web Development [video]
#25I'm still waiting on good Docker support. Word is it's close, but I don't know if it's there right now. Really all I need in a dev machine is a Unix + docker + IDE, so this is pretty interesting.
If that's what you're waiting for I'd say it's ready. Although you have to run Docker inside the host and I don't think you can run privileged containers (don't have in front of me to test).
Re: Chrome OS: Ready for Web Development [video]
#26Ready for web development just as it starts to achieve price parity with a macbook. I'd argue that this is largely a failure of the initial vision of a lightweight OS that can run very well on low cost hardware.
Only the Google Chromebooks are priced high, and still isn't even close to the Macbook.
There are many offerings from other company for just a few hundred dollars that run Chrome OS.
Re: Chrome OS: Ready for Web Development [video]
#27I'm thinking of getting a Chromebook for dev work, with the view of just using it as a dumb client for terminals and browser to cloud servers. I'm worried I'll buy then wish I bought a proper machine. Anyone thought the same then regretted it?
My suggestion right now(from a Mac user), is a Windows 10 machine with the Linux subsystem installed. You'll have an entire Linux environment integrated into Windows, giving you the best of both worlds. Supported software, hardware, and your natural development environment. Honestly, I'm weary of moving anything to Google with their track record of just abandoning projects, and privacy concerns.
Re: Chrome OS: Ready for Web Development [video]
#28Who is this really for? Students who have a cheap Chromebook and couldn't write / test code due to OS restrictions? Developers who have a Chromebook (and love it) and wanted to use it for everything?
You need a flagship Chromebook for proper Crostini support.
What's not supported on my $280 Acer Chromebook 13?
Re: Chrome OS: Ready for Web Development [video]
#29Earlier quoted context omitted.
Crostini is a VM solution (the container is in a VM). It's by no means a second class citizen. The Files app for instance shows Linux apps along side your Chrome OS apps. Other integration pieces are in the works. Why choose Chrome OS? It's the only mainstream OS with security at it's forefront and 6 week release cycles. Also, the battery life is amazing and there are a range of devices from low end to the higher end…
Support window for older devices is questionable. I own a Generation 1 Pixelbook and it has stopped receiving updates (including security updates). Dropping security updates after a couple of years in fact is worse than other operating systems. Am unsure if users are alerted that their devices will not be updated anymore. Disclaimer: Views expressed are my own and do not represent my employer.
Chromebooks have a 5 year support policy. It's not a couple of years.
Re: Chrome OS: Ready for Web Development [video]
#30Ready for web development just as it starts to achieve price parity with a macbook. I'd argue that this is largely a failure of the initial vision of a lightweight OS that can run very well on low cost hardware.
It can likely run well on low-cost portable hardware.
But the web development tools likely won't run well on it.
(You can get plenty of power using a now low-cost box of Xeons from two generations ago. Likely not your use case, though.)