Re:Ask HN: Are Chromebooks ready for serious development?
by ponco on Saturday May 12, 2018 @08:55AM
(#17053837)
Some people still write code that is compiled.
[ Parent
| on HN ]
Re:Ask HN: Are Chromebooks ready for serious development?
by cozzyd on Saturday May 12, 2018 @10:06AM
(#17054124)
And the people who do that tend to use super bloated Dev environments.
Re:Ask HN: Are Chromebooks ready for serious development?
by imtringued on Saturday May 12, 2018 @01:51PM
(#17055171)
I've had the opposite experience so far. Eclipse IDE that uses 1GB+ of RAM? Compiles java code to bytecode instantly everytime you save.
Sublime Text + gcc for a C++ project? Well, you have to live with the fact that sometimes a rebuild is going to take more than 5 minutes.
In other words it has nothing to do with how bloated the dev environment is and more with the fact that some programming languages have features that can cause excessive build time.
Re:Ask HN: Are Chromebooks ready for serious development?
by gmemstr on Saturday May 12, 2018 @11:18AM
(#17054421)
> super bloated dev environments
Care to give some examples of this? I've been using compiled languages for a while now and I've never felt my environment had been "bloated".
Re:Ask HN: Are Chromebooks ready for serious development?
by verhey on Saturday May 12, 2018 @11:50AM
(#17054604)
That's a pretty massive assumption.
Re:Ask HN: Are Chromebooks ready for serious development?
by ATsch on Saturday May 12, 2018 @09:16AM
(#17053912)
and even if you don't, using a slow machine is still not a great experience.
Opening a shell, reloading a page, switching tabs, running git pull, decompressing an archive, linting, building etc.
All these things will take noticably longer to the point of being frustrating on a low-end machine.