Earlier quoted context omitted.
About a year ago I decided it was time to finally modernize my Python coding setup. I really, really wanted to use Nova, would have paid full price no problem, but for some reason the one main Python plugin was extremely flaky for me. Linter highlighting would sometimes work and sometimes not, unaffected by the plugin settings, and the primary Python plugin I was using was based on somebody’s github repro that hadn’t…
What plugin(s) exactly are you using in VSCode for Python support?
Nova by Panic
261–267 of 267 posts
Re: Nova by Panic
#262Earlier quoted context omitted.
About a year ago I decided it was time to finally modernize my Python coding setup. I really, really wanted to use Nova, would have paid full price no problem, but for some reason the one main Python plugin was extremely flaky for me. Linter highlighting would sometimes work and sometimes not, unaffected by the plugin settings, and the primary Python plugin I was using was based on somebody’s github repro that hadn’t…
Is there a reason you didn't go with PyCharm? I tried vscode, and it works out of the box for particular things, but Pycharm is just a breeze on latger projects.
But I actually recently wrote a todo to try out PyCharm Pro. I haven't decided if that's pointless yak shaving since VSC works pretty well for me. But I would like to configure VSC more to make my workflow faster. And my guess is PyCharm Pro is probably better out of the box vs having to spend time configuring VSC settings (so many settings...) and plugins.
Re: Nova by Panic
#263Earlier quoted context omitted.
I'm sure it does fine at that, but there are perils with SSHFS-type access (like file corruption risks when you switch between editing machines.) And this really doesn't get close to what Visual Studio Code's Remote editing functionality can do. The Remote mode operates a full remote VSC environment over SSH or as a docker container, and that means things like being able to do find and replace at the remote end in th…
> I'm sure it does fine at that, but there are perils with SSHFS-type access (like file corruption risks when you switch between editing machines.) What does VSC do to mitigate that? > And this really doesn't get close to what Visual Studio Code's Remote editing functionality can do. The Remote mode operates a full remote VSC environment over SSH or as a docker container, and that means things like being able to do f…
Basically it's not running a block filesystem over SSH at all. You are editing your files remotely. So there is no risk of block corruption (which has bitten me on the arse before).
In fact, if you log in twice to the same remote host as the same user using VSC, your editors will magically update each other, live. This is the underpinning of a pair-programming aspect of remote VSC that MS intend to productise.
And if you log into that machine and edit a file that is open in VSC Remote using something like vi, VSC will know about the changes. Plus you can edit very large files remotely.
Yes, you obviously could/can do all of your git stuff in a terminal window -- that is how I used to work even with VSC before the Remote facility was added. After 30 years of using unix I'm fine with that if I have to do it.
But you lose all the editor integrations, because git cannot work effectively over networked filesystems. Whereas with VSC Remote, all of that stuff works exactly as if it was local. Including almost all extensions, which install into the remote. The normal file search does not work well over a slow SSH filesystem link, because to search all those files they have to be downloaded, whereas file search in Remote mode is done by the remote.
What I like about this is being able to work with pretty much any machine that can support VSCode, without having to worry about installing dev tools on that machine. I then also use Vagrant so I can separate concerns among my clients (I'm kind of working in a pre-Docker world in the wider sense in the job I do, still, so Vagrant boxes and my own configuration system are a good substitute). Or I could edit inside WSL2, while VSC itself runs on the Windows machine.
I think Nova looks very nice indeed, and as a Mac user and erstwhile Transmit mega-fan I wish them well, but I was never impressed with Coda, which was interactively slow in the editor -- in some situations painfully so. (The iPad version was an occasional lifesaver but I use GoCoEdit there now.)
But it's pretty inescapable that VSC Remote is its killer feature. It's just that unless you've used it, it's hard to explain. Now that I know how much it has helped me, I can't envisage going back if I have the choice not to.
Re: Nova by Panic
#264I don't understand why every editor these days come with a minimap, and many of them turn it on by default. I know Sublime introduced it but what does it do exactly? Why is everyone copying it? It just shows you the shapes of blocks of texts of a long file from ten meters away. It doesn't tell you what they are or what they do, or even how to get there. Every IDE since at least the early 2000s gave you an index or a…
Not only the position in a source file is relevant for many languages, but if you're jumping to references/definitions blindly from another source, you can tell which source file it is and where you are in a single shot without looking at the rest.
That being said, I don't use the minimap. I did try to use it though to see what's the fuss around it. For me it takes too much horizontal space. I can have another vertical split pane instead of having minimaps showing. Heck, I'm not even using scrollbars.
Having an indicator of which function your cursor is currently inside provides very similar benefits to me. Not as immediate as a minimap I have to say, but more useful if you take the time to read it. This is a tradeoff people will argue on forever.
Re: Nova by Panic
#265I will reiterate my chief complaint with this: it should have just copied the VSCode extensions API from day one and relied on easier porting of them.
The problem with doing that is that you've now created a substantial dependency for your commercial product, and not a dependency that's merely the "requires npm package foo" kind of dependency. Because Nova is not VSCode, being compatible with Code's extensions API means: - committing to implementing every new documented Code API function as quickly, completely, and transparently as possible, because if you don't, e…
Got a link for that? I was looking for a TextMate grammar to Monarch converter and couldn’t find anything that works
Re: Nova by Panic
#266I tried Nova when it first launched and again recently, and I switched back to VSCode due to the numerous plugins and prodigious output of its creators every month. In my opinion, Nova (through its lack) shows the true power of network effects, even in code editors, because even though VSCode is an inferior product in many respects, like speed and resource usage, it still wins due to its sheer popularity and extensib…
Before VSCode, same effects were conspicuously at work in Emacs and Vim. While JS has some warts here and there, vimscript is truly terrible. Nevertheless, a lot of advanced Vim plugins were built, drawing even more people to Vim, thus incentivizing more plugins, etc.
I don’t know about emacs, as I’ve never used it from either side
Re: Nova by Panic
#267I managed to make Nova work for some trivial frontend stuff, but not having a built-in robust git client really threw my workflow off. I don't really like using a separate terminal for diffing, nor do I like the default diff viewer for git anyway, nor do I want to buy Kaleidoscope for a billion dollars for that one thing, which would be an external viewer anyway. Yes I want a native mac app, but it doesn't really cou…
Maybe something like https://git-fork.com would work for you? It has a decent enough diff viewer (Even though I prefer Kaleidoscope for bigger rebases), is native and an actively developed indie app. I'm a happy user and can recommend it.