Earlier quoted context omitted.
This is exactly backwards, IMO. Command-P is "print" on the Mac, and always has been; Command-O is open. This is the kind of thing that makes non-native apps stand out as poor platform citizens.
It is "p" for pallette IIRC. Same as in Chrome devtools and others. In a development context, I do not want platform-specific quirks. Consistency is really important for me otherwise it is a jarring context switch when e.g. copy-paste changes when moving between OSes (which I do hundreds of time a day - laptop is Mac, developer workstation is in the office and is Linux, so I remote desktop into it for code, but "offi…
Nova 9
51–60 of 107 posts
Re: Nova 9
#52Earlier quoted context omitted.
This is exactly backwards, IMO. Command-P is "print" on the Mac, and always has been; Command-O is open. This is the kind of thing that makes non-native apps stand out as poor platform citizens.
It is "p" for pallette IIRC. Same as in Chrome devtools and others. In a development context, I do not want platform-specific quirks. Consistency is really important for me otherwise it is a jarring context switch when e.g. copy-paste changes when moving between OSes (which I do hundreds of time a day - laptop is Mac, developer workstation is in the office and is Linux, so I remote desktop into it for code, but "offi…
Just remap them if you need, macOS offers great support for this.
Re: Nova 9
#53Earlier quoted context omitted.
I want this to be wrong so badly , but I grudgingly admit it to be true. I want the native app from a boutique software shop to somehow be better than the open-source alternatives.
> I want the native app from a boutique software shop to somehow be better than the open-source alternatives. In a very loose sense, it already is. The apps I’ve seen it compared with in this thread are VSCode and Emacs. The former has the backing of onenof the largest corporations in the world, and the latter has 40 years of development time put it it. That you can even use Nova, Emacs and VsCode in the same sentenc…
Re: Nova 9
#54Tried v1 two years ago. Even purchased an year subscription. Send some bug issues, feature requests. Got reply in 3 months, at which point I was back on Sublime Text 4 and IntelliJ.
Such a beautiful app. I've been a HUUGE Panic fan too, so it was sad to somewhat mentally give up on them. I just recommend JetBrains products now.
I really wish it didn't have to be that way. :(
Re: Nova 9
#55Earlier quoted context omitted.
> I want the native app from a boutique software shop to somehow be better than the open-source alternatives. In a very loose sense, it already is. The apps I’ve seen it compared with in this thread are VSCode and Emacs. The former has the backing of onenof the largest corporations in the world, and the latter has 40 years of development time put it it. That you can even use Nova, Emacs and VsCode in the same sentenc…
I think the takeaway is that an new editor has to be a platform, not just an app. Emacs was an OS for running Lisp code from the beginning, and it was trivially easy for end users who weren't Emacs developers to add their own extensions to it. VSCode has a rich enough API that JavaScript devs were able to do the same with it, and while I think Lisp >>> JS, there are a lot more JS devs out there who can add and tweak…
Re: Nova 9
#56How does it compare to VS code?
Re: Nova 9
#57Nova is absolutely gorgeous. I'm so done with Electron apps, even ones "done well". There's a lot to be said for fast, native apps that look and feel like they belong on the platform you're running them on. That said, Nova's Python support wasn't in the ballpark of VS Code's. But testing it for a while soured me on VS Code, and I ended up switching back to Emacs (which has outstanding Python support via LSP these day…
Emacs with EVIL? If so, do you like the integration?
Re: Nova 9
#58Earlier quoted context omitted.
This is exactly backwards, IMO. Command-P is "print" on the Mac, and always has been; Command-O is open. This is the kind of thing that makes non-native apps stand out as poor platform citizens.
It is "p" for pallette IIRC. Same as in Chrome devtools and others. In a development context, I do not want platform-specific quirks. Consistency is really important for me otherwise it is a jarring context switch when e.g. copy-paste changes when moving between OSes (which I do hundreds of time a day - laptop is Mac, developer workstation is in the office and is Linux, so I remote desktop into it for code, but "offi…
(Personally, I love the fact that copy/paste work in my Terminal with the same keys as every other app)
And, if you weren't aware, the keystrokes and design pre-date most other GUI systems in use today (Ctrl-C/V/X and things like dialogue boxes and menus work were part of IBM's CUA standards which, in turn, were an imperfect copy of the existing MacOS guidelines).
Likewise, MacOS used to have a hugely important rule; because in English we read from top-left to bottom-right, important stuff should be bottom right and stuff we use infrequently or is dangerous at the top-left.
Which is why the Apple menu and the window close button are top-left, why the primary button in any dialogue box is bottom-right. (And there is research, for example eye-tracking studies, showing that this helps significantly with user comprehension of what's on screen). However, Apple gave up on all this research when His Steveness returned and now just wings it - but it's this user-centric stuff that people refer to when talking about the "Macness" of an app.
Re: Nova 9
#59Earlier quoted context omitted.
> I want the native app from a boutique software shop to somehow be better than the open-source alternatives. In a very loose sense, it already is. The apps I’ve seen it compared with in this thread are VSCode and Emacs. The former has the backing of onenof the largest corporations in the world, and the latter has 40 years of development time put it it. That you can even use Nova, Emacs and VsCode in the same sentenc…
I think the takeaway is that an new editor has to be a platform, not just an app. Emacs was an OS for running Lisp code from the beginning, and it was trivially easy for end users who weren't Emacs developers to add their own extensions to it. VSCode has a rich enough API that JavaScript devs were able to do the same with it, and while I think Lisp >>> JS, there are a lot more JS devs out there who can add and tweak…
TypeScript, though? TypeScript I love.
Re: Nova 9
#60I think it’s commendable to be pushing native purpose-built apps in this day and age.
I exclusively use Linux and Windows; I see something like this and ... it's a disappointment.
I think what's "commendable" is cross-platform development, breaking out of walled gardens to support everyone.