SoylentNews is people
SoylentNews
Robert Pogson reports:
Recent news about the popularity of Chromebooks with schools may seem puzzling.
Schools in Hillsborough, New Jersey decided to make an experiment out of its own program. Beginning in 2012, 200 students were given iPads and 200 students were given Chromebooks. After receiving feedback from both students and teachers, the schools sold off their iPads and bought 4,600 Chromebooks.
After all, a keyboard is a great input device and writing is one of the three "Rs" but why not just [buy] a notebook PC? The answer is that the high cost of maintaining the legacy PC is too great. Keeping content on the server makes the job easier and with Chromebooks, schools don't even need to own the server.
...then there's the malware, the slowing down, the re-re-rebooting with that other OS.
That makes the ChromeBook a winner in education and probably a lot of organizations large and small, even consumers. Of course, they could get those benefits with GNU/Linux but it would take more technical knowledge. Again Chromebooks win.
See iPad vs. Chromebook For Students
(Score: 2) by choose another one on Thursday August 14 2014, @01:39AM
If there is _one_ thing I've taken from my learning experiences with computers, from school kid, through college student, programmer and guy-who-hires-programmers, it is that learning _only_ _one_ of pretty much _anything_ in computing (but particularly platform, OS, and programming language) is a really spectacularly BAD idea - and it does not matter _which_ one it is. It is incredibly short sighted, breeds an insular inflexible outlook, inability to appreciate strengths and weaknesses of different solutions, and means that you cannot demonstrate to future employers an ability to adapt and learn something new.
In 30 years college + commercial experience I've used (as end user, developer or admin) at least 10 major different OSes (that I can remember), so that's changing about once every 3yrs on average (of course in reality, some overlapped). Note: that is _not_ counting OS versions, not counting mobile, not counting embedded / custom OSes for particular projects, and not counting OSes I only played with or tried out - only ones that I used significantly for at least a year. For programming languages, text editors and compilers, multiply that number up by a few (I've lost count).
I've been to job interviews where I had never used the target OS, or compiler/toolchain, and barely knew the target language. I was successful, in the interview and the job, those that hired me knew that I could do it because of what _else_ I knew. Similarly if I am hiring have a candidate who knows one language, the one for the project, and one who knows ten but not the one for the project, who will I favour ? Maybe that makes me strange in the world of HR-droids asking for 5yrs experience in a language that has only existed for 3, but it hasn't failed me yet, and when the PHB wants the next project done in buzzword-lange-du-jour, I know I have a team that will cope.
If my kids' school system is short sighted enough to _only_ teach them one OS, then I will ensure they learn about, and to use, others (note the plural). Anything else is just failing to prepare them for the future - because it _will_ be different, and it _will_ involve change.
But, you go ahead and teach kids just the one true language on the one true OS - just so long as you understand that that is Fortran 77 on VAX/VMS (first job - "learn this right, it's all you'll ever need"...).
(Score: 0) by Anonymous Coward on Thursday August 14 2014, @06:07AM
I amend my statement:
The oldest/earliest of his students probably -had- used Windoze.
When Pogson got to his first teaching assignment, he had a bunch of Lose95 boxes that were infected to the gunwales and were laying idle.
With the M$ OS those were running, he couldn't keep the boxes he had up very long and the amount of time he wasted on de-crapping boxes drove him to Linux.
...then there were the licensing restrictions (specifically, networking).
.
Schools should teach CONCEPTS.
Once the kids have those, they should be able to extrapolate.
Teaching where to click in a particular app is just silly.
("Industry standard apps" have been mentioned in this thread.
Think of the kids who were taught that it was useful to memorize menu locations in M$Office just before "The Ribbon" was introduced.)
If a language|app|protocol isn't cross-platform, I question the utility of that something.
Again: Teach CONCEPTS.
...and if you didn't read my post about Pogson in a previous thread:
He was in the Great White North working with First Nation kids.
They didn't have a pot to piss in.
The freight charge to fly something in added significantly to the purchase price.
Pogson discovered that having Linux Just Work(tm) on his old gear allowed his kids do computing with modern, supported software without wasting a dime on that software.
That was another good lesson for the kids to learn.
-- gewg_