Speaking of VIMs - I suppose I could possible live with booting up in BootCamp - as against using Parallels.
I’m trying to avoid going down the route of a new PC - maybe one of those NUC’s - headless - since I currently work on my iMac for coding purposes remotely using a macbook anyway so headless would be ok. ( but took a look at a UK company specialising in NUCs and after configuring up to 16GB they aren’t cheap - another reason to stick with my 16GB i5 iMac )
Running OSX in a VM from Windows is technically against their TOS, but I think it’s a pretty asinine rule since I paid for the OS. VMWare has a flag now that prevents you from doing it, but it’s still easily done and runs just as well in a VM as it does on hardware. This isn’t really the place to bring that conversation though!
Something to keep in mind - VS is free now, but Resharper (and a lot of the other best extensions) are NOT free. VS alone does not solve the JUCE #include namespace problems at all. You have to install Resharper C++, disable VS’s intellisense squigglies, and enable Resharper’s version. That does fix every JUCE issue though! I haven’t hit any problems in a couple months. Everything’s parsed and located fine, jumping to declarations/definitions in the JUCE source from your own code works fine, intellisense/autocomplete picks everything up fine, auto generating virtual/pure virtual method skeletons after inheriting from a JUCE class works fine, etc. Pretty hard to go back to using anything else after seeing it in action
I would love to hear if anyone from the JUCE team has anything to say about this namespace issue. I know in the past they’ve basically said “it’s up to Microsoft to fix their shit” but it’s pretty clear that isn’t going to happen. What’s stopping JUCE from having all its namespaces in-file instead of around the entire module includes?
Is the free version enough for a solo JUCE developer ? or does one end up having to pay more - say for a “pro” VS licence etc in order to get full benefits from VS ?
For JUCE/non-managed C++, the free version of VS is literally identical to the paid version. The only paid-version features I can even think of that could potentially be of any use at all are the automatic UML diagramming stuff (barely above useless at best) and the team integration stuff (totally useless to solo developer). Nothing else you have to pay for applies to JUCE C++ at all, so no worries there
further question for those who know about CLion and reshaper:
Are the features in CLIon ( refactoring etc etc ) on OSX basically the same kind as Resharper on windows ? or does reshaper on windows go a lot further in sexy features than CLIon ?
Now that it looks like CLion will finally get those JUCE issues fixed are there any significant reasons left IDE-tool-wise as to why i should still consider moving away from OSX to Win10 and VS as my dev tool ?
They’ll be pretty similar. I doubt CLion will have complete feature parity quite yet, but last time I tried it was close enough as to not matter. I like Visual Assist too much to move entirely to CLion personally, but if you’re happy with just VS + Resharper then CLion will fill that need more than well enough that you’d be fine using CLion rather than switching to Win/VS!
With Resharper in VS, how long is the initial parsing (eg how long would I have to wait to use the “find usage” function)? I’m using AppCode on OSX and switching between branches in my project can be a real headache because the reparsing/analysis can take up to 4 or 5 minutes which really breaks flow.
Also AppCode seems to use a ton of CPU, sometimes seemingly randomly and things will get hung up. I’ve turned off all the “Inspections” (basically stuff the compiler can catch anyways) but I still get massive CPU spikes. Does this happen on Resharper?
Great news. Jetbrains released a beta version that works with JUCE!! Just tested it for a few hours and din’t have any issues. Maybe let them know, that this would be great in a major release. I tried AppCode for now, you can just open the project created by the Projucer.
In fact I’m a little unclear about AppCode vs CLion - I thought AppCode was all about iOS/OSX. focusing on Cocoa/ObjC. while CLion was the IDE designed for C++. development on OSX. But reading more just now seems AppCode supports C++. too.
