JetBrains Moving Its Dev Tools To Subscription Model
esarjeant writes: For many Java developers, IntelliJ has been our predominant IDE. JetBrains is looking to make their tools easier easier to buy and use by switching to a subscription program. Their plan is to have people pay a monthly/yearly fee for access to the tools instead of upgrading when they're ready. Fortunately, if your subscription lapses it looks like you'll have 30 days to check all your stuff in. How does NetBeans look now?
Many members of various developer communities are pushing back against this change: "For a developer with an unstable income, it might be perfectly fine to stay on an older version of the software until they've stashed enough cash to afford the upgrade. That will no longer work." JetBrains has acknowledged the feedback, and say they will act on it.
This is just another example of greedy, rent-seeking behavior, trying to force users to pony up cash on a monthly basis forever and ever and ever...heaven forbid you ever get to actually own anything ever again.
Just cruising through this digital world at 33 1/3 rpm...
I have used it once on a contract and was not impressed with its functionality. There wasn't much difference from other IDEs and most of them are free.
Hmmm, pay for something or use a free one?
If you think Eclipse is bad you haven't seen bad.
If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
... I'd feel a bit better about it, if they actually fixed some of the long-standing rough edges, like the completely-broken built-in compiler behaviour (something that Eclipse, despite being free and generally Old and Busted), and severe lag even on powerful machines, seeing as they're now asking for more money for the same product.
They promised this years ago, and it still hasn't happened. If I'm paying (and now, paying continuously), I'd expect them to lift their game.
Want my money? Give me software that works better than the free alternative.
Just to be clear, "stashing enough cash for to afford the upgrade" means setting aside $100 for the year.
If you have to "stash cash" to afford the upgrade chances are you should save your money; you can get by with Eclipse. I don't approve of the new pricing model, but the "I can no longer afford to be a developer" argument doesn't work. The new model is actually cheaper per year for anyone who always renews their license.
Personally, I prefer to purchase something and be done with it. If I want the upgrade I can purchase that outright as well. If I don't then I think I should be able to continue using what I have already paid for.
in early 2000s. They had an invoicing package designed for print shops. The software was very popular. Apparently just about every print shop in America used it. The software was easy to use, install and maintain. It never broke and didn't need updates The company that made it is tits up. After they were done selling it to all the print shops out there there just wasn't anything left for them, and there weren't enough new print shops to sell to (what with the chains like FedEx/Kinkos muscling in).
Yeah, it's rent seeking, but I don't really see an alternative for a company that makes utility software. It's damned hard to get people to pay for it...
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
I've been using Netbeans since version 3.6 and am quite pleased with how it works, even in the recently released 8.1 beta. I've tried JetBrains and it seems fine enough for what you pay for (except the maven support feels very clunky and not very seamless, IMHO.) But feature comparison vs. price paid? Netbeans wins, hands down. I've tried Eclipse many times over the years also, but come to the same conclusion: I still don't personally like using Eclipse. Therefore I keep going back to Netbeans because it has 90% of what I need and there's plugins for the other missing 5%. The rest? I have a command line and I'm not afraid to use it. You can use whatever tool(s) you like, but I've been coding in Java professionally since 2000 and you can uninstall my copy of Netbeans when you pry my harddrive from my cold, dead hands.
And what if you DON'T think Eclipse is bad? What if you consider it to be pretty wonderful? Hmmm?
I'm self-employed and the price of IntelliJ is the equivalent of about 30 minutes of my time. I write algorithms for several companies, in multiple languages, and have been quite happy with IntelliJ. Your mileage may vary...
That said, perhaps Eclipse would do everything I need, but there is a cost of changing - I'd be spending some time scanning websites to figure out how to do what I want to do.
A.
The hate for Eclipse is so terribly outdated.
I haven't heard anyone come up with one single proper argument against Eclipse that stands today. Any dev worth his salt has an SSD, plenty of memory and a half-decent CPU. In addition to that, Eclipse has come a long way, which make the "It's slow as hell!"-thing quite outdated.
Even if it would be marginally worse than other IDEs, it has some great advantages:
1. Multi-language, hell, multi-purpose even.
2. Cross-platform
3. Free
4. Open source
5. Designed to be extended with plugins and as such, a veritable buttload of them exist.
6. Generally consistent interface
I've used it (professionally) for editing and debugging PHP, Twig, HTML, XML, YAML, CSS, Android, Java, C, Shell scripts and Javascript code residing in CVS, SVN, Git repos (and even via FTP - shudder) in the past decade and in general being able to use the same hotkeys and UI elements to perform similar tasks. I will readily admit that the different languages have varying levels of support for the more advanced features, but on the whole it easily beats other multi-language tools and saves me from having to use and become proficient in the use of a multitude of language specific editors.
It's probably not the best example, but due to the lack of plugins for Objective C in Eclipse I've been forced to use XCode for iOS development: Talking about donkey shit..
Anyway, I am genuinely interested in which features/properties for any of the above-mentioned languages are lacking in Eclipse and make it worth switching to another IDE for that language.
You know that Lightroom is still available for sale, right?
When Adobe announced the "Creative Cloud" nonsense, I bought a copy of CS6, upgrading from CS3, knowing that if I didn't act, I would never be able to do so again. At that point, I immediately began phasing out my use of Photoshop. Unfortunately, I haven't created any big new projects since then, and I'm stuck using Photoshop for existing projects because Pixelmator doesn't handle manual text kerning changes correctly on import. But the cover art for my fourth novel will be done entirely in Pixelmator.
You see, Photoshop hasn't added anything I really care about since they added layers and layer effects. There are a few minor enhancements that are nice to have, but I was happy on Photoshop 7. I buy upgrades to Photoshop whenever an OS X upgrade breaks it badly enough. It annoyed me badly enough paying for bug fixes when I was doing it on my own terms. When Adobe tried to push me to a monthly fee schedule for Photoshop, I walked away and haven't looked back.
I still buy Lightroom about every second release (about $40 annually), because unlike Photoshop, its upgrades actually provide tangible benefits—new camera support, face recognition, etc. (Yeah, theoretically Photoshop upgrades technically add new camera support, too, but I've imported RAW files into Photoshop a total of three or four times ever; typically, I start out with the processed output from Lightroom.) The problem with Photoshop is that it is a mature product, and there aren't any cool new features left to add that provide enough benefit to pony up an extra $80 a year to get them.
That's a serious problem for companies like Adobe. You see, they're in a position where they command the market. The only place to go from there is down, and the writing is on the wall. Flash is a failure. Photoshop is rapidly seeing the bottom portion of its market worn away by competition. This leaves Adobe's last remaining market—big graphics shops. Those folks will keep buying Photoshop until they no longer find themselves exchanging Photoshop files with other companies. Adobe is thus bleeding those companies for every possible penny they can before Photoshop eventually fades into obsolescence. Or at least that's what it looks like from where I'm standing.
Check out my sci-fi/humor trilogy at PatriotsBooks.
If you luck into a niche it's easy to well for a while. Being a competent programmer doesn't mean the money never stops. And making a useful product doesn't matter if you can't get users to pay for it. I'm not defending rent seeking, I'm just saying I don't think utility software companies can survive without it. You can't just keep cranking out new software. It take a lot of time and resources to get a new product off the ground and it's easy for it to flop.
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
Only until November 1st, after which they will no longer sell perpetual licenses. If you want the latest and greatest, you must subscribe.
BTW, nice job knowing what you're talking about before ripping into TFS.
> 3. It's not user friendly.
> A very well supported statement.
I for one would like all my Desktop apps to have an Eclipse style UI. Its very flexible to layout, as you see fit. I first tried Eclipse in 2002. I picked it up instantly and had no confusion about anything (had used several other Java IDEs before).
> 4. It doesn't run on other operating systems well because it wasn't pure swing.
> 'Other' operating systems?
> AFAIK, it generally runs fine on Linux (barring high-DPI KDE environments) and OSX.
Indeed. I prefer Eclipse on Linux in part because it is NOT "pure swing". Swing fonts on Linux are not nice. I wish that no IDEs are Swing-based.
That you have a pretty low bar for "wonderful"?
That is all.