Live data from Hacker News

Nova by Panic

nova.app

501–510 of 549 posts

Re: Nova by Panic

#501
post #223

Earlier quoted context omitted.

any pointers? i'd love to upgrade my beloved VIM from ctags-era navigation, but don't have time to shave the whole yak. Would love to hear your tips.

Multiple plugins are available to add LSP support in vim, such as coc.nvim (uses node.js, more features) or vim-lsp (lighter, written in vimscript). Neovim is also going to add native LSP support as well as tree-sitter in their 5.0 release, it's already available in nightly builds. The most straightforward option is probably coc.nvim, which tries to give a similar experience to VS Code out of the box. https://github.…

I'm mostly well served by a slew of ruby/rails plug-ins along with tags - but this so answer might be a good, somewhat modern starting point. I'm going to check out if vimspector can help me with my debug flow:

https://stackoverflow.com/a/51195409

Re: Nova by Panic

#502
post #480
post #137

Earlier quoted context omitted.

There are known issues with scaled resolutions on macOS and JetBrains IDEs. If that is the case for you, using a tool like resolutionator to scale instead of the native macOS scaler, should solve the performance issues.

I wonder what makes the scaling in macOS difficult. For years Firefox would eat through my battery in no time if scaling was enabled.

It’s due to the Retina displays. The scaled resolutions don’t map in a clean way to pixels. The renderer renders everything at the native resolution of the panel and then has to downscale it to the scaled resolutions. For the “native” Retina view, it’s just /2, so it’s easy and pixel perfect. The others are more like /1.523134... and there’s more work to figure out what color each pixel should be.

Re: Nova by Panic

#503
post #36

Earlier quoted context omitted.

It's the same for VSCode and JS/TS support though. Fighting against a fully featured, free, open-source and well-established product just on the basis of speed is going to be an uphill battle.

There is a big "ugh, Electron apps" contingent of Mac users. Or at least, there's a loud one, and I guess they figured it's also a big-enough one...

Where? Here in HN, a little bit, but out IRL?

Out in real life no one knows or cares about this

Re: Nova by Panic

#504
post #456

Earlier quoted context omitted.

>I can't imagine the world of hurt, discomfort and frustration of developing against a lib set I can't read source code of or improve. Thank you . It boggles the mind that anyone who can write code would ever use a closed source operating system.

Some of us prefer the Xerox PARC experience, and gave up on the promise of Linux Desktop with its fragmentation and continuous churn. My MFC/VCL applications work just fine today, and can be easily extended to take advantage of modern UWP APIs.

In what way(s) does Linux fail to follow in the footsteps of PARC?

Re: Nova by Panic

#505
post #495

Earlier quoted context omitted.

When you use Nova and then go back to something web based, like Atom, it becomes clear why that’s not ideal. It jut feels snappier.

And then when you go back to something terminal based, like Vim, it becomes clear...

To be fair if you get a few plugins for web dev running vim/nvim does slow down a quite a bit.

Re: Nova by Panic

#506
The first sentence on the website is:

> Can a native Mac code editor really be that much better?

I honestly thought that this must be a fork of Text Wrangler.

Footnote: Text Wrangler was merged into BBEdit and this was superficially complicated enough that I never made the switch. I think this is an I promise the problem is with me situation.

Re: Nova by Panic

#507
post #28

I love native Mac apps, I love Panic…but I’m not sure what this gets me over Visual Studio Code, besides a Preferences pane that isn’t inscrutable. I’m not sure there’s enough of a market on the Mac for another commercial code editor, as we already have BBEdit for hard-core text wrangling. (And obviously all the open-source options.)

Biggest draw for me would be how it handles Dvorak-Q method input. I found VSC falls apart on Mac with that where Coda handles it like a champ.

Re: Nova by Panic

#508

Earlier quoted context omitted.

But 95MB is small enough that it doesn't matter—1/3 the size of basically nothing is still basically nothing. Even in terms of memory or CPU usage, VS Code is relatively efficient compared to some other products on the market such as the JetBrains IDEs. Say what you will about Electron apps in general, but Microsoft has done a great job in making VS Code not feel like a typical Electron app.

> VS Code is relatively efficient compared to some other products on the market such as the JetBrains IDEs. That's not really a fair comparison I think. JetBrains IDEs do a lot more than VS Code. You'd have to load it up with plugins to make something resembling a fair comparison, and in that case I'd be very interested in how efficient VS Code still is.

I completely agree, but I would wager that VS Code would still be noticeably faster even if it had all of the functionality that IntelliJ does. As a daily user of the latter, it seems like they have a lot more room for optimization, whereas VS Code seems to have been built from day 1 with performance in mind. But this is pure anecdote so I could be wrong.

Re: Nova by Panic

#509

Earlier quoted context omitted.

> hierarchical playlist Like playing music by albums, or artists and it would recursively play all of the music within those albums?

You could have a playlist with folders, which you could collapse, expand, nest, etc. It would then be played in order, yes, recursing through all the layers.

What order did the folders play? Was it usually just the order of the album tracks, or was it more folders of playlists where you custom ordered each? So you might have a playlist of playlists of programming music for instance.

I might be able to replicate this by building a front-end for it which converts it into a flat playlist for Spotify/Apple Music etc.

Re: Nova by Panic

#510
post #486

Earlier quoted context omitted.

If it's an open source browser (Firefox or Chromium-based) can't you submit a patch?

That is likely to be non-trivial to develop unless you’re very comfortable with large, complex C++ projects and then you have to convince them to accept and ship ship it. That’s better than not having the option but it’s not for the faint of heart.

Chromium — yeah, seems like not friendly towards outside contributors, and nobody has convinced Google to accept stuff they don't care about (JIT for unpopular CPUs, support for new windowing systems, video decoding acceleration APIs, …).

Mozilla? Getting your patches merged is rather easy and very pleasant. Firefox is truly a community project we all build together.

Post reply on HN