491–500 of 680 posts
Earlier quoted context omitted.
I'm really curious - why do people want a graphical git client? The command line exposes everything, and the model is simple and intuitive. I work in a very large monorepo, so it's not like I'm working in a git tree that isn't complicated.
I like to drag and drop commits into an order I want when doing an interactive rebase.
Earlier quoted context omitted.
I also tried their CLion and was somewhat disappointed. Slow in places, sometime stalls, bugs here and there. Ended up using CodeLite and Qt designer
If you haven't tried it recently, I'd give it another try. They've had significant speed improvements with 2019.3, whereas 2019.2 was very slow
VSCode with CMake, clangd, and C++ code filter seems to work for the little I've used it so far.
Havn't quite taken the leap of faith in VIM, clangd to see if that is suitable.
I'm a big fan of the way JetBrains sells their licenses. Like a lot of software companies nowadays, they only sell licenses on a subscription basis. But with a very customer-friendly clause of where if you pay for a subscription for 12 months you get a perpetual license for the latest version of the product when you initially subscribed. And then after paying for any particular version of a product for 12 months, you…
It’s also worth noting that the requirement is 12 consecutive months. You can’t have any breaks so you need to be actively subscribed to take advantage of this.
It’s not the best solution (I am a fan of pay for a year (prepaid or monthly) and you get 12 months of updates where you keep all of them), but it’s a good compromise in the era of SaaS. And a compromise I’m willing to make for their IDEs.
Earlier quoted context omitted.
I’ve got them! Did a stint on Sketch as well. It’s now gone subscription, but it think it’s the more acceptable “still works but you stops getting updates” type subscription like jetbrains. What I really want is an Affinity photo library manager like Lightroom. I’ve looked at some currently available options and not been impressed, but there were tweets to the effect that Affinity was thinking about it.
I believe its the current objective to produce a lightroom alternative.
Earlier quoted context omitted.
You're talking about how it's easy to move to a function or a file, and then you're "ready to edit", but edanm is talking about actually doing the editing . For example: say I jump to this function and want to fix a bug (the `search` should strip off the first two characters here, not just one). So I need to change `regex.search(s[1:], ...)` to `regex.search(s[2:], ...)`: def compile_hg_glob(line): pat = glob_to_re(l…
Or just use the mouse to point and click in the same time. With laptop mousepads it's just moving a finger. Most devs aren't writing that much code and all these Vim efficiencies are vastly overstated. I've seen many Vim/Emacs-only devs being easily beaten in speed by others using modern IDEs that have tooling and functionality (auto formatting, refactoring, templating, etc) focused on actually getting things done.
Earlier quoted context omitted.
Or just use the mouse to point and click in the same time. With laptop mousepads it's just moving a finger. Most devs aren't writing that much code and all these Vim efficiencies are vastly overstated. I've seen many Vim/Emacs-only devs being easily beaten in speed by others using modern IDEs that have tooling and functionality (auto formatting, refactoring, templating, etc) focused on actually getting things done.
I think where the IDE’s are really powerful is when refactoring. Need that one class renamed? File is automatically renamed too, and all references in every file that link to it (instantiations, calls, imports) are updated too.
Moving a little bit faster through the text file to edit characters is rarely the issue and I certainly wouldn't give up IDE features for it.
I agree with many of the other posters: JetBrains has succeeded because their products are generally awesome, and I am a happy personal subscriber. People should especially remember what the Java IDE landscape looked like when they first came out with IntelliJ: using IntelliJ after using NetBeans or Eclipse was like using Google for the first time after being familiar with AltaVista - it was just a night and day bett…
Which is a pretty strong vote for building your company somewhere with lower salaries and lower cost of living. There are a LOT of great engineers in places other than SV, Austin, Boston, etc.
Every time I see these guys pop up, I'm reminded of the time a decade ago where they literally copied my .NET profiler (nprof) into their "brand new" .NET profiling product at the time and just shipped it. No apologies, no compensation for building a commercial product on something I had spent a decent amount of time on. Very disappointing of them.
Pretty standard in the .NET ecosystem, unfortunately. I had a similar experience with multiple tools vendors repackaging my stuff for free as the foundation of their product. The only time I ever got a sponsorship offer or even bug fix contributions was a while after I had stopped doing their work for them for free.
I agree with many of the other posters: JetBrains has succeeded because their products are generally awesome, and I am a happy personal subscriber. People should especially remember what the Java IDE landscape looked like when they first came out with IntelliJ: using IntelliJ after using NetBeans or Eclipse was like using Google for the first time after being familiar with AltaVista - it was just a night and day bett…
You're skipping over several commercial Java IDEs available when IntelliJ first came out: Most notably, Borland JBuilder, which was an excellent product. Symantec had Visual Cafe as well, which was not really in the same league as JBuilder, but still had some magic.
IMHO, JetBrains succeeded by having a product as good as JBuilder (and revving it so it got better quickly) and not cratering as a company the way Borland did.
Earlier quoted context omitted.
> the model is simple and intuitive I nearly spat out my drink. Git is many things but those aren't the first two words that would leap into my head.
The model is relatively simple, but the UI is a disaster. Which is exactly why people want better clients than the official git cli client.