Live data from Hacker News

Dear JetBrains, Don't mess with your UI

neil.computer

351–360 of 420 posts

Re: Dear JetBrains, Don't mess with your UI

#351
post #33
post #14

Earlier quoted context omitted.

to be honest, not sure why they have to explain themselves. started using JetBrains products when Eclipse became a monstrosity. this is not the first time the UI has changed. and it has always been gradual, with options to customize. they don't have to explain themselves here.

True, but people will also not have to explain themselves when they eventually switch to VS Code because VS Code is free, has the same UI, and get more feature rich by the week.

> people will also not have to explain themselves when they eventually switch to VS Code

People need not justify the tools they choose to anyone, so correct, should that happen, people will not have to explain themselves.

Re: Dear JetBrains, Don't mess with your UI

#353
post #274

Earlier quoted context omitted.

Personally I'm not "rewarding the post with hundred of points", but I've upvoted because I share the sentiment and want JetBrains to really consider each change they make: Is it for change's sake, or because it's actually better ?

What makes you think that they haven't already considered it? It's rather offensive to assume that a group of UX professionals decided to take on a massive overhaul just for fun. Given UX has never been a major priority at JetBrains, it implies that they decided it was valuable enough to spend the time and money on this. I just can't imagine this was done on a whim

How do you explain the current UI shit hole that we live in these days then? It surely wasn't to increase productivity or user experience. UIs in the 90's were more functional and flexible than the UIs of today.

Re: Dear JetBrains, Don't mess with your UI

#354
post #274

Earlier quoted context omitted.

Personally I'm not "rewarding the post with hundred of points", but I've upvoted because I share the sentiment and want JetBrains to really consider each change they make: Is it for change's sake, or because it's actually better ?

What makes you think that they haven't already considered it? It's rather offensive to assume that a group of UX professionals decided to take on a massive overhaul just for fun. Given UX has never been a major priority at JetBrains, it implies that they decided it was valuable enough to spend the time and money on this. I just can't imagine this was done on a whim

> UX professionals decided to take on a massive overhaul just for fun.

I’d say they were doing it because they were getting paid for doing it. But that doesn’t mean it actually needed doing. What I have found in tech especially is that a product may get to a point where it’s meeting all its functional goals and really only needs small tweaks and fixes. But this is at odds with company growth. I’m not saying this is the case here but it’s prevalent in this industry.

Re: Dear JetBrains, Don't mess with your UI

#355
post #274

Earlier quoted context omitted.

Personally I'm not "rewarding the post with hundred of points", but I've upvoted because I share the sentiment and want JetBrains to really consider each change they make: Is it for change's sake, or because it's actually better ?

What makes you think that they haven't already considered it? It's rather offensive to assume that a group of UX professionals decided to take on a massive overhaul just for fun. Given UX has never been a major priority at JetBrains, it implies that they decided it was valuable enough to spend the time and money on this. I just can't imagine this was done on a whim

It didn't have to be UX team. It could have been some marketing genius that came to UX team and told them that his nephew is using new funky, black background IDE called VS Code, which is all the hottest nowadays, so IntelliJ HAS TO catch up, should become modern, trendy and fun again, so it will bring more sales.

I only hope nephew didn't mention Electron backend.

Re: Dear JetBrains, Don't mess with your UI

#356
post #344
post #141

Earlier quoted context omitted.

> On the flip side, the only thing I want Jetbrains to do is implement proper UI scaling. Oh man I'm still mad that if I want to present my Jetbrains IDE screen and make it readable, I have to change 2 fonts, one for the editor, one for the interface.

Shift shift -> Enter Presentation Mode. (Replace shift shift with whatever you have the “everything” search bound to).

Presentation mode is terrible for doing code pairing, code presentations, or really anything that involves screen sharing.

Re: Dear JetBrains, Don't mess with your UI

#357
post #346

Earlier quoted context omitted.

It's nice that it's being an accepted point of view this time. Usually I get a lot of aggressive responses about how I don't understand presentation mode. I do, and it's crap.

By contrast, I only want the content to scale, and actively cannot stand entire UIs scaling and looking and feeling like web pages. If this was ever implemented, it would need an opt-out to please us both.

Which is fine. As I already mentioned, even if they just had a text scaling which applied to all the editors so I didn't have to keep doing it every time I opened a file that would be a massive QOL improvement.

Re: Dear JetBrains, Don't mess with your UI

#358
post #344

Earlier quoted context omitted.

Shift shift -> Enter Presentation Mode. (Replace shift shift with whatever you have the “everything” search bound to).

Presentation mode is terrible for doing code pairing, code presentations, or really anything that involves screen sharing.

Curious why is that, what are the pain points specifically? I use it often when presenting and the only downside is that presentation mode forces full screen (on mac)

Re: Dear JetBrains, Don't mess with your UI

#359
post #288

Earlier quoted context omitted.

On the contrary, I find a common debugger (see questions below) an underwhelming experience, not a powerful tool. Can it: - assign (scenario, subsystem, level, description) to breakpoints and watches, so they can be turned on/off or selected in groups for debugging without removal? - commit these scenarios of bps and watches into a repository? - edit/read them in a textual form to patch or share over an IM? - store t…

> - assign (scenario, subsystem, level, description) to breakpoints and watches, so they can be turned on/off or selected in groups for debugging without removal? In Jetbrain's tools they definitely can. I can * create a bunch of breakpoints * give them descriptions * only have them break on execution under certain conditions (conditions stated via the programming language being debugged, so `my_struct.some_func() ==…

Well, this is good to learn. I skimmed through intellij debugger docs before writing that comment and didn’t find anything like that. Thanks!

Re: Dear JetBrains, Don't mess with your UI

#360
This absolutely cracks me up. Developers reacting like every user who has the perfectly functional UI/UX pulled out from under them. Shoe on the other foot as it were. Perhaps there's a lesson here for developers of software, their management, and/or companies who take part in this UI/UX churn for churns sake.

The problem here is that statistics, and feedback, doesn't inform about the negative. All the users out there who are happily using your software in its current state and are perfectly happy with it but can't be assed to take the time to fill out your survey. As the saying goes "you can't improve what you don't measure." This should have continued something like "so be sure to consider what you can't measure". You can't force everyone to take your survey.

Sure in part that puts the blame on the users who don't bother to fill out the survey. But that shouldn't also give the right to ignore them and what they might want. Perhaps a non-vote should be counted as a vote for no change instead of simply being ignored. It's pretty well known that the squeaky wheel gets the grease but that shouldn't mean the entire UI should be slathered in the grease the squeaky wheel wants but no one else asked for.

Post reply on HN