Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Windows Microsoft Operating Systems

Microsoft Releases Windows 10 IoT Core For Small, Embedded Devices 123

An anonymous reader writes: One of the more interesting aspects of Microsoft's Windows 10 push is their desire to see it running on hobbyist hardware platforms. Today they released Windows 10 IoT Core for the Raspberry Pi 2 and the MinnowBoard Max. They say, "Windows 10 IoT Core is a new edition for Windows targeted towards small, embedded devices that may or may not have screens. For devices with screens, Windows 10 IoT Core does not have a Windows shell experience; instead you can write a Universal Windows app that is the interface and "personality" for your device." Microsoft has posted a list of release notes for this version, calling out improved support for Python and Node.js, significantly improved GPIO performance, and more electronics support for breakout boards. Under a heading cheekily named 'Developers, Developer, Developers,' they lay out their plan for language support and provide a code sample.
This discussion has been archived. No new comments can be posted.

Microsoft Releases Windows 10 IoT Core For Small, Embedded Devices

Comments Filter:
  • I wish they would add Intel Edison support.
  • Given that WinCE has mostly gotten the chop(the sort of legacy customers that remain aren't the kind that you just cut off; but they aren't soliciting new ones); I assume that an NT kernel is included; but given that we are dealing with ARM devices that have a mostly fixed set of hardware included and largely custom add-ons, driver support or binary compatibility aren't going to be selling points.

    So, what do they include, and what is the pitch? Best environment for .net programmers looking to twiddle GPI
  • Anything that runs node.js and python is not part of the I O things. An IOt device is more likely to have 256 bytes not 256MB and be a PIC or an 8051 not a x86 or A9. If it is an overpriced high end device maybe a M0. 8K bytes is a whole universe on an embedded device. An IOt device is a connected sensor or a actuator, not a computer or a web server.
    • by hughbar ( 579555 )
      Yes, agree. The other 'thing' is simplicity, if a sensor is remote, you need crash-proofiness [I made that a fuzzy set, nothing is 100% crash-proof]. That has never been a 'feature' of any version of Windows, complex with the 'wrong sort of complexity'.

      Currently I use Arduinos and compatibles for remote sensors and Pi2 for things I can get my hands on [near at hand time lapse, the garden, the house]. Yes, I could go to tailor made, but I don't need scale currently, so off the shelf is fine. I am looking
  • With multiple "things" throughout a house, office, wherever, it does not make sense for all of them to be heavyweight processors (which I'm assuming a Windows IoT version will need). A Raspberry PI as a controller? Sure. The 100's of "things" it controls are also RPI level of power? Nope, not going to fly.

    The problem with the IoT industry right now is that they are putting *waaay* too much computational power into controlling a thermostat (Nest). The power is not for controlling, sensing or communication,

    • Those $1 devices are going to need to talk to a mothership to work properly though. The Philips lightbulbs do something like this (so I'm told) - you have a 'hub' that's actually on your wifi and it talks to the lightbulbs via proprietary RF. I can see that working quite well for quite a few things, and largely solves the problem of security on low powered devices - although requires the hub is properly secured.

      The obvious next step is to have some sort of 'universal hub' that can talk to multiple little th

  • ....with a 40 page EULA.

    Nope.

"The vast majority of successful major crimes against property are perpetrated by individuals abusing positions of trust." -- Lawrence Dalzell

Working...