Skip to content

Should we fork VS Code? #458

Closed
Closed
@WaynePhillipsEA

Description

@WaynePhillipsEA

I've toyed with this idea for a while now. You guys know I love VS Code very much, and its extensibility is frankly amazing. However, there are certain things that the VS Code team are not open to considering supporting such as proper customizable toolbars, and fully customizable menus, to name just a couple of them. There are also some things I'd love to do to make the transition from VB6/VBA more familiar for developers that are just impossible to implement as a VS Code extension.

Is it a mad idea to create our own fork of Code OSS and do whatever customizations we see fit? i.e. an official twinBASIC IDE?

It could be a maintenance nightmare. VS Code has major releases every month that introduce vast amounts of new features and bug fixes. Realistically, If we did fork it, we'd probably only be able to sync with the VS Code codebase every so often... perhaps annually. So we'd effectively miss out on the brand new VS Code features. But that may not be a bad thing either, as it allows the new features to mature before we look at using them for tB.

Also of note is that on two occasions the monthly update to VS Code broke something in tB that required me to make some adjustments and release tweaked versions of tB to match the changes in VS Code. So having a stable fork to work off would certainly help in this regard.

Enough from me... any thoughts?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions