Live data from Hacker News

PyCharm 2023.1

jetbrains.com

11–20 of 60 posts

Re: PyCharm 2023.1

#11

Interesting. I heard many good things about Pycharm, but it kind of looks bloated? How does it compare to VS Code (which is quite good (notebook and repl support mostly), but not great, in particular regarding the debugging experience)?

For large codebases PyCharm is superior, as VS Code usually chokes in its JavaScript memory usage before PyCharm's Java. You need to load large symbol datasets in the memory and VS Code seem to be struggling with this.

PyCharm autocompletion, autoimport, red underline errors and type hinting tools are also better than in VS Code.

VS Code Jupyter Notebook integration as better. PyCharm tends to do very badly with complex notebooks.

Using both 5+ years.

Re: PyCharm 2023.1

#12

Interesting. I heard many good things about Pycharm, but it kind of looks bloated? How does it compare to VS Code (which is quite good (notebook and repl support mostly), but not great, in particular regarding the debugging experience)?

PyCharm has a great debugger. I am a longtime Pycharm user and have used VScode from time to time for python, and it seems like only now VSCode is catching up. Pycharm is still better though in the general language support department. However I feel that if you were already a VSCode user, VSCode has become good enough. Pycharm like other IntelliJ based IDEs has many other QoL features which I can't find anywhere else…

For me, it comes down to the cohesiveness of the whole thing. VSCode plugins often feel janky.

Re: PyCharm 2023.1

#13

Interesting. I heard many good things about Pycharm, but it kind of looks bloated? How does it compare to VS Code (which is quite good (notebook and repl support mostly), but not great, in particular regarding the debugging experience)?

People always use bloated as an argument against something. Bloated framework, bloated linux distro, bloated ide…

What really is the problem with having all “the plugins installed”/features, nicely integrated, always compatible, reasonably configurable, maintained and with support vs inflating a minimal editor (framework, *) yourself, without all the advantages mentioned earlier.

Yes it may cost some cheap memory, vs costs of fixing plugins yourself.

My advice: Embrace it. Everything just works. Bloated in many cases is a non argument.

Disclaimer: long time bloated fan. Pycharm, django, monoliths. I rather spend time fixing things that matter.

Re: PyCharm 2023.1

#14

Interesting. I heard many good things about Pycharm, but it kind of looks bloated? How does it compare to VS Code (which is quite good (notebook and repl support mostly), but not great, in particular regarding the debugging experience)?

Jetbrains IDEs are an industry standard, and has a quantified ROI on time saved.

First thing to think about: Pycharm is an IDE, VSCode is an editor. You're going to bloat VSCode to get anywhere near the functionality of Pycharm.

I believe jetbrains products have made me a better developer as it should provide more context and intellisense to give you guidance away from code smells and bad practices, without becoming a crutch (moreso for statically typed languages).

Also, very fond of the keybindings on macos as they mirror chrome, os, and electron applications.

Re: PyCharm 2023.1

#15
Still a knights battle helmet when it comes to looking on text.

Transparent Modal background to the text is were its at in my opinion. That and buttons on the side. One key to switch into the background. One key to switch the modes.

Re: PyCharm 2023.1

#16

Interesting. I heard many good things about Pycharm, but it kind of looks bloated? How does it compare to VS Code (which is quite good (notebook and repl support mostly), but not great, in particular regarding the debugging experience)?

The IntelliJ git interface makes a lot of sense, and makes many helpful operations easy, like “compare what I have now to this particular commit”. The VSCode git interface, even with plugins like GitLens, seems to make these operations hard to get to, and how VSCode manages diffs with the staging area involved is totally bananas.

Aside from that, PyCharm has a slightly better debugging interface but otherwise it’s quite close to VSCode for Python development. Sane version control is a bit aside though.

Re: PyCharm 2023.1

#17

Interesting. I heard many good things about Pycharm, but it kind of looks bloated? How does it compare to VS Code (which is quite good (notebook and repl support mostly), but not great, in particular regarding the debugging experience)?

It's the best IDE you can ever use, not affiliated.

The number of little 'intends' that make your life easier is just next level.

If you are using other IDEs of the intelliJ set you can use all the familiar refactory workflows etc.

Re: PyCharm 2023.1

#19

Interesting. I heard many good things about Pycharm, but it kind of looks bloated? How does it compare to VS Code (which is quite good (notebook and repl support mostly), but not great, in particular regarding the debugging experience)?

VS code support for multiple Python environments and dependency handling (be that requirements.txt or pyenv or…) is really quite terrible compared to Pycharm.

Re: PyCharm 2023.1

#20

Interesting. I heard many good things about Pycharm, but it kind of looks bloated? How does it compare to VS Code (which is quite good (notebook and repl support mostly), but not great, in particular regarding the debugging experience)?

I use PyCharm for my job as well as for personal projects, and it handles large codebases with type annotations very well. I would compare it to Visual Studio (not Code) in the sense that it’s a batteries included deal, which means larger initial size but I use maybe two plugins.
Post reply on HN