this post was submitted on 30 Jan 2024
261 points (95.5% liked)
Open Source
31354 readers
206 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Depends on what you're used before I guess. I came from sublime text which was written in C++ and was blazing fast. You could throw any size file at it, I still use it when I need to edit a large file. I can notice the input lag in vs code even in small files with a vanilla setup. After adding plugins the lag can become even more noticable and in certain use cases it straight up slows you down. It's not so slow that it's unusable, but it's noticably slower, and leaves me desiring more speed. But speed alone isn't enough, it needs really good plugins which is why I traded speedy sublime text for vs code in the first place.