Slashdot Mirror
Ditch Linux For Windows 10 On Your Raspberry Pi With Microsoft's IoT Kit
An anonymous reader writes: Partnering with Adafruit, Microsoft has announced the Windows IoT Core Starter Kit. The $75 kit comes comes with an SD card preloaded with Windows 10 IoT. According to the Raspberry Pi blog: "The pack is available with a Pi 2 for people who are are new to Raspberry Pi or who'd like a dedicated device for their projects, or without one for those who'll be using a Pi they already own. The box contains an SD card with Windows 10 Core and a case, power supply, wifi module and Ethernet cable for your Pi; a breadboard, jumper wires and components including LEDs, potentiometers and switches; and sensors for light, colour, temperature and pressure. There's everything you need to start building."
It's perfect. Now my Pi can have Telemetry!
DirectX ought to come in handy, too.
why the hell would I want to do that?
Build your own Raspberry Pi kit. It will be cheaper.
Dumping a system that works and does what I want for a system that spies on me and will change at the whim of its maker with but a "swallow bitch" if I complain.
Decisions, decisions...
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
As if IoT wasn't insecure enough already - let's put the BIGGEST consumer malware target into everything!
Anyone else think this is bad idea?
A thousand pounds of wood moving at 300 feet per minute. Don't get in the way.
is the year that Windows will replace Linux on the IoT.
'why' for developers and 'why' for microsoft as well.
For developers, MS is so mismatched to the sensibilities of the embedded space, business and technology wise. Picking up the ball and going home from one linux to another or even to something like a BSD is easy enough if you have to. If you commit to MS ecosystem, there's no where to go if things pan out poorly (e.g, Windows mobile, windows ce, windows phone (at least 7 was a dead end), Windows RT). MS has a terrible track record in this space, even when their wheelhouse of desktop application ecosystem has some relevance, where the Pi has pretty much no relevance (it may have video out, but there are better choices for even ARM based graphical systems than Pi). MS ecosystem is in general so *alien* compared to the rest of the industry, you *really* have to believe in it to commit. It's silly to bet your project on MS's technology and ongoing commitment to the platform in this market.
For MS, what do they hope to get out of this? They are coming into this from behind, against a competitor that gives away for free and where the entire ecosystem is tilted against them. They are going in to explore with no royalties, and no path to profit, or even revenue. Incidentally this has some resemblance to when they tried to break into 'supercomputing' nearly a decade ago, only to give up and let the resources mostly scatter to the winds when they figured out that there was no money to be made in the market, despite the prestige.
XML is like violence. If it doesn't solve the problem, use more.
just trying to make sure all iterations of "no" are covered.
How much would you pay to have a software development platform that is more difficult to use? $25? $50? no, for only $74.99 you too can run a limited subset of Windows kernel on Raspberry Pi! (plus $0.01 handling)
This is sort of like the opposite philosophy of Ardunio, instead of a simple IDE where people can get things done you can have a hairy ball of software and expensive tools where few people (if any) get to making their projects go.
Linux on the target plus eclipse/emacs/vi/whatever on the host is all you really need to make a RPi go. There are cross compile suites for Windows and Mac, and they tend to integrate with most IDEs (maybe not so well with Visual Studio, but if you really want that option I guess Window IoT is made just for you)
“Common sense is not so common.” — Voltaire
There were a ton of misconceptions and two tons of lies/crap (can't tell which) going on over at the Ars Technica comments thread about this earlier today.
1) Windows 10 IoT is free. There is no paid-for version of WinIoT. (And you thought "WinCE" was a bad nickname...) .Net Micro Framework (NetMF), which is a stripped-down version of the standard .Net Framework (NetFX). It shares virtually nothing in common with the old .Net Compact Framework (NetCF), and is, in fact, less stripped-down than that. .Net and the rest of Windows. Nobody (reasonable) gets belligerent and calls you an asshole because you use Linux, so have the same consideration for those that work with, or even *gasp* like, WinIoT.
2) WinIoT is NOT based on the main WinNT kernel. It's based on good-old Windows Embedded Handheld, not Windows Embedded Compact. WinEC is based on WinXP, and is thus part of mainline NT, but WinEH is based on WinCE.
3) It uses
4) If you like Linux, then use it. The reason to use WinIoT is if you already have a ton of experience working with
5) WinIoT doesn't spy. It's too stripped-down to do most of that telemetry crap, and people (even "true believers") would piss/bitch/moan/threaten-mob-action if they were to waste precious processor cycles on an embedded platform for that crap anyway.
6) WinIoT doesn't auto-update. Again, people would be pissed off if their "things" suddenly stopped working because an update broke compatibility. Not gonna happen. (Also, it's WinCE, so it never had an update cycle to begin with.)
Now that that's all out of the way, there can be a civil discussion (read: no discussion, because this is the internet, and everyone hates everyone else).
I remember when Microsoft used to try to compete against us with Windows NT replacing OS/2 (OS/2!!!) on ATM machines. It took them a very, very long time.
I remember when Microsoft used to try to compete against IBM embedded PC/DOS on handhelds. It took them a very, very long time.
Now I shudder at the thought that they might just impact on IoT. They've started late, and it may take them a very, very long time but they are a relentless, well-funded and Government approved software company. This is a genuine threat, people and you shouldn't just laugh it off.
To start with, I have to dedicate a PC to Windows 10 in order to do Windows development for my Pi 2?
.NET APIs, viruses, trojans, and whatnot infesting on the Windows 10 ecosystem.
Or, I can continue to run Raspbian (Debian) on the Pi and host development on the Pi, or do cross-development on other Linux hosts or my Mac.
I know the overhead/footprint Raspbian imposes, and I know how to carve out the bits I don't need.
How do I do that with Windows 10?
Easy! Stick to Raspbian!
Oh, I realize I won't have access to the latest development tools like Visual Studio,
Thanks, I'll stick with Raspbian on the Pi, and not having to support a separate Windows 10 box as well.
Because Windows on ARM has been nothing but a giant success so far.
If it ain't broke, don't fix it.
It might be nice having a ms honey pot ...
With the impending IoT, I suspect that eventually, actual jars of honey will have IP addresses ... allowing one to make the metaphor a reality.
It must have been something you assimilated. . . .
It doesn't come with a GUI, so if you want a working display, you need Linux.
I don't think anyone has ever said those words before.