Live data from Hacker News

The Era of Visual Studio Code

blog.robenkleene.com

681–690 of 698 posts

Re: The Era of Visual Studio Code

#681

Earlier quoted context omitted.

> The idea that VSCode is the future doesn't seem right to me. VS Code is the future of editors, not IDEs or all developing. There will always this two sides which live from the box and those who build their own box. And for the later VS Code is nowadays one of the best road to walk. > JetBrains products allow you to do so much out of the box, It's also very limited on where you can work with it. It works for the han…

Then you install the plugin for Markdown, rst or PlantUML into IntelliJ? ????

Yes, that's the point. For everything outside the box you need to install a Plugin for IntelliJ too. So there is no difference in that regard.

But there is a difference in culture and availability between a box-driven community and a plugin-driven community. The plugin-culture has more likely a good plugin for something exotic than the box-culture.

For example, searching for mermaid (popular diagram-tool for markdown) in InteliJ-Plugins I only found one commecial plugin that I need to pay for. So it seems here already is a popular corner which is not well covered in this box-culture. And we always can go deeper there, toward more exotic stuff.

For VS Code I immidiatly found a dozen tools BTW.

Re: The Era of Visual Studio Code

#682
post #613

Earlier quoted context omitted.

IdeaVim always seems extremely buggy to me compared to what I'm used to in vscode-vim

odd, never really had a problem with it, of all the vim emulations I've found it to be one of the best. It's not fully featured, but none of them are. I also use vscode-vim.

My biggest complaint is that Shift+V and selecting lines will sometimes jump to completely random spots in my file. It makes it unusuable sometimes.

Re: The Era of Visual Studio Code

#683

Question I have for everyone who doesn't use an IDE What is your workflow? I find the following to be true, in that one of 3 things happens inevitably: 1. The Text Editor becomes the IDE, (e.g., with VSCode, if you just live in plain HTML, CSS/SCSS/LESS and JSX/TSX/JS/TS all day, its actually pretty great, lots of well maintained extensions and Microsoft really put their energy into capturing into this market with VS…

For Python work I use a pretty much out-of-the-box Emacs, with "magit" being the only plugin of note installed. And I also used "web-mode" when I was doing webdev. magit is the best Git interface ever, and a built-in Emacs feature called TRAMP allows for remote editing. I'm running ipython in a separate terminal. I don't really understand why you'd need something more than a text editor to edit Python code.

Now for Common Lisp I use SLIME, which I guess does count as IDE, seeing as it's much more powerful than most IDEs.

Re: The Era of Visual Studio Code

#684
post #62
post #45

Earlier quoted context omitted.

I open a new window for each project, so I don't share this pain.

This. I wasn't even aware I could use a single window, need to look it up.

Tried it, but I didn't like how single window seemed to work with the VCS detection. And I found it generally too messy to keep track of what files belonged to what project.

I just have a few vscode windows open in fullscreen on my laptop. So I just switch to whatever one I need to use at that time. It's never really more than 3 at a time.

Re: The Era of Visual Studio Code

#685
post #238
post #198

I find this post along with the comments in "A Picture of Java in 2020" https://news.ycombinator.com/item?id=24551390 to be incongruous with my experience as a professional developer. My first couple of years writing software I used Vim, then VSCode, then worked in a Java shop and was forced to use IntelliJ. I didn't like it at first, but now after a couple of years I cannot see how I lived without it. The idea that…

Fancy IDEs are lubricants for high-friction languages. If a language is already low-friction, there won't be much benefit to be gained from an IDE, as even a plain text editor will already get you near to optimal productivity in said language. Personally, I'd rather use a plain-old "code editor" (with at most syntax highlighting, but no snippets, let alone autocomplete), in part because doing so will actively steer m…

I'm not sure what you mean by "Fancy IDEs", but if it's ones that integrate with the language (eg intellij) then I really disagree that there won't be much benefit. The main benefit I find with a good IDE is that it makes your typing follow the constraints of the scope you are in.

A string literal can be any sequence of characters so it's up to you to type them, but when I'm accessing members of a class, I'm not interested in being able to try to access a random string that is not a member of that class.

Re: your thinking comment, I also think it's the opposite. When the IDE follows the constraints of the language, it's more intuitive than when it suggests typing random strings everywhere is fine. That's not how a language works, and neither do I find it constructive to think that way.

Re: The Era of Visual Studio Code

#686

Earlier quoted context omitted.

Not at all. You can open a directory, or a workspace. A workspace is just a collection of directories. If you want a confusing workspace/project system try Eclipse!

Actually, the designer of Eclipse’s and VS Code’s extension system is the same person: Eric Gamma from Gang of four.

We weren't discussing the extension system. Workspaces are a core feature of both IDEs. Still, that's an interesting fact!

Re: The Era of Visual Studio Code

#687

Earlier quoted context omitted.

This is completely not restricted to IntelliJ/PyCharm. The MBP i7 is terrible for this, and I get thermal throttling all the time when I use 4k external screens and anything remotely that seems like work.

OK, but (for example) my experience is that I only experience this as a problem with PyCharm — it literally becomes unusable; VSCode (say) is fine.

Depends on the plugin that gets activated. Jest can bring it to its knees.

Re: The Era of Visual Studio Code

#688

Earlier quoted context omitted.

I think the fairer comparison is with Visual Studio 2019, not Visual Studio Code. Visual Studio Code is free, making it highly attractive for a larger audience. The pricing for IntelliJ is not accessible: https://www.jetbrains.com/idea/buy/#personal?billing=yearly I've also used IDEs that are highly optimized for Java and .NET. I agree it's great for the use case I had.

What do you mean not accessible? $150/yr isn't insane for a piece of software you might spend 6 hours a day in.

If you are building software in a paid capacity then yes it's a small price to pay. But if you aren't getting paid or getting paid somewhat decently (e.g. study, hobby, open-source) then it's a lot.

It's great they have various editions, to address the above, so if those editions are good, then it makes my point moot.

edited: Recognizing different free subscriptions exists

Re: The Era of Visual Studio Code

#689
post #682

Earlier quoted context omitted.

odd, never really had a problem with it, of all the vim emulations I've found it to be one of the best. It's not fully featured, but none of them are. I also use vscode-vim.

My biggest complaint is that Shift+V and selecting lines will sometimes jump to completely random spots in my file. It makes it unusuable sometimes.

in what Jetbrains product? I use Visual Lines all the time in webstorm, rider, and clion for multiple purposes

possibly some other keybinding is getting accidently triggered somehow..

Post reply on HN