As somebody who worked on two IDEs which didn't fork VSCode but still used Monaco for code editing views, I think forking VSCode is almost always the right solutions for a new IDE. You get extensions, familiarity and most importantly, don't waste valuable time on the boring stuff which VSCode has already implemented.

Nothing bad with using code other people made open. Our whole industry is built on this.

▲

ghuntley 4 hours ago | parent | next [-]

it isn’t http://ghuntley.com/fracture

forking vscode? simple. extensions not so simple. they are controlled by microsoft. without them you’ll run into continual papercuts as a vendor who has forked vscode.

▲

nahuel0x 5 hours ago | parent | prev [-]

Why the need to fork it instead of creating a new extension? (besides marketing)

	▲	benoau 5 hours ago \| parent \| next [-]
		Because if they're just an extension they're stuck with whatever rules Microsoft makes up, and Google is no stranger to using this leverage against others.
	▲	meowface 4 hours ago \| parent \| prev \| next [-]
		Because there are plenty of good reasons why you may want to modify/extend the code and the look and feel beyond what an extension would let you do. I never understood why people scoff at VS Code forks. I'd honestly tend to be more skeptical of new editors that don't fork VS Code, because then they're probably missing a ton of useful capabilities and are incompatible with all the VSC extensions everyone's gotten used to.
	▲	jonny_eh 4 hours ago \| parent \| prev [-]
		https://www.bleepingcomputer.com/news/microsoft/microsoft-ap...