Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert Build Extensions to Wren Language #181

Merged
merged 45 commits into from
Jan 29, 2023
Merged

Convert Build Extensions to Wren Language #181

merged 45 commits into from
Jan 29, 2023

Conversation

mwasplund
Copy link
Collaborator

By converting to Wren we gain a lot of benefits and only a few drawbacks.

  1. Hosting environment is able to create cleaner runtime environment with 1st class modules to interface with extensions.
  2. Hosting environment is fully sandboxed, preventing build extension from accessing environment to cause issues.
  3. No longer require dotnet sdk as a dependency unless building dotnet code!!!!!!

Downside: The biggest drawback is that Wren is a dynamically typed language which has caused a lot of runtime errors during migration that could have been caught with a static type system.

@mwasplund mwasplund merged commit e123e1b into main Jan 29, 2023
@mwasplund mwasplund deleted the mwasplund/wren branch January 29, 2023 02:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant