Casper Beyer
medium.com/@caspervonb · Personal blog · on HN since 2015
Casper Beyer is a programmer who writes opinionated posts on Vim, Electron, Node.js, programming languages, and Go.
What HN saysHN commenters cite his Electron and Vim posts for memory usage claims, and his Node.js piece when criticizing language package managers.
30HN people shared it
5linked it in comments
45stories submitted
743story points
6 years agolast shared
2015people per year2026
Most-shared posts
- 1A Brief Totally Accurate History of Programming Languages8 people · 52 points · first shared 2018 · 1 comments on HN
- 2Why I Still Use Vim4 people · 186 points · first shared 2017 · 197 comments on HN
- 3The Node.js Ecosystem Is Chaotic and Insecure4 people · 64 points · first shared 2018 · 40 comments on HN
- 4Electron is Cancer3 people · 31 points · first shared 2017 · 15 comments on HN
- 5In Memory of Dennis Ritchie3 people · 26 points · first shared 2017 · 1 comments on HN
- 6Why I Still Use Vim2 people · 147 points · first shared 2018 · 108 comments on HN
- 7Visualizing Sorting Algorithms with Web Audio for the Heck of It2 people · 14 points · first shared 2018 · 1 comments on HN
- 8Amok and Hot Patching Scripts2 people · 5 points · first shared 2015 · discussion on HN
- 9Hello Go1 people · 83 points · first shared 2018 · 69 comments on HN
- 10Electron is Harmful1 people · 45 points · first shared 2017 · 36 comments on HN
- 11Benchmarks show Electron apps are slow and eat memory like there is no tomorrow1 people · 23 points · first shared 2017 · 7 comments on HN
- 12Live Code Editing with Amok 1.0, the Future and Time Travel1 people · 9 points · first shared 2015 · 2 comments on HN
- 13Happy Birthday Linux1 people · 7 points · first shared 2017 · discussion on HN
- 14The Absurdity of Cyber Laws1 people · 7 points · first shared 2019 · discussion on HN
- 15Node.js Is Chaotic and Insecure1 people · 6 points · first shared 2018 · 1 comments on HN
What HN people wrote when they linked it
bayindirh · 2018-01-15
First of all, for the 800MB thing, there's the source: https://medium.com/@caspervonb/why-i-still-use-vim-67afd76b4db6?21 and I've also seen this behavior while editing small Python files. I also had no other plugins other than the default bundle. So my atom installation was pretty lean.
It looks like you're a web developer, I'm not. I develop at the system level, and for development scenarios Atom is nowhere capable as Eclipse, and seriously that's OK. Every IDE has its niche. I used atom as a pretty text and script editor for my needs, but its auto complete capabilities left too much to be desired for me.
Honestly, maybe atom was not optimized for better memory usage before. Maybe there were memory leaks. Maybe my build was buggy (I used an official deb package BTW), or maybe he tested a buggy version, but these problems were (or are) real for some other people, and they may have been solved or not; but I'm neither the only, nor the last people who talked about excessive memory usage of atom.
I loved atom when it first came out. I tried to migrate to it, but it has burned me with its radioactivity. So I returned to my dark corner under Eclipse to work and recover.
movedx · 2018-04-23
I've got three Go files open and looking at all the processes related to "Visual Studio Code.app", I see a residential memory footprint of 660MB. I'm using the latest version.
That also coincides with:
https://medium.com/@caspervonb/why-i-still-use-vim-67afd76b4db6
And
https://github.com/jhallen/joes-sandbox/tree/master/editor-perf
digi_owl · 2018-04-12
Especially now that every damned language comes with their own custom package manager, with node.js as the posterboy:
https://medium.com/@caspervonb/the-internet-is-at-the-mercy-of-a-handf…
thealfreds · 2018-01-07
Working Link -> https://medium.com/@caspervonb/electron-is-cancer-b066108e6c32