311–320 of 549 posts
While this editor looks very nice I'm still confused on why I would use this over sublimetext or vscode. It doesn't try to contrast at all just lists a bunch of features that I already have in other editors.
They answered that in the first line of the page > native Mac code editor Looks much more native and likely faster than electron based editors like vscode or Atom.
Earlier quoted context omitted.
That's the first thing I looked for - Java support. Looks like it's not available... for now?
Seems like Panic is billing Nova as a text editor only—not necessarily an IDE. They’d have to add in functionality for a whole host of other things to make that a reality, including compilation, build, debugging, and so on. I doubt all of that can be done with their build scripts and extension framework alone, but, hey—I’ve been wrong before. The state of the IDE landscape on Mac amazes me. It seems like there a $#!*…
Earlier quoted context omitted.
How is that pompous? Seems rather straight forward to be honest.
A rejection email for a product that's positioned like I just got turned down for a job? How is that not pompous?
“We have chosen to go with another beta tester that better aligns with our needs at this time”.
Earlier quoted context omitted.
> and in particular VS Code can’t compete because of it’s business model. What do you mean by that? If there was real demand for it, creating an iPad distribution for VS Code probably wouldn't be that difficult. It already runs great fully in a web browser.
I meant that it's open source with a mix of a number of OSS projects that would all need to arranged and accepted to be packaged in an app to be able to come to the App Store. There has been interest in doing something to have VSCode in some way or shape on the iPad for a long time [0]. I see a lot of "you just need to" iPad on VSCode tricks that basically describe running a part of the UI locally and the rest hosted…
Earlier quoted context omitted.
Seems like Panic is billing Nova as a text editor only—not necessarily an IDE. They’d have to add in functionality for a whole host of other things to make that a reality, including compilation, build, debugging, and so on. I doubt all of that can be done with their build scripts and extension framework alone, but, hey—I’ve been wrong before. The state of the IDE landscape on Mac amazes me. It seems like there a $#!*…
Is IntelliJ generally considered ugly?
Earlier quoted context omitted.
Why is this being downvoted? He’s right. > When purchasing an annual subscription, you will immediately get a perpetual fallback license for the exact version available at the time. https://sales.jetbrains.com/hc/en-gb/articles/207240845-What...
Though it is made slightly (?) better for the fact that if you for 12 month consecutively, then your fallback license is upgraded to the version 12 months ahead. (That is, the next sentence in the bit you quoted is:) > You will receive perpetual fallback licenses for every version you’ve paid 12 consecutive months for.
Earlier quoted context omitted.
I used Emacs for 10 years. When I started writing JS almost exclusively at my current job, I switched finally to VSCode (albeit with emacs keybindings). The plugin/extension experience between emacs and vscode is, of course, almost an apples to oranges comparison. But VSCode is much better in that regard in my opinion. I want yak-free IDE. After ten years my Emacs config is a herd of beautifully shaved yaks. VSCode i…
The problem I've had with VSCode - and also Sublime, as it happens - is that on a moderately large JS project it's something of a CPU hog. Both editors seem to do a lot of indexing, and this is even with loads of ignore folders configured. The irony is that this has driven me to try emacs. I am being driven nearly to distraction by the fact that every single operation seems to almost glory in using a different key co…
One would imagine that most CPU load because of rescanning would happen in the language server, and those should be the same between VS Code and Emacs.
I don't mean to complain about Nova, but I don't think being platform-specific is something to be applauded (in itself). It's like making your webapp only for Chrome -- that's not a feature, per-se.
I used to love Coda back in the late 00s, especially for its live CSS mode (not so revolutionary today with this built into every browser these days), and would happily give Nova a try if they support a decent vim-emulation mode, but without it’s a non starter for me. These days I feel heavily handicapped without it, just recently some tool dropped me into nano and I felt like a child adding random characters to various places in the document while trying to force myself to navigate the text correctly, muscle memory is a strange beast.
I am so confused why they didn't put efforts into making this an iPad app. There is a market for something like this that developers are crying out for, but on mac why would anyone use this over VSCode (and pay $99 for the privilege?)
Does anyone seriously want to develop on the iPad?
The iPad is a computer with a keyboard and mouse and a full-featured web browser. There are also language-specific native IDEs like Pythonista and Play.js. There are Git clients available natively as well. Pretty much the only thing you can’t do is make iPad apps on the iPad, which is a pretty small subset of programmers. Pythonista costs $10 and has nearly 1k reviews, so someone must be using it.
So why do people constantly ask “does anyone really want to develop on a computer that offers many development options?” The answer is yes, of course people seriously want to develop on an iPad.