r/programming • u/SergeantFTC • Nov 22 '16
IntelliJ 2016.3 released
https://blog.jetbrains.com/idea/2016/11/intellij-idea-2016-3-ga-java-8-and-es6-debugger-and-ui-improvements-and-a-ton-more/48
u/rabbitspy Nov 22 '16
I find these point updates annoying. You have to download the full installer and run it, which uninstalls the old version (provided you allow it to do so) and then installs the new one. Why can't their built in updater handle this?
It becomes even more annoying when you have multiple products installers such as WebStorm, IDEA, DataGrip, etc.
37
u/callcifer Nov 22 '16 edited Nov 23 '16
when you have multiple products installers such as WebStorm, IDEA, DataGrip, etc.
Have you tried Toolbox?
5
2
u/egeozcan Nov 23 '16
That page is for toolbox subscription. The app itself can be found here: https://www.jetbrains.com/toolbox/app/
1
1
Nov 23 '16
I have now! Thank you. Still sucks that it doesn't detect manually installed versions, but this is better.
No project window resizing yet, I see.
1
u/cyanballoon Nov 24 '16
This is great, I wonder why it's not built-in similar to Adobe's Creative Suites.
15
u/simion314 Nov 22 '16
I think the reason is that is a major update, it could break some things/plugins , so you could keep 2 versions if you want, run the new one if all works fine but if you have problems or missing plugin you can use the old version ofr more time.
4
u/wildjokers Nov 22 '16
Not sure how it is on Windows but on a Mac even though you are installing a full version again it is very seamless. When it starts up it simply asks you to import settings from a previous version (the location of which it already has pre-selected) and off you go. It asked to update a few plugins too (markdown, IdeaVIM, bash support, etc). I was up and coding again in less than 5 minutes.
3
Nov 23 '16
Yeah. It's annoying on Linux because there's no real installer. It's solved by keeping multiple versions in a directory, symlinking the current one, and manually creating / updating shortcuts. It's not the worst thing, but it's weird for such a slick product to do so DIY about these things.
11
u/wildjokers Nov 22 '16
I haven't been using the 2016.3 EAPs so just now getting a look at the new features. I am already really liking semantic highlighting and the inline parameter name hints.
I can already see how semantic highlighting is going to be a feature I have no idea how I lived without for 13 years.
3
u/justaphpguy Nov 23 '16
Oh boy I love semantic highlighting!
Took a while to get used to and since I'm running a custom color scheme I had to fiddle a while to get useful color/variations.
However don't want to go back!
Also only after a while I realized it's not picking the sem. colors in order but according to the symbols name. So I think same symbol in different context has the same color.
-1
4
u/jetrii Nov 22 '16
Perfectly valid Java code that compiled in IntelliJ 2016.2 doesn't compile in IntelliJ 2016.3. Very minor refactor to fix it, but still annoying. And yes, I checked the JDK version.
10
6
u/callcifer Nov 22 '16
Just curious, can you share the code (just the problematic bit)?
7
u/jetrii Nov 22 '16
V largest = FluentIterable.from(col).toSortedList(desc()).get(0);doesn't work but the following does:
List<V> sortedCol = FluentIterable.from(col).toSortedList(desc()); V largest = sortedCol.get(0);2
2
u/Gosig Nov 23 '16
Do you use javac or the eclipse compiler? I've noticed a lot of minor inconsistencies between them and intelij updated the eclipse compiler in this version.
1
-15
u/elucidatum Nov 22 '16
Too bad they moved to subscription billing, which is the stupidest model for development software ever, where after 1 year your entire IDE reverts to the version that existed when you bought it. Great way to completely corrupt an entire project and force subscription lock-in.
I used to love JetBrains products but I avoid them like the plague now.
Perfect example of hiring mindless middle managers with zero understanding of the product and the problem domain, trying to squeeze blood from a turnip.
Very sad!
16
u/SergeantFTC Nov 22 '16
Great way to completely corrupt an entire project and force subscription lock-in.
How does switching to an older version corrupt an entire project? Is your code somehow dependent on the IDE? The IDE is just a tool, the code shouldn't be dependent on it whatsoever.
6
u/bdavisx Nov 22 '16
Some of the settings stored in IDE specific files might not be compatible (although I don't know if that's the case, just guessing).
While that's a bit of a pain, it's not world stopping. As long as you're using some kind of build tool (Maven, Gradle, SBT, etc.) then worst case scenario is that you would have to wipe out the IDE specific files and re-import from the build file(s).
9
u/SergeantFTC Nov 22 '16
Exactly. I don't get why people act like it's a dealbreaker. A build system is really a must for anything remotely complex.
-13
u/elucidatum Nov 22 '16
It's a dealbreaker because there are superior alternatives, both paid and FOSS, that don't introduce uncertain edgecases with forced reversions due to petty profiteering.
16
u/Cilph Nov 22 '16
There is no superiour alternative to IntelliJ and it is well worth the money over Eclipse. And you always have the free Community Edition.
0
5
u/tomservo291 Nov 23 '16
There's no uncertain edge cases... You use a standard build tool for your language (ex: Maven for Java).
IDEA imports your pom.xml and creates a project and it just works. You don't need to commit literally any IDE specific files, whatsoever. If you are, you're doing it wrong.
6
u/Stickiler Nov 22 '16
The only forced reversion is the reversion to the version you actually paid for.
Old model: Pay upfront for a licence fee to current version, get no updates, pay extra for 12 months of updates.
New model: Agree to pay for 12 months of subscription, get licence to current version, and can trial all updates for 12 months, but if you don't keep your subscription going, those updates go away, because you haven't actually paid for them, they're just letting you try them out so you can decide if you want to keep your subscription going or not.
You're still paying a set price for the current version, that price is just spread over 12 months, and same for the 12 months of updates.
-8
u/elucidatum Nov 22 '16
If you're a new customer that doesn't know any better, I'm sure this makes complete sense to you. For everyone else who's been buying IDE software before the idiotic "subscription software fad" came onto the scene, this is a massive reduction in customer expectations.
Going from paying for 12 months of updates from date of purchase to paying for a "trial" of 12 months of updates that revert at subscription expiration is one of the biggest slights of customer expectations I've ever witnesses in this field.
Do you remember this fucking bullshit?
Yeah, that little issue with anyone being able to perform remote code execution with elevated privileges on your machine through the local IntelliJ webserver just by visiting any webpage that was aware of the exploit.
If you're OK with your software potentially reverting to a version that turns your development machine into security swiss cheese 12 months after the fact, sorry to tell you little buddy, but you don't belong in software development.
11
u/afastow Nov 22 '16
It says very clearly in your link that updates for the security vulnerability were made available for all versions, even 4 year old ones, that were affected.
4
u/Stickiler Nov 22 '16
You can still pay upfront for a year, which gives you the current version literally identically to how the old system worked.
And you don't pay for the trial, you pay for the current version, and they allow you to install and use newer versions, which you haven't paid for, for a year, so you can try them out and determine whether it's worth upgrading to those versions.
Also, as /u/afastow said, they gave a fix for that security vulnerability to all versions.
-6
u/elucidatum Nov 22 '16
Is your code somehow dependent on the IDE?
With certain advanced IDE features, especially pertaining to automated features, yes, this can absolutely be the case that code integrity, and most importantly developer familiarity with the code can become dependent on the IDE.
A lot can change featurewise in a single year. If some killer feature is introduced mid-cycle, like new refactoring tools or intellisense objectives, etc. then reverting to a 365 day old version can critically endanger developer productivity and familiarity with the project.
Then there are the aforementioned automated effects, like customized code formatting being overwritten project-wide by defaults on first load during an IDE version change, which I've had an issue with personally.
It's just a bad business model for development software that introduces unnecessary and potentially critical edgecases, full stop.
4
u/Gosig Nov 23 '16
Then just don't install any version updates if you're not planning to continue your subscription. It's pretty damn straightforward.
10
u/wildjokers Nov 22 '16
For me, their change in licensing model hasn't made the slightest difference since I always updated every year anyway.
Now if you want to see a company with a horrible licensing model look no further than ZeroTurnaround (e.g. their JRebel product). At the end of the year it simply disables itself. You can't even use it anymore.
1
u/elucidatum Nov 22 '16
since I always updated every year anyway.
Well, this is exactly what they want so of course you wouldn't notice or care.
However, I know explicitly that a number of largish development shops with common industry acquisition requirements that don't align with the subscription model, have completely abandoned JetBrains products, as well as most of my personal freelancer associates.
It's just bad business to lower customer expectations of software functionality in something as critical as software development by greedy executives and mindless middle managers who only care about quarterly returns.
7
u/SemaphoreBingo Nov 22 '16
If they're a large shop, why aren't they used to paying on a subscription model for enterprise software already?
0
u/elucidatum Nov 22 '16
I don't know, perhaps ask the US Federal Govt. why they're still using Windows XP?
6
u/SemaphoreBingo Nov 23 '16
Are you seriously suggesting that the feds aren't paying truckloads of money every thirty days to all sorts of enterprise vendors for software subscriptions.
3
u/schema9000 Nov 22 '16
common industry acquisition requirements that don't align with the subscription model
That makes no sense whatsoever.
4
u/Xerxero Nov 22 '16 edited Nov 22 '16
I thought to that patch level. So if your subscription runs out tomorrow you can run 2016.3
At least that is how I remember reading it somewhere but that was some time ago.
3
u/elucidatum Nov 22 '16
Nope. That was the old model, where at the end of your license, you retained the most current version at the time of license expiration.
Now, once your subscription runs out, if you don't resubscribe, your license is only valid for the version you bought exactly 365 days ago, which means a complete reversion with absolutely no patches or updates past the very first day that you bought the software.
My mind recoils in horror at the stupidity.
9
u/Derimagia Nov 23 '16
Nope, bug fix releases/patches are given to you.
https://sales.jetbrains.com/hc/en-gb/articles/207240845-What-is-perpetual-fallback-license-
4
Nov 22 '16
it's strange. I loved jetbrains and always bought their licenses once a year so a subscription wouldn't hurt me as it doesn't change anything but I, somehow, felt "betrayed"; I can't really describe the feeling but their new way of handling licenses made me re-evaluate other open source products and I realized that I simply don't need jetbrains anymore.
I simply don't want subscriptions. I want to pay for a year of updates.
3
1
u/neitz Nov 22 '16 edited Nov 22 '16
My upgrade subscription (not part of the new subscription system) just ran out. Of course they wait to release all the Q3 products until right after this happens :P
Same here, hoping Visual Studio "15"s improvements are enough to drop ReSharper and it's surrounding ecosystem for good.
It might sound petty, but I did not mind paying slightly higher prices for an actual license. This way I knew that if my freelancing situation changed and I did not want to upgrade I wouldn't be set back to tools from a year ago. I knew that the product I paid for was mine to use as long as I needed.
5
u/Stickiler Nov 22 '16
You still get an actual licence.
Old model: Pay upfront for a licence fee to current version, get no updates, pay extra for 12 months of updates.
New model: Agree to pay for 12 months of subscription, get licence to current version, and can trial all updates for 12 months, but if you don't keep your subscription going, those updates go away, because you haven't actually paid for them, they're just letting you try them out so you can decide if you want to keep your subscription going or not.
You're still paying a set price for the current version, that price is just spread over 12 months, and same for the 12 months of updates.
2
u/neitz Nov 22 '16 edited Nov 22 '16
Actually on the old model I got all updates for free until the next major version or 1 year later, whichever came first. This included bug fixes, performance fixes, and new features. It was nice because the product was actually supported.
Now I can buy it, and then a month later they could release a huge performance or bug fix and I'd have to buy it again to lock it in. They essentially are forcing you to pay for bug fixes within a rolling release model.
Again I am not trying to be cheap (I have a full budget for professional tools). I just like a company that stands by its product and I don't like paying for new features before I even know what they are.
I also have to keep track of which "features" I have paid for and which might be going away at some point if I cancel. This is really annoying.
6
u/Stickiler Nov 22 '16
You still get updates to the version you paid for, for free, the versions have just changed to a rolling release, so you pay for 2016.1, and you get all sub patches for 2016.1, but you don't get 2016.2
I don't like paying for new features before I even know what they are.
The new subscription model actually fixes this problem compared to the old one. With the new model, you pay for the current version, but you can then try out all their new versions for a year, so you can determine whether those versions have features that make it worthwhile paying for another year and getting those versions. If you determine that nothing in them entices you, you just switch back to the version you have a licence for and you're fine.
4
u/SergeantFTC Nov 22 '16 edited Nov 22 '16
After updating via the Jetbrains Toolbox utility, I get a dialog box saying that the main method could not be invoked. Looks like a very useful update if you can get it to work though.
Edit: https://youtrack.jetbrains.com/issue/IDEA-164286