This is why I don’t drink

I don't understand all the rage about forking VSCode. If you want to contribute, sure, but otherwise, if you run your own fork separately, you lose out on the extension ecosystem (and the official marketplace), which is arguably VSCode's biggest merit.

I love that though

apparently people who interview me for jobs do not tho 😝

@kamen you can install plugins from the website by dragging and dropping

It looks like a shot glass

@kamen Fuck Microsoft stores, OpenVSX is simply the best out there.

Better fork: Make UI nice

Eclipse's fork: Add another useless toolbar, pick a terrible name

@kamen The extension *ecosystem* includes OpenVSX. By forking VSCode, you mostly miss out on extensions developed by Microsoft under a restrictive license to prevent forks of VSCode from thriving so that they don't have to actually play the FOSS game.

Why ever fork it, write a plugin, they can do anything and it's very comfortable to do.

You should fork kilo editor. That's for the winners. Did that, done that. Added lua to it like vim has vim script