Unfortunately VS for Mac currently doesn't support Python or R (the two languages our team supports). However, if you are interested, please file the request on uservocie - that really helps us convince mgmt.
Meanwhile, VS Code has pretty decent Python support which can be used on Windows, MacOS and Linux:
Visual Studio for the Mac is a re-branding of Xamarin Studio, so it doesn't actually share any code with Visual Studio for Windows. I doubt that VS Windows plugins will ever work with it.
Agreed. I think Technical Debt is used incorrectly here, I only consider items debt once they are merged and are intended to be fixed at a future time.
I love the one for iOS development. It's perfect even for people new to programming. Will you ever re-write the Andriod version to be just as beginner friendly? I would love to hand it off to my girlfriend so she can learn how to do apps. Right now it is harder to grok than the iOS one.
KG4ZHA here. I have been doing it for a little over 10 years now. I second the Baofeng recommendation, it is a great starter radio and you will be able to find a local 2m repeater to participate in.
I would also recommend looking for a local radio club, or see if ARES has an organization in your area.
While not required anymore for HF, I have the most fun with CW. It is amazing what some of the small 1-5w QRP radios are capable of these days. There are plenty of small kits that will get you on the air in an afternoon of assembly.
I'm interested in more information about why you decided to alter GOMAXPROCS and what your results were from testing.
I've had a play with this myself and found that it cause sporadic and unpredictable crashing (very different style of application though - I was building a webserver). However this was an earlier iteration of Go (possibly Go 1.1 but likely 1.2) so things may have improved since then, or you might have found a saner way of tweaking it.
When GOMAXPROCS > 1, your program goes from "everything is executed sequentially" to "everything is maybe executed in parallel." This can expose data race bugs in your code that aren't present when GOMAXPROCS = 1.
You know, that's entirely possible. I was playing around with different methods of passing data between goroutines for increasing performance and I knew one of the methods I was testing wasn't idiomatic Go. However since I wasn't getting race conditions normally i assumed that the GOMAXPROCS fault wasn't down to my shonky code.
The weird thing is I thought I'd read somewhere that said Go defaulted to a process per CPU core (like the OP has hardcoded ib this project). I'm guessing that isn't the case then? It sadly wouldn't be the first time I've misread something! :(
If you contact me (twitter @leehambley, or email address in my HN profile) I'll be happy to share a video demo with you when we have one, we're just finished with our production-like staging environment, and we're going to spend the next few weeks ironing out bugs before launching a limited alpha in the new year. As I mentioned somewhere else in the comments, that landing page is super, super "too marketing", and I personally don't like it too much, but it's not for "us" (technical folk) and it's certainly not for HN. I plan on making a technical release page which is heavier on concrete design, use-cases, and etc. But, unfortunately cnolden jumped the gun and submitted (he's not affiliated with us) the page to HN!
I'm not an expert on licensing, but couldn't Apple continue using the current version of mogenerator? A license change would only prevent them from taking latest.
Right, but that would mean that mogenator could change the names of the class methods (or add additional ones) without having to worry that Apple would adopt them in a later update and thus render the whole exercise moot.