Let's have a real conversation about ayo HOT 10 CLOSED

@hashseed "I'm sure many of us use Node.js day to day due to obligations work related."
Go and Java are pretty solid. Dart is awesome too, but kind of defeats the purpose of my statement.

Seems like more bureaucratic bullshit is required in order to get any shit done in the Open Source world. Good thing I don't really participate in any of it, thought this would be an opportunity to write something meaningful for the community. Thanks for informing me though.

from ayo.

🤣

from ayo.

@hashseed then what is the point of even forking it if no one else is going to use it. I'd rather just use Elixir and C/++ at that point. I don't even have 100 followers on Github and not even 1k followers on Facebook. Not sure how anything I produce would gain any traction whatsoever. Just kind of reality you know?

I've spent enough time doing similar things living in my own bubble. No need to spend time engineering things that don't really benefit me (but could benefit a lot of other people... technically the entire internet... but hey... Politics is politics).

from ayo.

Remember the days when every browser had its own flavor of JavaScript? That's what you are proposing, essentially.

from ayo.

Fwiw, threading in the form of standard (Web)Workers is something I’ve been wanting to approach anyway in Node.js.

Also, while I agree with what @hashseed is saying here, I think it’s also worth mentioning that the amount of technical work required to affect language features is huge compared to the work just going on working on Node; so: If you want to change the language via forking, it’s likely better to start with a fork of a JS engine, not a fork of Node.

from ayo.

Chances are pretty slim for these proposal to make into V8 if they are not made part of ECMA262 standard through TC39. I'm pretty sure this applies to ChakraCore too.

It sounds like you want a different language with other design goals. How about Java, Go, or Dart?

from ayo.

Adding dynamic type inference to the language would be an enormous amount of work. Like tens of thousands of human hours. It's not really reasonable to expect a small team of people just using a JS virtual machine to have the capacity to make this change on their own. You could take it to TC39 or try to build it yourself.

Threading is reasonably possible, though still quite a bit of work. There was prior effort to get web workers into Node.js, so we could probably take that and finish it.

I get what you're saying about atomic operations and low-level data structures, but those are systems-y things, and JS is just not meant for that. JS and ayo are intended more for app development purposes than systems development.

from ayo.

I've been banned from Ayo.js for no reason specified other than my comments

@ChrisCates The repo was locked down for 24h due to spam in some other threads, as far as I can tell what you are saying in this edit is not the case.

from ayo.

V8 is open source, so you can definitely fork it too. I'm just saying that you won't be able to get these changes into upstream V8.

from ayo.

@hashseed I proposed it to be the new standard. That's a little different. However, no one wants it to be a standard. Therefore, I have no interest in pursuing it, because I would literally be living in my own bubble. You're part of the core Chromium and V8 team so you know how the political system works there. Pretty sure I won't be able to get anything meaningful done for the project if this is the kind of response I get.

from ayo.