91–100 of 459 posts
I do need to give Visual Studio Code a fair shot. Heard a lot of good things about it.
Eh. Why is 1.0 out already? Keyboard layouts which use AltGr are still broken. E.g. I can't type '@', '\', and 'µ'. Yes, I can't write metadata annotations or escape some characters.
> Eh. Why is 1.0 out already? Keyboard layouts which use AltGr are still broken. Perhaps such keyboards don't concern that many people?
Earlier quoted context omitted.
Atom is nice but much slower than ST3. It takes 30 seconds to open a file while ST3 almost instantly loads. It's not worth switching from Sublime.
I've been using atom for several months now, and i've never had a file take 30 seconds to open.. Granted all my devices use SSDs, but still for me it's been like 10 seconds at the worst, and currently it opens in like 3-4 (and i have about 30 plugins too)
The killer feature of Atom to me is the ease with which it can be extended (via packages) and the openness to community contribution on core features. That's not a knock against any other editor (some of which share similar characteristics in this regard) – it's just what draws me to Atom. It's super easy to hack on and contribute to.
It's the Cycle of Bloat. 1. Develop tool. It's small and fast and minimal! Woo! 2. It's easy to modify because it's so small! Woo! 3. Look, there's a budding ecosystem of packages! Woo! (Let's not talk about the fact the packages exist precisely because the original product wasn't big enough.) 4. Oh dear, some of them conflict, a lot of them suck. Well, here's some winners, let's pull them into the core. Now the base…
For your step 6, it just means disable all packages and add them back only as needed.
Earlier quoted context omitted.
Comes down to preference. I still use sublime for opening really large files. But otherwise i stick with Atom. I've found when using linters, typescript compile checking and such Atom is just better. The notifications built in and such are great, where as the bottom bar for listing that kind of stuff in sublime feels archaic.
The consensus seems to be that Atom is still much slower than ST3; I'm still on ST2, and I find it terrible for opening large files and mostly resort to Emacs for that sort of task (and anything involving search and replace with regular expressions on even moderately-sized files). Is ST3 markedly faster than ST2 and generally worth upgrading to now? (I've held off upgrading because I've always been in the middle of a…
I remember when Atom beta came out I was turned off because it (presumably) didn't run on Windows(my workstation at the time). Then I remember trying to give it a try once again a few months ago but gave up because I've heard so many horror story about performance issues. Now I'm willing to give it yet another try because of vim-bindings and performance issue improvements. Is it at workable state?
> Is it at workable state? I would say so. I've used it as my primary code editor for several months now and really enjoy it. Yeah occasionally you can tell it's a web app running on the desktop but only because opening projects or large files is kinda slow (also an occasional JavaScript error but I haven't seen those in a least two months) but beyond that it works very well. Very speeding on my MacBook and my HP Spe…
The killer feature of Atom to me is the ease with which it can be extended (via packages) and the openness to community contribution on core features. That's not a knock against any other editor (some of which share similar characteristics in this regard) – it's just what draws me to Atom. It's super easy to hack on and contribute to.
It's the Cycle of Bloat. 1. Develop tool. It's small and fast and minimal! Woo! 2. It's easy to modify because it's so small! Woo! 3. Look, there's a budding ecosystem of packages! Woo! (Let's not talk about the fact the packages exist precisely because the original product wasn't big enough.) 4. Oh dear, some of them conflict, a lot of them suck. Well, here's some winners, let's pull them into the core. Now the base…
I really want to like Atom but it's such a pity that they went for CoffeeScript instead of plain ES5/ES6.
That's really only a problem if you're contributing to the core, right? You can write your own packages in JS, and if you're just a user of the editor I don't see how that matters.
I've gotta say, honestly, I'm preferring Visual Studio Code over Atom simply due to the fact that it seems MUCH more stable and lightweight. Atom is very visually appealing, and I'm a fan of the project, in general, but it constantly freezes up and crashes on me. I think I'll be sticking with VS Code & Sublime.
Can it be that we are both using old version of the editors (atom for you and vsCode for me)? Else it seems strange this difference of behaviors
www.developingandstuff.com/2015/04/setting-up-atom-for-rails-development.html