Wanted iPad support - Got VS Code UI
I have been impatiently waiting years for iPad support. You had a nearly workable tool a few years ago. I can't remember its name: Platform? The old product worked great, for a beta. It continuously crashed and tended to go bonkers when you had more than one monitor connected to your MacBook. But it was a solid first effort and I was eager to see it mature.
Now we are stuck with Gateway. Which is the exact opposite of what the community has begged for. It seems likely Gateway does fulfill a valid security use case, especially for companies that like to hire programming staffs from 3rd world countries. But it doesn't get us one inch closer to being able to develop on iPad like the old product did.
Regardless now we have the death threat of the new UI. The UI everyone hates and no one wanted. I can't help but wonder how much more interesting and rewarding it would have been for your team to get remote development working rather than putting so many hours into a UI that is universally despised by the paying customers. This is clearly the project that should have been discontinued, not remote development.
I can tell everyone hates it not only from reading the endless complaints online but by your now desperate “WE ARE RIGHT, YOU ARE ALL WRONG” statement that you are going to turn off the good UI in favor of this hot mess. That is a classic retrenchment of bad executives when the reality that tens of millions of dollars have been squandered on a product dead end. I will never forget my very first real job out of college when the owner of the small business I was working for indignantly announced “I will bankrupt this company before I admit I was wrong”. Fun fact he did too. About a year later the FBI put padlocks on the building. We never did get our personal belongings back. Honestly the new UI feels like the hill on which said executive has chosen to die. I just don't get it.
I have turned off all updating of your product. I got blindsided by the IntelliJ update, but I was able to restore normal function with the plugin and prevented the other products from updating. Since I'll have a perpetual license for the current release this will be where we part ways. I will continue to use your products while I search for replacements. But unless you issue an apology and guarantee never ending support for the core UI, our 15 year relationship is at an end.
I deeply resent the effort I must now direct away from productive programming and into finding and learning a new tool. But it is your business. You are free to immolate it if that is your choice. But I won't pay to watch.
Please sign in to leave a comment.
The reasons for turning on New UI are explained in https://blog.jetbrains.com/blog/2024/07/08/the-new-ui-becomes-the-default-in-2024-2/
Supporting iPad is a job of JBR team, that is currently focused on Wayland support (https://blog.jetbrains.com/platform/2024/07/wayland-support-preview-in-2024-2/). NewUI is primarily a job of UI and UX teams. They are as different as the front end and the back end.
I'd say iPad support is more for our remote development team, but it's also a separate team and the work on the new UI did not affect the progress with the tasks like https://youtrack.jetbrains.com/issue/GTW-3415/iOS-Android-Remote-Development-feature .
Running natively on iOS is unlikely to happen any time soon due to Apple restrictions (such as no JIT allowed and many others).