The update system on Chrome is wonderful, in that it just happens. No strange dialog boxes, popup messages or confusing options for the computer-illiterate. It just goes ahead and does it. A power user might not like that, but it is a great system for a huge userbase.
How many insecure ChromeOS devices are there out there? Very few, I'd expect. Not many other operating systems can claim this.
Source: I know lots of people who deploy and manage these in schools.
I made a computer illiterate friend get one because I was sick of doing tech support for his windows Lappie and he loves it, and has had zero probs with it.. the only time he's called me with a problem with it was when he was trying to some fucking exe to win a free ipod. CHROME os rocks.
Have you calculated how much it's costing you?
I ended up scripting up a way to find the cheapest Spot Instance price from Amazon for whatever workload I needed - if I was doing builds I wanted the 8 core machines (c4.2xlarge?). They're ~11c an hour as a Spot Instance, although it's 3x the amount for a Windows instance, and I'd be pushed out of the market if everyone started doing this.
I think I was averaging a couple of dollars a day, so I suppose it comes out in favour of using AWS all the time.
(Also if I had a powerful local laptop, I couldn't tell it to do a build, close the lid, and get on the subway without my backpack catching fire. Nor could I have it provide IPv6 to my apartment, host websites behind CloudFlare, provide shells to my friends, etc.)
If I wanted to put some more effort into it, I could certainly do a good fraction of my work (git clone, vi, IRC and email, etc.) on a micro instance. But even a couple of dollars a day would require me to be pretty careful to come out cheaper.
I think my costs would be a bit higher because Kimsufi/OVH/Hetzner are 300-400ms away from me, so the latency is a bit uncomfortable.
When I was in Canada, a Hetzner box was 200ms away and usable, but for ~$30 a month I only had a dual core box - a bit restrictive when doing large builds.
I might have a go at automating setting up a dev environment on AWS which can be torn down when not in use.
Could you share a couple of lines on how you would set that up? Spin up an upstream-provided basic AMI (eg: RedHat/Ubunut/Debian) - and run a few commands under screen via ssh - and then shut it down?
It's like driving a little remote control car to the shops and claiming that you went. You didn't.
I could walk into a library and use a terminal there to type code in, but I'm not doing development on that machine - it's just a dumb terminal.
Now I understand the fact that you can remotely connect somewhere else to do work, but the advent of the microcomputer has meant that you shouldn't need to do that. Power usage for the earth will not be great if everyone runs a device that needs power locally, over a network system that needs powered routers, to a computer remotely that needs power just so you can type code in.
That really doesn't make sense.
I agree that in the context of this (sub)thread, it's a bit odd to claim that chromebooks are decent developer workstations, when what's meant is that they're decent dumb terminals. I'd still like to run my code on my dumb terminal - but I think it makes perfect sense to work like that - have something dumb and wireless for human interaction, and data/processing on a dedicated piece of kit. Be that a low power intel cpu and ssd in a small box behind the tv, or something in a rack somewhere.
And the advent of dynamic libraries has meant we shouldn't need Docker, but, well, that's how it is. It's true that in an ideal world we shouldn't need such a mechanism, but in practice this system works very well for me, and the other ones have been frustrating.
I need a working internet connection anyway to do work: I need everything from software updates to GitHub to IM with coworkers to Google and StackOverflow. And the remote machine shouldn't need any more power than my local one. So my added power consumption is just that of my Chromebook, which is about 10 W.
I admit freely that I am not fulfilling the definition of "development on the Chromebook" in a strict sense, but it is certainly a serious answer for how I develop on my Chromebook.
There's also in-browser VPNing.
That's damning with faint praise, isn't it? It can, at this point, do MOST of what an everyday Internet user might want? It's that whole 80/20 thing that everyone thought would let somebody overthrow Microsoft Office -- 80% of users only use 20% of the features. Well that's true and all, but it's not the same 20% for everyone, and you only have to miss one feature to make a Chromebook an untenable alternative to a Windows machine. There was a brief window where Chromebooks were significantly cheaper than a comparable Windows laptop but Intel took the ARM threat seriously, Microsoft took the licensing seriously and now the base Chromebook price from a name manufacturer isn't significantly cheaper than the HP Stream or what have you. "Most" is not going to cut it now that the price advantage is gone.
> There are lots of people who are content with its restrictions.
This is really only true in that we live on a planet with many, many lots of people, and so you can find lots of people for which almost anything holds true if you funnel it down. ChromeOS market share is a rounding error at this point, and if there were any signs that this was turning around, Google apparently decided they weren't enough for them to continue.
Having an elderly family member struggle to stay up on Windows is super sad to watch and try to help with. I personally definitely wish that I had been more proactive migrating my grandfather to a more locked-down system when he was slightly younger and had a better capacity to adapt.
If the grandfather really is elderly, like older than 75 or 80, I would push in the direction of asking the question "Does he really need Quicken anyway, or maybe he's at a point where he could give up that responsibility, or compromise with Quicken Online?"
I've never met anyone who said it was, so I doubt it. Stop being a blind advocate and realize that some people do need Windows because they need apps that only run on Windows.
The screen, keyboard, case and battery quality are a joke in most offerings, not to mention most lack dedicated GPUs or specific BIOS features.
Granted, it's not as productive (trackpoint or riot!), but it works.
But with the increasing tivoization of computing? Once below-1000€-laptops/desktops disappear in favour of oversized tablets, how are children going to learn coding? People in developing countries? Poor people in developed countries? Not everyone can afford a 1000€ price tag. Should these people really be excluded from everything that isn't mindless passive consumption?
The same way we learned since the late 70's on the home computers.
Installing some kind of application that allows coding.
The only difference being that BASIC or Forth were already builtin.
Secure Boot is the best example for that:
• On Windows RT devices it always was mandatory and could not be disabled.
• On Windows 8 devices, manufacturers must give users an option to disable it.
• On Windows 10 devices, it is now in the manufacturer discretion whether it can be disabled or not.
The next step is obvious.
I suppose it's no surprise. It goes something like this: a) underwrite the device (not necessarily lose money on every sale, just lower the margins), b) introduce an app store, c) take a cut of every transaction.
As long as users and developers need your OS, your device - your appstore - you will make money.
I see at least one clear profit motive for the industry here, let's say you have a "Desktop enabled, smart" smartphone, you'll probably want to buy a dock, screen, keyboard, mouse, productivity software, etc.
Supermicro XnSAE workstation motherboard: 215
3.3GHz 4 core Xeon E3-1226 CPU w/HDMI out: 217
32 GiB DDR3 1600 ECC Kingston memory: 240
Low end 1/3 w/year for 5 years data center 80GB Intel SATA SSD: 100
Seagate "enterprise" <550/TB/year 4 TB hard disk: 210
982 USD plus shipping plus whatever enclosure, power supply, high quality fans etc. you put into it, which ought not go over $200 new. E.g. after discovering a Lian-Li enclosure I love I bought 3 more and cycle through them.Plus backup, however you do that (make sure critical stuff is offsite!). And, say, a man-week of your time to configure, order, build, install and configure Linux. The result will be very fast and rock solid (well, if put behind a good UPS) workstation class machine with a 5 year design life.
Simple enough; they'll code on tablets.
I'm actually currently working on a prototype for how a simple, useful development environment might look on a phone or tablet. It's a stack-based concatenative array language with a zoomable user interface. Instead of representing code as lines of text, it takes a more Smalltalk-like approach of a live environment. The benefit of being a concatenative language is that it naturally lends itself to a tree-like format where each word can be viewed and edited on a phone screen. Since semantically it's closer to a weird mashup of J and Perl(!), it can be concise (hopefully still readable) and the vector aspect makes drawing graphics pretty straightforward.
The downside, of course, is that it can be quite hard to reason in. Truthfully, I'm not really sure how to work around that—and I don't think most children will easily think in a function composition/matrix manipulation way. That said, I'd like to find something since I'm fairly sold on the idea that tacit programming with arrays is key to making coding on a tablet work (I think it's fairly clear that imperative or even conventional function languages would be a royal pain to use in such an environment). Maybe something Lisp-like where the user zooms around the AST would be an alternative.
> Poor people in developed countries?
Much cheaper phones and tablets are already vastly more popular than laptops or desktops among poor people. The solution is to move coding forward on mobile, not simply keep rather trashy cheap laptops around.
I see you've chosen well known readable languages as your inspiration ;)
There's plenty of free, on-device code editor, compiler/interpreter, etc. apps for Android, including ones that will allow you to run code in the app, or build, package, and install (given that you've enable non-Store installation) Android apps right on the device.
I and many others did learn computing on those systems, so apparently it isn't a show stopper to learn.
I don't remember getting any compiler or interpreter for Amiga, Atari or Apple Mac. You had to pay for them and the schematics were part of the OS SDK, also commercial.
Also going besides the ROM BASIC or Forth meant buying a compiler/interpreter.
The app stores are full of them, just pick one.
AFAIK Arexx was part of Worbench? But yes, you did need to get a compiler/interpreter for that. I thought you were talking about stuff like the C64 generation of computers.
I remember there were GNU tools available for the Amiga, and some magazines came with various development tools -- eg: Blitz Basic. But most were certainly commercial (including Blitz Basic) - but one must consider that even with aminet - there was nothing like the essentially free distribution of today (eg: push to github).
According to this site, Amiga Basic was actually bundled with the machine (note-section: "bundled basic language interpreter (free with machine)"):
http://www.classicamiga.com/content/view/5044/175/
> The app stores are full of them, just pick one.
Did Apple change their policy of allowing development tools? They certainly don't allow the creation of apps on the ipad/iphone as far as I know?
A few of the best ways to learn coding on the move
Codea
https://itunes.apple.com/us/app/codea/id439571171?mt=8
Pythonista
https://itunes.apple.com/us/app/pythonista/id528579881?mt=8
GLSL Studio
https://itunes.apple.com/us/app/glsl-studio/id481421644?mt=8
Lisping
https://itunes.apple.com/us/app/lisping/id512138518?mt=8
There are plenty more, one just needs to search for them.
Also they are pretty cheap compared to what I used to pay for, back in those days.
Much of the use of ChromeOS and ChromeBooks is in education (where they compete with Macs and iPads), where the buyers are not the users, and the restrictions are actually part of the appeal. It's a decent niche I guess, it's just that but when I see some of the newer Chromebooks with Core-i5 processors, I can't but feel it's a waste of horsepower.
I bought my mom a Chromebook and she loves it. I think the group of users who are willing and able to do all their computing tasks inside a browser window is larger than you think.
Sure, if you say so it must be true.
> How many insecure ChromeOS devices are there out there?
How many ChromeOS devices in absolute numbers are out there and what is the target audience of 200$ laptops?
If I were a hacker, I would certainly not target this platform.
It's not my "main" computer though, but that was never the problem raised in this thread. The fact is, chromebooks and Chrom{e,ium}OS are very decent platforms for all kinds of users, and they are indeed pretty safe to run. And I often do as others said: I ssh from the chromebook to my other PCs in other rooms, or remote servers, etc...
It's also a great device when travelling if you have a 4G phone providing connectivity or you stop in hotels or conferences with WiFi (I wonder if there's been attempts to bring one to a DefCon or pwn conference to see how it holds... haven't checked).
Sure I find that it hads plenty of shortcomings. But most of them are stuff that are shortcomings for me, professional CS/IT dev/tester/consultant/trainer/teacher/etc... Lots of other user groups will also probably fine shortcomings (like the "elderly" person mentioned requiring Quicken), but it doesn't mean you can't work around the issue (substitute it, use quicken from another machine, etc...).
It surely isn't all-purpose or perfect, but it's still great.
I wholeheartedly agree that I'd be deeply sad to see it sank, way more than I'd have been to see it merged the other way around.
That being said, as recently Android Apps were starting to be available on ChromeOS via the Chrome Web Store and worked decently for the most part, I'm curious to see what the actual integration/folding will be. Because it may be largely marketing-oriented to make Android the prominent part (or just the prominent brand) as it's way more popular in terms of user and device share (billions vs probably a few millions, if even that).
EDIT: And Pichai's quote does not worry me too much until I see something happening: "mobile as a computing paradigm is eventually going to blend with what we think of as desktop today."
In fact, the article seems mostly unsubstantiated, so as long as I don't see an announcement from Google I think I'm not letting go of my chromebook and ChromeOS. :)
I planned to buy a Chromebook a while ago and do exactly as the parent suggested, but got to the conclusion that it's just not worth the hassle (also, Chromebooks tend to have minimal storage, which is definitely not ideal in a normal laptop).
In general, Chrome OS or not, the HW (touchpad, screen and keyboard even more than raw power) in a 200$ laptop is BAD.
Before Chrome OS, I ran homegrown minimal Linux installations with a separate user account to run Firefox. It was way too much overhead for me to be excited about maintaining, and paying $200 for a secure architecture and security updates by the most competent people in the industry was super attractive. I can do servers very well; I don't also need to do desktops, let alone my personal desktop.
A CrOS-like OS with the ability to run VMs would be pretty great. (And yes, I should check out Qubes.)
I'm all for allowing native applications a place to run, however that doesn't mean that ChromeOS was not able to do anything... both my parents and grandparents are all on ChromeOS laptops now... why? It's all they need, secure and I haven't had to remotely clear out any malware in over a year.
Except for an operating system, of course.
http://programmers.stackexchange.com/questions/221615/why-do...
In the end it all runs on an operating system... so it technically falls short of that of course, but building a web-based app is generally easier than raw-coding an application from the OS level.
This is pretty much one of the two markets I've ever heard of for ChromeOS machines, the other being education space. What they have in common is that:
1) People want them for SOMEBODY ELSE 2) Because they don't trust that somebody else with the power of a less locked-down machine.
Sure, schools are buying ChromeOS machines... for the students. Not the teachers and administrators. It's too limited of a market segment for ChromeOS to grow a large enough userbase.
They've all been very happy with them... well, one of my grandmothers has trouble with using it sometimes, her hand shakes, but that's a problem with desktops for her too.
I used one for about a year and if I were able to use the VPN to remote into work (stupid proprietary VPN software), I'd probably still be using it... I used remote desktop and SSH to other systems when I needed more for work, but was pretty happy with it. Yes, there were times I needed more, I had a desktop for that... one at work, another at home... most of the time I used my chromebook though.
These days aside from at work, I use my htpc for more web stuff than anything else... I've tried a few android and arm based mini systems for that role, but the experience was less than stellar.. currently an i3-5010u which does pretty well for my general use, and htpc chores. I'm on it right now.
Most people only use/need the web for home use... Chromebooks are great for that... There's even a few halfway decent general purpose email clients being worked on (one client to work over imap, etc for multiple accounts) as opposed to typical webmail. That was about the only shortcoming I really felt. Also, getting my private rsa token for SSH setup on the thing was a little bit of a pain.
Nope, it was called Smalltalk.
* chromebooks
* web browsers
* a turing machine implemented by having a grad student a car drive around on a long street
Of course it might be a bit slower, it might take a bit more effort, time and imagination on the part of the user.
But seriously: it needs to run existing programs without recompilation.
That said, while compatibility helps adoption, it is not absolutely necessary. If it were, we would all be stuck with Windows computers in our pockets running on Atom processors having 1:30 hours battery life.
..Or maybe you simply have a deficient imagination?