If you're switching from LabView to Python because it's an open, popular, well-supported language that's easy to find experienced programmers for, I can't recommend learning anything other than git for version control. SVN works, yes, and lots of people have previous experience with it, yes, but git is ubiquitous and there are lots of excellent tutorials that should have your team up and running on it in less than an hour. My biggest difficulty in moving from SVN to git was not git, but rather un-learning SVN and the assumptions and mindset needed to use it effectively.
There's the added bonus of finding extremely inexpensive ($25/month) git hosting (GitHub) for private teams of unlimited size.

I should have looked more carefully. Apparently the diagnosing doctor DOES provide homeopathic treatments!
http://drhubbuch.com/patient-c...

I propose a novel treatment:
Seal pure water into a container and place it into a microwave oven for 1 millisecond (or a microsecond for extreme cases). Sell it as a homopathic treatment for $50/ounce.

Sure, but imagine a kid as agoraphobia and can't stand being in the open air. Is it reasonable for the parents to expect the school to put the football field inside of a building so the kid can be on the team? Also there is absolutely no evidence that EHS itself exists, which is what the parents claim. The child would be better off if the parents admitted that it was a psychiatric disorder and started getting the kid treatment for it. The ADA has limits on what accommodations an employer, or school has to make for somebody disabled. My understanding is they tend to be limited to making spaces mobility-accessible and ergonomic accommodations to their personal workspace/desk and not wide-ranging changes to the work environment to accommodate a severe psychological disorder.

The problem, as I understand it, in standardized (CORE) testing in mathematics is not that ALL the students are made to learn how to add, subtract and multiply, but that the test makes extremely specific assumptions about PRECISELY what method that the student was taught in order to make use of those operations. For example, I believe it is common for the standardized tests to assume that students do all of their basic arithmetic by using number-lines in a very specific way. If, instead, the student was taught to do arithmetic using any of the MANY, MANY other methods out there instead of the number-line method (which I personally think is slow and stupid) they will flunk because they must show every step of the problem on a number-line, regardless of the resulting answer the student supplies.
I can't imagine a more soul-sucking task for a teacher then to have to re-teach their students how to do their math problems in an objectively WORSE manner than the one that the teacher had been, JUST so that the class doesn't fail their standardized tests and the teacher/school isn't penalized. This is exactly how you discourage passionate individuals from becoming teachers.

Sorry, momentarily confused Wine and Mono. Wine has never been legally challenged by Microsoft and the development of it has been done clean-room, leaving MS with no legal recourse unless they can demonstrate otherwise. Personally, I don't think they care at all about the existence of wine at this point.

MS has basically gifted the Win32 and .NET APIs to Wine. MS is actually now actively involved in Wine's development. (Believe it or not) Wine is now a targeted and supported runtime environment for ASP.NET5, meaning that if something in ASP.NET5 fails to work on Wine, MS will either work around it in ASP.NET5 or help contribute a patch to Wine (if it's a bug in Wine). Samba's legal situation has been more contentious in the past, with MS basically insisting that it was impossible to reverse-engineer it without breaking license agreements. Ultimately, 8 years ago, Samba, MS and the courts hand-waved together an arrangement that allowed a 3rd-party organization (PFIF) to legally provide the technical specifications to the Samba group.

I see these as being two pretty different things, though. Wine is an implementation of Win32 (and .NET), which is an API specifically provided to the general public as a development API right from the very beginning. Samba is an implementation of a bunch of networking protocols that were originally only intended to be implemented by MS itself, or partners that were very deep in bed with them.

Personally, I believe that either of them should be allowed to be reverse engineered, but they're still somewhat different.

Having had personal technical experience with both Java ME and Android, I gotta say that from a technology point of view, Java ME was a complete and total dead-end. It was far, far different from vanilla desktop/server java than Android is and therefore had practically zero notice or integration with the Java ecosystem. It was designed to work within the restrictions of devices that had single or double-digit CPU MHz and RAM MBs. It was modelled around Java 1.1, with almost no new language features or APIs. RIM used it as the basis for Blackberry and as a developer, I can tell you it was a decision they regretted.

Android is essentially vanilla Java with only the most esoteric of APIs removed from it, and then device-specific APIs placed on top of it. You can use 95% of existing java desktop/server libraries without any modification. If Google was given the option of using Java ME absolutely for free, or developing their own language and APIs, I guarantee they would have made their own because there would have been a riot among their software developers who would have been forced to essentially develop all of the libraries and google apps using the software equivalent of alphabet blocks and duplo. The additional "device profiles" that were subsequently released were too little, too late and hardly any of them were adopted into devices. I can't imagine any situation where Google would have paid Sun or Oracle for a Java ME license.

You know that Kim Stanley Robinson and Spider Robinson aren't related, right?

How does a tool that allows you to re-work your existing iOS or Android source projects into Win10 projects compare to a tool that allows you to convert a document from 1-2-3 or WP into Excel/Word? Or rather, how could it possibly lock a software developer into the Windows platform? This is more like a life-support tactic to allow developers to publish to mobile Windows with minimal effort, with the hope that the platform catches enough traction that developers would start developing native Windows 10 mobile apps. This is identical to what Blackberry did with BB10 to allow developers to publish Android apps that supported it (which I've done at my work). That certainly did absolutely nothing to lock me into the BB10 platform (though it did not make me want to develop for the platform any more than I did).

Why would they want to do this? MS providing a "reworking"/"publishing" tool that lets you easily port iOS and Android apps to Win10 means that more developers are targeting non-MS platforms as their primary platforms. This sounds more like MS is signalling, "We haven't been very successful with this, so we're going to follow your lead for now." There's been a pretty radical culture change in the DevTools/Frameworks/Runtimes teams at Microsoft, signalled by the fact that all of their core runtimes and web frameworks are 100% open source (APL2), published on GitHub (https://github.com/aspnet) and are directly accepting and responding to issue reports and pull requests on these projects. Their new DNX runtime (in preview right now) targets Windows, Linux and MacOS (through Wine, which they are contributing to) and (almost) all of their example code for the new ASPNET5 frameworks is developable and deployable on all three platforms.
3 years ago I would never imagine myself ever recommending any MS development tools to anybody, but here I am now
Btw, Visual Studio 2015 Pro is now 100% free for small organizations or open source projects (branded as Community edition).

I think you might misunderstand how sonar scales in range and intensity. Think of water as being much less like perfectly-transparent air, and more like a light, but continuous fog. After a certain distance, increasing the intensity of sonar will only give you a marginal increase in range, since a certain portion of your signal will end up scattered back at your hydrophones. No matter how 'noisy' they are, there's really absolutely nothing a surface ship can do to ensure they can detect a deep and silent running submarine that really doesn't want to be detected. It's also much easier to design a submarine to mask its active sonar (reflective) signal. Typically, detecting a submarine is more about having better 'eyes' than it does having brighter 'lights'.

To add some data to the current replies to this comment, I suggest you look at the graph here: https://www.census.gov/populat... Between the growth peak in the early 60s of over 2%, we've reduced it to %1. The latest annual letter from the Gates Foundation provides some good background about what's ACTUALLY been improving in the world: http://annualletter.gatesfound...

The problem is: current CPU designs are frequently limited by wire propagation delays. Optical circuits do have somewhat faster propagation than copper (1c vs 0.75c), but increasing the size of components necessarily increases the distance between them. 1 thz = 1 * 10^-12 light seconds, which is 0.3mm, I believe.

This is just simply false. There's nothing in the GPL that prohibits releasing software on the App Store. Why would you think this?