91–100 of 169 posts
Earlier quoted context omitted.
Being old enough to have used thin terminals, they aren't insane, plenty of industries don't allow for local development.
Yes, but if they ever removed the ability to run locally altogether then they would be insane. Because there's plenty of people that do development on their local machine.
It’s funny that the person who wrote the copy for the webpage thought that “does X in seconds” was a good way to describe the speed of a modern text editor.
Earlier quoted context omitted.
> I get a horrible feeling in my stomach when I see these "remote" IDE options. Same here. For me, it is the understanding that every bit of this 'convenience' is adding overhead and latency to what should ultimately just be a text editor with some degree of real-time feedback. I can barely tolerate RDP on a local LAN setup for writing code. Across the internet is a joke, especially if some corporate VPN is in the mi…
But here I have to ask what your experience with such remote setups is? I used the remote features of Visual Studio Code a while back because I needed a beefy machine that was integrated into a specific remote service landscape. I have to say I couldn't really notice that it was running remotely. But that probably depends on your company and how weird their network setup is. You mentioned RDP which I wouldn't even st…
Perhaps this is like how some people swear on their life they cant see the difference between a 60hz and 120hz display. I know individuals who absolutely love all the touch screen controls and fly-by-wire features in their cars.
There is definitely some subjectivity to this. Especially, if the notion of building remote workspaces is cool to you. This would make the little annoyances much easier to ignore.
Some of us are sent right off the deep end by the most trivial of matters. I find myself in this camp. If I consciously detect the network round trip, I am going to immediately fall out of flow and start fucking with settings and checking network conditions. This is a huge liability for me when I already struggle to find focus to write code during the day.
Can it finally do something like .vscode/settings.json so that everyone on the team doesn’t have to do manual setup steps or download a settings file from somewhere? Opening a project should bring with it all of the conventions for working on that project, along with plugins also. Bonus points for auto format on save and other style enforcement tools to remove pointless nit picking from the PR process and focus on th…
I get a horrible feeling in my stomach when I see these "remote" IDE options. I am very sure that they have their benefits, coding from a thin-client machine and having an "always on" session in the cloud ... But it feels like a slow errosion of our control and ownership of our tools. Where everything is becoming a rent-seeking opportunity and good tools are made available for a monthly rent. Personally I like having…
No wonder developers complain about sluggishness and running out of memory when they're literally using a headless web browser to write code. Sublime Text works brilliantly. I can have tens of projects, hundreds of files open and the memory usage is peanuts. I don't get the hype about "modern" IDEs let alone remote IDEs.
Earlier quoted context omitted.
IntelliJ IDEA along with the platform is the largest team at JetBrains and we're constantly working on bugs and features. If you can please point me to the issues you're referring to in YouTrack, I can check the status.
I think that it would be good to dedicate a few months with no new feature and just focus on fixing all the regression bugs, there's a lot of bugs that are reported for many months to a year seemingly without activity. I used to like Intellij but got fed up and just stopped using it. Dealing with regression bugs isn't worth it. An IDE should be extremely stable, releasing new features is great but it shouldn't be to…
5. Do you fix bugs before writing new code?
Earlier quoted context omitted.
Whole architecture of Fleet is distributed, so we need a small binary without dependencies that could be uploaded to the dev container. All the access goes through that binary (even in local case)
It's interesting and says something about the state of tooling that, in response to those requirements, it was easier to switch to an entirely different language and ecosystem than it was to build off the existing work and convince the toolchain you were using to produce output with those properties.