91–100 of 173 posts
Earlier quoted context omitted.
I imagine you never used VC++ debugger...
I have quite regularly, but I'm just as comfortable in that of Eclipse, Qt Creator, gdb, or even binary debuggers like IDA's or OllyDbg for reverse engineering. I don't see it as a major advantage over any other platform. It's a simple GUI debugger, nothing fancy. Am I missing something?
Sorry, silly question: can one use this Win10 R-pi as a "real computer"? (more to the point: I want to run labview programs on this r-pi, because of its small size/cost -- give/receive triggers various home automation equipment etc., I'm wondering if that'll be possible with this)
You can install LabView on it, just not if the OS is Windows 10 IoT. http://forums.ni.com/t5/LabVIEW-Idea-Exchange/LabVIEW-for-Ra...
Earlier quoted context omitted.
Microsoft just came out with an Android Emulator this year too. It's faster than any other emulator that I've seen and it's really well integrated with Visual Studio. If you've never really used Microsofts tools before and all that you've heard about Microsoft has originated from the crowd that hangs out at HN, you can be forgiven for not knowing that they make very fine quality tools.
I've managed a 25-year career out of staying away from anything Microsoft in the embedded arena. WinCE, WinCE Auto, Windows Embedded, Windows XP Embedded, Windows XP Embedded Cool Ranch Flavor, Windows Mobile, Windows Phone, Windows Phone 8, Windows whatever-the-hell-it-is-today. And that philosophy has saved me a lot of pain over the years. The tools might be great, but I don't ship tools. I ship applications that n…
The flavors of Windows that you mention are part of a longer term story, and are really just two operating systems: Windows CE and Windows NT. Windows CE was important for targeting the small devices of the 90's era in which it was developed. Now we can run NT on the 'small' devices that we have today. I think that's pretty cool. Now we have Linux and NT (and FreeBSD, etc.) and we have more choices.
EDIT: Phrasing
Earlier quoted context omitted.
I don't see how you can practically have an open platform and then close it off to proprietary things.
The commenter isn't saying it should be blocked, they're saying it's against the spirit of openness.
Maybe I'm wrong and they mean a person or organization, in which case I'm not sure who they mean. Windows does not appear on the official Raspberry Pi website front page or blog.
A robotic hockey table doesn't seem very IoT to me. I'm a little confused as to what Windows brings to the table for embedded devices at this point, especially screenless ones.
Microsoft just came out with an Android Emulator this year too. It's faster than any other emulator that I've seen and it's really well integrated with Visual Studio. If you've never really used Microsofts tools before and all that you've heard about Microsoft has originated from the crowd that hangs out at HN, you can be forgiven for not knowing that they make very fine quality tools.
When they released this a couple of months ago I was pretty excited to try it out. I think the barrier to installation is a bit high. First install Windows 10, then custom install of VS, install IoT Templates, then about 30 more steps before you get the image to flash on your SD. How about a link to the image I can blast on the SD and kick the tires without a couple hours of downloading and installing prerequisites?
I really don't understand people who want this, with closed source software the learning stops at some point, you can't learn everything about your Windows-Pi even though it was created for learning! Even the example code (read I2C temp sensor, display using webserver) they give on the home page starts with: "// Copyright (c) Microsoft. All rights reserved.". Why would you want this? Can there really be people that are willing and able to build their own IOT but do not want to learn about Linux?
I just don't get why they would put up a barrier to entry by requiring Windows 10 - at least I can't think of any technical rationale.
probably for the same reason that Apple requires you to own a mac to build an iPhone app
Earlier quoted context omitted.
I use Visual studio to write c# apps for my day job(love it). My Linux development had been polar opposites of spending days getting a embedded arm toolchain to compile and using vim to make a .c file an typing gcc main.c -o HelloWorld . There is also the whole make file strangeness. Where would you point me to make me like linux development more?
I'd recommend Yocto to build a system and toolchain for your target, but it's insanely painful to do anything beyond building a precooked recipe for a known embedded target. Installing an ARM toolchain is simple now. Don't build one unless you really need to (or you install Yocto). apt-get install gcc-arm-linux-gnueabi
Back when I wrote it, in the gcc 4.3.3 days, I don't even think gcc had a release manager --- we're talking clean, out-of-the-box build failures here.
It's gotten a bit better since then, but getting hold of a gcc cross-compiler is still painfully, pointlessly hard.