This happens when a company hires new product managers who don't give a hoot about what made the product originally great to begin with. I call it "Skypeification"
Dear JetBrains, Don't mess with your UI
81–90 of 420 posts
Re: Dear JetBrains, Don't mess with your UI
#82Earlier quoted context omitted.
Switch branches? Let's index it all again! Working on a Rust project? Let's index the Go stdlib. It'll be ready in 10-20 min, please hold. I've been waiting for indexing improvemence for over 10 years, not holding my breath.
I use Clion for C/C++ and Rust (with the rust plugin) and indexing seems fine. PHP, Python, Ruby and Go have been generally miserable for me.
Same. Typescript, Python and Ruby are so painful for indexing especially if you use a workspace based build tool at a big tech company.
Re: Dear JetBrains, Don't mess with your UI
#83Eh, I have used vim, spacemacs, sublime, vscode, atom, eclipse and netbeans. Jetbrains IDEs have superior functionality out of the box across languages and don’t require me to mess with and debug a million plugins. I don’t mind a UI refresh, it’s going to be just like the gmail refresh everyone hated it and now we’re all fine with it. I just wish they would invest more money into things that are actually a problem cu…
Switch branches? Let's index it all again! Working on a Rust project? Let's index the Go stdlib. It'll be ready in 10-20 min, please hold. I've been waiting for indexing improvemence for over 10 years, not holding my breath.
You want to run a task from your build tool that has nothing to do with indexing before indexing finishes? No can do!
You installed an npm package and it seems to depend on all the things? Let's start indexing on node_modules and give you no chance to even uninstall the **er. You used the CLI to work around our tooling? Hey let's start indexing immediately after this one finishes so it's a great idea for a coffee break, just never pull directly after coming back so you may actually do some work until we bog down all the cpu cores.
Don't get me wrong, I love all the JB IDEs, but indexing has been a deal-breaker for many.
Re: Dear JetBrains, Don't mess with your UI
#84I love Jebrains IDEs. They can save you lot of time. For example, VSCode does not even come close to Jetbrains git branch comparison. It's insanely good. I think a proper IDE is always better than adding 10s of extension to get similar functionality from VScode. Even then it does not compare to the beast that is Jetbrains IDE. Jetbrains should keep working on their own thing instead of trying to change because of som…
Me too, I don't think I can function without JetBrain products as an engineer. It is ridiculously powerful. PyCharm + Database tab + Debugger + Little calculator icon for impromptu interpreter + long tail of features that totally make it amazing. I don't use built in Git but I heard that's great too. The database feature has stuff like copy results of a query as INSERT statements. Mind blown.
The built-in git is honestly quite intuitive while still being pretty powerful. I haven't tried other GUI-like git integrations but I was a fan of IntelliJ's.
That said I was talking to a friend about how great it was and he was like "yeah all these things you describe seem like they were lifted from magit" so I suppose once again the answer is "magit is still the best".
Maybe if I ever have the motivation to actually set up an editor I'll try Spacemacs again but I get frustrated when things don't just work and end up going down the configuration rabbit hole anyway.
Re: Dear JetBrains, Don't mess with your UI
#85> Removal of color from icons.
Software is getting very depressing as designers decide that everything needs to be shades of grey. It's really sad.
Re: Dear JetBrains, Don't mess with your UI
#86The old UI should still be available in the settings. atleast, that's what they promised after the first UI beta
Also Fleet isn't replacing the other IDEs
Re: Dear JetBrains, Don't mess with your UI
#87Earlier quoted context omitted.
While I agree with this point, I also like my interfaces small. Because, since I don't click around on them, I don't like them taking up space. I also use a mouse on my PC, so I'm fairly precise in case I want to use the icons. There's no need to blow them up, so my fat fingers wouldn't misclick on a tablet. I like to code with two windows side by side, usually IDE + browser for docs, sometimes on a small screen. I'd…
I like them small too which is why I hide basically everything except for the editor itself :)
I just wish the panels would default hide. I run bazel sync and half my window is build logs until I get around to closing them. If it’s not in active use, maybe after 5s, get it out of the way of code.
Re: Dear JetBrains, Don't mess with your UI
#88This is like HN candy. Complain about “modern UI trends” even if it isn’t true. Even if you explicitly admit it isn’t true because you speculate it might someday be true. Bash the nearest Electron app that isn’t even involved in the thing being hypothesized about. Modern UI Trends front page post here we go!
Re: Dear JetBrains, Don't mess with your UI
#89Eh, I have used vim, spacemacs, sublime, vscode, atom, eclipse and netbeans. Jetbrains IDEs have superior functionality out of the box across languages and don’t require me to mess with and debug a million plugins. I don’t mind a UI refresh, it’s going to be just like the gmail refresh everyone hated it and now we’re all fine with it. I just wish they would invest more money into things that are actually a problem cu…
> I don’t mind a UI refresh, it’s going to be just like the gmail refresh everyone hated it and now we’re all fine with it.
We are not fine with it. It really sucks. It's just out of our hands.
To this day I hate the gmail interface. It used to be so much better back in the day.
Re: Dear JetBrains, Don't mess with your UI
#90So company internal proof of work produces UI Components, that over time make a "breaking" change necessary destroying user work worth in the billions and a pr-word of mouth disaster.
Worser still, all those features accumulating over time (nobody deletes codes) destroy the product.
So as a product manager you can
a)
Anticipate it, create UIs that allow for large scale changes without breaking the old user flow and automatically prioritize hotkey-commands by user usage if there is a conflict. You also need to stop the Designers from going amok, rendering the whole tutorial section of your product on youtube obsolete. It will always be a paint point, but as you anticipated the bloat on success you integrated it into the architecture.
b) Phoenix Lifecycle it. When it all becomes to much, a smaller, more lightweight version of your product emerges out of the ashes, capable of integrating the newest, shiniest changes, without having the weight of all the bloat, it is first ignored, laughed at, finally emulated and it becomes your new product. There it slowly aggregates the same bloat, waiting for a challenger to appear. Its inevitable.
Is your IDE still a program, or is it in fact a OS for interacting addons and a really hungry text editor?