3 ms·
What are your thoughts on eventually forking the language and moving it in a different direction? Like 100% typed and AOT compiled, similar to Hack/PHP situatio
by dcgudeman 5y ago
What are your thoughts on eventually forking the language and moving it in a different direction? Like 100% typed and AOT compiled, similar to Hack/PHP situation with Facebook.
- jez 5y agoWe're reluctant to completely fork the language. We benefit from so many open source tools, technologies, and libraries built around Ruby. For example: we've built: - A type checker - LSP-based editor tooling - A compiler But we haven't: - implemented our own GraphQL, protobuf, gRPC, or JSON libraries - built a Ruby debugger or debug protocol adapter - built custom performance monitoring tools - etc. There might come a time when it makes sense to fork the language, but we've been very reluctant to do so from the start, because we know what we'd be throwing away. "Compatible with Ruby" has been an explicit design principle of Sorbet from the start: https://github.com/sorbet/sorbet/#sorbet-user-facing-design-principles https://github.com/sorbet/sorbet/#sorbet-user-facing-design-...
- dcgudeman 5y agoWould you guys ever consider reimplementing the runtime for more aggressive optimizations? Thinking back that was the first step Facebook took towards their Hack transition.
- cutler 5y agoThere's Crystal already so what's the point?