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?
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.
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.
I did a while ago. But you still need win 10 as a development station for Windows 10 IoT Core. kinda lame.
http://ms-iot.github.io/content/en-US/win10/SetupPCRPI.htm
"
To setup your Windows 10 IoT Core development PC, you first need to install the following:
Make sure you are running the public release of Windows 10 (version 10240) or better. You can upgrade from here. If you are already running Windows 10, you can find your current build number by clicking the start button and typing “winver” and hitting enter.
Install Visual Studio 2015
We recommend Community Edition.
If you already have or choose to install Visual Studio Professional 2015 or Visual Studio Enterprise 2015 (available here), make sure to do a Custom install and select the checkbox Universal Windows App Development Tools -> Tools and Windows SDK.
Install Windows IoT Core Project Templates from here. Alternatively, the templates can be found by searching for Windows IoT Core Project Templates in the Visual Studio Gallery or directly from Visual Studio in the Extension and Updates dialog (Tools > Extensions and Updates > Online).
Make sure you’ve enabled developer mode by following these instructions."
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).
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.