29 ms·
We've also been in the same boat as you guys. Starting to just look into VSCode as an alternative, then immediately switching to it after realising the performa
by akuji1993 8y ago
We've also been in the same boat as you guys. Starting to just look into VSCode as an alternative, then immediately switching to it after realising the performance difference is like night and day.
Since Atom doesn't provide anything that we can't install in VSCode as a plugin, there really is no reason to use Atom right now. The only problem I had with VSCode was the default interface, that I modified with plugins until it pretty much looks like Atom, but runs way faster.
- sdiq 8y agoI still use Atom mostly because of the default interface. Care to list the plugins that you used?
- akuji1993 8y agoOf course. The most useful ones are the following: - Bracket Pair Colorizer - EditorConfig for VS Code - ESLint - Git Blame - Material Icon Theme - Path Intellisense - Prettier - Code Formatter - SCSS IntelliSense - TSLInt - Winter is Coming Theme by John Papa
- Lordarminius 8y agoEmmet.
- akuji1993 8y agoI get why people use it, I just don't have any use case for it. I'd rather write my code myself instead. Just a personal preference though.
- deleted 8y ago[deleted]
- statictype 8y agoI don't find the code generation stuff that useful but I found it useful for its text manipulation features - like selecting all text within 2 nodes, editing a start and end tag at once.
- Lordarminius 8y agoTo each his preference, I suppose. But I definitely could imagine a far more difficult life without Emmet.