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

I saw your talk, and very interesting. But why use the same paradigm as before? #201

Closed
foxjazz opened this issue Jun 7, 2019 · 1 comment

Comments

@foxjazz
Copy link

foxjazz commented Jun 7, 2019

Node is an interesting tool, but why stick with old technology when dotnet core works at scale with greater performance than node, coming into version 3?

This is Month old code, and yet it seems no consideration to architecture was even made and we assume Node is best for this. What a waist.

@chrisdickinson
Copy link
Collaborator

Hi! Node was specifically selected because both ceej and I are well-practiced in it, and the community we hope to grow around the project is likely to be most comfortable contributing JS. (I had to be talked down from writing portions of this in Rust, likewise ceej and golang. JS is the right fit for this project, though. Alternate registries and clients may appear written in other languages.) Notably: we knew we would end up with multiple services, but wanted to build a single functioning service first and split it out (which is what I’m working on in #135), because of Gall’s law.

I also want to note here: coming into a project, disparaging underlying tech choices, and lamenting the choices made is generally considered to be very rude. Further comments like this will be removed and result in a block.

@entropic-dev entropic-dev locked as resolved and limited conversation to collaborators Jun 7, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants