Earlier quoted context omitted.
It’s not change for change‘s sake though. People are migrating towards mobile displays and actually doing work on those - as small as 11“. IntelliJ doesn’t work well on those displays. I‘m not saying we shouldn’t have both options (eg minimal mode and pro mode or whatever).
I used Eclipse on an asus eee901. It was fine.
Dear JetBrains, Don't mess with your UI
261–270 of 420 posts
Re: Dear JetBrains, Don't mess with your UI
#262It's a little surprising that these UI choices are not a matter of user choice. Although when you think of the complexity of making a truly skinnable UI, or a component framework (I'm thinking Swing and the pluggable look and feel, or PLAF) Swing that IntelliJ used to be nominally written in. In that universe you could have made your own PLAF and rendered IntelliJ in that PLAF without asking permission. It turns out,…
> It turns out, though, there is a lot of value in homogenizing your application skin. This is pretty well documented in the UX world, it’s called Jacob’s Law[1] and it states that your users spend most of their time using other products, and they generally prefer yours to work like others they’ve already trained themselves to use. I get that change always comes with resistance, but I will never understand the knee j…
What's there to understand? In most cases they are morons that don't know what they're doing (and are not doing the change to improve users' lives, but to drive internal promotions for product people).
Re: Dear JetBrains, Don't mess with your UI
#263Earlier quoted context omitted.
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.
I use Rust in IntelliJ, and the indexing is usually fine once the IDE is up . But for some reason, whenever I reopen a project, it needs to reindex it. Even when I open the same project every day, not having changed anything in between. I understand from a friend it doesn't do that with Java projects.
Re: Dear JetBrains, Don't mess with your UI
#264Earlier quoted context omitted.
Because my ec2 dev server is even more powerful, and I can easily upgrade the hardware configuration without spending $1k on a new laptop. I never really appreciated a remote dev server until I had to work on a behemoth Java project and then a behemoth C++ project. Having the extra memory and the extra cores is great. Never having to worry about your laptop heating up or having your battery die due to CPU load is eve…
I guess if your IDE is as responsive as anything else locally and only the compiling and runtime happens in the cloud it might be somewhat pleasant to work with. But what if you decide to do something from a coffee shop and the WiFi is super laggy. Or doing something while traveling etc. I like to know that my dev station is independent of an Internet connection.
Re: Dear JetBrains, Don't mess with your UI
#265Earlier quoted context omitted.
From their FAQ: Will Fleet replace any existing JetBrains IDEs? No, it will not. We are fully committed to continuing active development of our IntelliJ-based IDEs. With Fleet, we’re aiming to offer an alternative view on how an IDE can be organized, and this is impossible to implement within our current product line without going against the expectations of developers currently using those other IDEs. This means Fle…
> This means Fleet will co-exist with our established products This means it will take resources away from the development of the established products. You cannot have the cake and eat it.
Re: Dear JetBrains, Don't mess with your UI
#266Earlier quoted context omitted.
> This means Fleet will co-exist with our established products This means it will take resources away from the development of the established products. You cannot have the cake and eat it.
Fleet has been in development for multiple years. It has already "taken away" dev resource. It is not my our job to micro manage their dev resources.
Re: Dear JetBrains, Don't mess with your UI
#267I find the entire "java world" as I like to think of it, littered with slow IDEs. The "Electron bloat world" editors have been much more snappy in my experience. Typically the "java world" editors will lag out to the point where tapping on the "File" menu will take 3-5 seconds on occasion. Also they seem to rely on "indexing" and while the "indexing" operating is taking place, the entire editor just slows to a comple…
> tapping on the "File" menu will take 3-5 seconds on occasion. Are you still using a hard disk drive? I think I was last time I saw a delay that took that long on IntelliJ IDEA.
Re: Dear JetBrains, Don't mess with your UI
#268Earlier quoted context omitted.
> 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.
IIRC on desktop you can still use the old-ish (at least, plain HTML) version of gmail if you disable Javascript once logged in. At least it worked quite recently for me.
Re: Dear JetBrains, Don't mess with your UI
#269Earlier quoted context omitted.
> Forget what VSCode is doing. Except for remote development extension. Do that. It's the killer feature of VSCode.
Why would one do remote development with laptops being as powerful as they are today (think: the raw power of an M1 Mac Book Air even).
Re: Dear JetBrains, Don't mess with your UI
#270Eh, 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 Sadly it’s not actually just a UI refresh but a UI downgrade because they’ve actually removed key functionality, not just tweaked some visual styling. It’s a completely different tool window layout mechanism with far fewer tool windows that can be open at the same time. I rely on having my source control, embedded terminal, problems window, commit window + more all simultaneously visible.…