321–330 of 549 posts
Is there some reason that text macros aren't a built-in feature more often? I spent a lot of years using the very simple PFE on Windows because it had text macros and code snippets / templates. VS Code doesn't have them and neither does this one. Do people not find this useful or at least useful? I guess I do a lot of data munging with coding.
It's all well and good to strive to take advantage of a native OS but it should not come at the cost of platform exclusivity.
Why not? Most developers seem to work on one platform anyway. It’s time someone built a good macOS-native editor. There are already plenty of non-native solutions out there.
The developers in my team work on a mix of MacOS, Linux, and Windows.
In the face of VSC, a MacOS-exclusive app simply does not compete.
Earlier quoted context omitted.
> Coda was far ahead of its time Other than the Cocoa UI what feature did it introduce? > Panic is well known for decades for making incredibly high-quality software They make great UIs that for sure, but other than that I wouldn't consider them a great software company. Transmit 4 is one of the slowest FTP clients I've ever used. [0] Coda 1 and 2 were extremely slow. I remember years ago a coworker had to wait a min…
Transmit 4? That came out over a decade ago. Why would you use that as a basis of comparison? Transmit 5 has been out for more than three years.
Earlier quoted context omitted.
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…
Do you use it with lsp-mode or similar? 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.
Earlier quoted context omitted.
> I'm sure there's a VSC plugin for that This part of your comments nails 100% why, for me (web developer, 90% in typescript these days), it's nearly impossible to justify paying for an IDE. Visual Studio code has almost everything that I need, and what it's not baked in, is easily done with a plug-in, which in the worst case I can write myself. But that's really a worst case scenario, since to this date it has never…
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…
It really depends on you wanting to use something like Emacs, of course.
> Here's a little editor story for fun. During beta we found some bugs in Apple's text layout engine that we just could not fix. Our solution? Writing our own text layout manager… from scratch. Not only did this fix the bugs, but it also boosted our editor's performance. We're not messing around! Seems like there's nobody better than Panic at doing this sort of thing. They're willing to push Apple's UI forward, but t…
"Writing our own text layout manager… from scratch". I would be pessimistic of the magnitude of this statement. I do a significant amount of text engine work and I'm skeptical what they implied by this. The likely case is they glued together other solutions (Like HarfBuzz/FreeType/etc) and expose their own API on top of that. This is perfectly acceptable and even encouraged for accessibility reasons. It may be that C…
I really like their pricing structure here. If you want updates forever, it's functionally a subscription (which makes sense - constant updates require constant dev work). The key difference is that if you stop paying, you keep everything you've paid for previously (the app and all past updates). That's a _great_ way to do a subscription.
Test your site out on Firefox, then we'll talk.
The site seems to work fine for me on Firefox 80, both Mac and Windows - what problem do you see?