Chromebooks and iPads are both completely unsuitable for digital education in my opinion. They can be decent tools for education using digital resources, but that is something different.
To "force" someone to develop on a Chromebook is like giving someone a bicycle to become a race car driver.
That said, I usually flashed my arduinos and used bare metal C. Ironically I think it makes many things easier to learn and understand, provided you have a programming device.
What does a "digital education" look like, specifically?
Having spent several years teaching kids to code everything from games to lightbulbs on Chromebooks, I can confirm that there are certainly difficulties - but they're tradeoffs. I could spend my time coming up with a way to work through the platform restrictions, or I could spend my time maintaining a motley crew of devices and configurations. Having done it both ways, they both have different pain points.
You really can't compare a Chromebook with an iPad. On a Chromebook that I bought and that I fully own I can enable the Linux system and install whatever I want on it (it runs in a VM and it is a full Linux system). The iPad is artificially crippled for programming by Apple.
School IT departments are unlikely to allow this. Even if they don't have technical restrictions, they'll have policies that prohibit it (at least my kids' school district would).
School-issued devices are generally intended to be similar to devices a corporation would provision for non-technical workers.
Honest question, if you buy (just a hypothetical, I assume most parents can't afford to buy one) a Chromebook for your kid that will be used in school, do you have to lock it down or can you enable the Linux system (assuming that you want to do that and that your kid is interested in learning to program).
I think an old PC would be more useful then a chromebook to a kid interested in learning to program; also it avoids dealing with a School District IT Department, which have to defend themselves from all kinds of attack from annoying kids and parents, so are probably more technologically conservative then the average IT worker.
So my advice would be: Don't bother trying to provision a chrome-book to connect to some school network. Use a school-issued chromebook for school stuff (if that's what they issue...), use a normal PC for extracurricular learning.
For the record: my kids are in elementary school, and are issued lenovo laptops running windows. They are locked down to the point where they might as well be chromebooks; kids have unprivileged accounts and are allowed to run very few programs. This is as it should be; those computers are for a very specific purpose, and are not general purpose toys.
> a School District IT Department, which have to defend themselves from all kinds of attack from annoying kids
Indeed, when I was in school, the WiFi networks were very poorly secured, so it was easy for annoying kids to get their own computers onto school networks if other students were using school-issued laptops around them. Annoying!
I never said they did a great job keeping the network secure, I only meant to imply that they tend to default to "no" when asked for any kind of technical permission.
Schools typically don't allow BYOD policies because of support costs and equitability between students. Assuming a school district even did allow this, they would only allow the student to use a managed Chrome profile and the school's device policy would lock out the Linux VM option and everything else that might become an in-class distraction.
If a kid wants to learn how to program, they're going to have to bring their own separate computer and it will be treated about the same as bringing their smartphone to class, i.e. not allowed except during very specific times, there would be concerns about liability of damage or theft from other students, and they probably wouldn't allow it on the school networks.
Can confirm no-BYOD policy is typical. I had to whine directly and without invitation to school principal to get an exemption for daughter. The trouble with no-BYOD is the kid must bring the school-controlled Chromebook home and connect to the home network for homework (which often requires Chromebook). Many US middle and high schools have an IT department of 1 or 2 people; it introduces abuse risk I think schools in general are not appreciating.
I see the problem with Chromebooks and cloud stuff more generally as being that it's difficult to see the productive use-case of programming outside just shuffling a bunch of data around. If your program's not actually doing something useful, it seems like it'd be difficult to imagine a career in it. -But if a kid can get a relay to trigger via button and then maybe via web interface and then maybe automate it, I think that opens the world of hacking up to them. You know, for $10, they can have a fully-solar (w/battery) thermometer or whatever they want -- the thermometer can feed a thermostat to energize a relay coil to start a heater or whatever.
-But I might be outlier, because in school we had robotics class a lot of kids were pumped for, but I was confused because we never did anything useful with them; it was more like an art class, except at least in art class we baked ashtrays for our parents. -But what am I supposed to do with a 5-watt robot that follows yellow tape?
> (just a hypothetical, I assume most parents can't afford to buy one)
It used to be that high school students were required to have a graphing calculator. These had to be purchased by the student (iow by their parents) and without factoring in 20+ years of inflation costed more than some Chromebooks available today. I suspect there were (and still are) financial assistance programs as i've known students living below the poverty line and they were able to meet that requirement.
Most larger school systems (if they allowed it at all) would end up "locking" the device as if it were one of theirs for the duration, just like some companies allow you to bring your own laptop or phone, but it becomes "as if it were theirs" while it is managed.
Support costs, mainly.
A small school that does its own IT is more likely to be flexible.
Your personally owned Chromebook isn’t comparable to a school issued Chromebook at all. They’re more locked down and useless than a stock iPad. Kids cannot install Linux on them.
You commented in context of digital education. The point is that your argument of Chromebooks comparing better to iPads doesn't apply in this situation. In fact they're often worse because schools deploy the cheapest, lowest common denominator Chromebooks with slow CPUs, horrible screen resolutions, inadequate RAM and terrible battery life. Kids hate them. The fact that good and uncrippled Chromebooks exists doesn't help them at all. A 5 year old iPad is likely a better experience and a more capable OS and device than a new Chromebook issued to students this fall, but the warranty and repair costs for schools dealing with careless kids don't add up to less so they get the cheaper option.
> On a Chromebook that I bought and that I fully own I can enable the Linux system and install whatever I want on it (it runs in a VM and it is a full Linux system).
Do you really own it ? Can you install linux or BSD _instead_ of ChromeOS ?
Yes[1], depending on the chromebook / chrometablet it will have varying levels of support for even swapping the firmware and running standard linux/BSD. Sometimes you will need to open up the laptop for a jumper/screw to adjust for enabling firmware flashing. Others its just turning on dev mode first.
Apple has long provided tools for teaching kids how to code. Including lessons targeted at kids in middle schools.
> young coders are asked to assist these characters achieving simple goals by coding simple instructions. As challenges become more difficult, more complex algorithms are required to solve them and new concepts are introduced.
Even then an ipad is not good. An Ipad is good for digital art and thats it. For the same money you can buy a computer capable of 3d modeling, digital art and a drawing tablet buy some paint brushes and clay to do real life art.
Your work Chromebook is completely incomparable to a school issued Chromebook. It's doubtful that your employer locks you out of literally everything that would allow you to develop software on-device. See my other comments in this thread.
People of HN-age are assuming that school Chromebooks are anything like the Apple-IIe or other computers they had "in the computer lab". Those machines had a "purpose" - but they were wide open for investigation by those who wanted to.
They're not. They're locked down as hard as they can be.
> It's doubtful that your employer locks you out of literally everything that would allow you to develop software on-device.
In strongly regulated industries, it is not unusual that you are indeed strongly locked out of this, and you need to create special requests to get access to the specific functionalities (as an exception) that you need for developing software on-device.
Right, many people have to treat their local computer as a thin-client and do everything through a WebEx session or similar means, which makes the local device irrelevant. Or if you're regulated but have to be specifically exempted and allowed to work in a way that schools would never permit, then in that case you'd not be arguing in good faith that kids are able to learn to code and develop on a Chromebook since they can't.
> Or if you're regulated but have to be specifically exempted and allowed to work in a way that schools would never permit, then in that case you'd not be arguing in good faith that kids are able to learn to code and develop on a Chromebook since they can't.
No, I just wanted to show that your claim
> It's doubtful that your employer locks you out of literally everything that would allow you to develop software on-device. See my other comments in this thread.
simply does not hold in practice.
--
Addendum: Additionally, from my school experience, rather the attempts to circumvent "abitrary" restrictions on the computers which were set up by the school made you a good coder. :-)
I sense that your claims and suggestions here strongly suggest that your school experience is not a recent one where you were issued a locked down Chromebook.
I would encourage you to expand your lived experience here. Circumventing "arbitrary" restrictions today will burn a hardware fuse, brick it for actual school allowed purposes and cost your parents $170 to resolve. The age of innocently hacking on school property is long gone.
>
I sense that your claims and suggestions here strongly suggest that your school experience is not a recent one
Of course.
But nevertheless, I have a feeling that the central difference is not in "recent or not", but in the fact that older generations were simply much more rebellious in not wanting to accept the restrictions set on the school computers and willingness to do everything imaginable to circumvent them.
To "force" someone to develop on a Chromebook is like giving someone a bicycle to become a race car driver.
That said, I usually flashed my arduinos and used bare metal C. Ironically I think it makes many things easier to learn and understand, provided you have a programming device.