Yes you did, you said "It's let me down". I just assumed t was something more serious like major design flaw, or periodic segfaults in the runtime, and not "bugs go in the mailing list" vs "no Github issues".
> > What do you want Ericsson to bake a cake for you?
> Yes.
And they will. Throw in a couple of millions their way in there and they'll take a few engineers off from building their product and you might get a delicious cake.
> Presumably you bring this up because I pointed out there is not a public bug tracker. A mailing list is not a substitue for a bug tracker.
It is not but they are the ones who pay their developers to work on this and they have a bug mailing list. You can still issue pull requests if you want. There are plenty here:
File the bug, submit a patch and discuss there. Some pull requests have 20+ comments.
> there are regular bug fixes, pull requests, frequent releases. New features added (like maps).
Yes, and? And it is not exactly a "throw over the wall. It is like getting a free car from someone but complaining that the seats are the wrong color.And the car has now failed you.
> Where do I go to see the status of, I don't know, native processes?
Ask on the mailing list. Comment on the pull request or go on #erlang on IRC.
> Lastly, I'd ask you to consider what your response has done to improve and grow the Erlang community.
But what has your response done to hurt it? Here someone shared a cool project, and someone else commented how cool it is. And you are complaining that it is a "throw over the all" and it is a failure because they didn't set up Github issues properly. If you are going to spread fud then, well, be prepared to get nasty comments back.
Wow. What a mountain from a molehill. Your response has so little to do with what I've actually said that I can't see any useful way of responding. Good day.
Yes you did, you said "It's let me down". I just assumed t was something more serious like major design flaw, or periodic segfaults in the runtime, and not "bugs go in the mailing list" vs "no Github issues".
> > What do you want Ericsson to bake a cake for you?
> Yes.
And they will. Throw in a couple of millions their way in there and they'll take a few engineers off from building their product and you might get a delicious cake.
> > There is a bug mailing list (http://erlang.org/pipermail/erlang-bugs/),
> Presumably you bring this up because I pointed out there is not a public bug tracker. A mailing list is not a substitue for a bug tracker.
It is not but they are the ones who pay their developers to work on this and they have a bug mailing list. You can still issue pull requests if you want. There are plenty here:
https://github.com/erlang/otp/pulls
File the bug, submit a patch and discuss there. Some pull requests have 20+ comments.
> there are regular bug fixes, pull requests, frequent releases. New features added (like maps).
Yes, and? And it is not exactly a "throw over the wall. It is like getting a free car from someone but complaining that the seats are the wrong color.And the car has now failed you.
> Where do I go to see the status of, I don't know, native processes?
Ask on the mailing list. Comment on the pull request or go on #erlang on IRC.
> Lastly, I'd ask you to consider what your response has done to improve and grow the Erlang community.
But what has your response done to hurt it? Here someone shared a cool project, and someone else commented how cool it is. And you are complaining that it is a "throw over the all" and it is a failure because they didn't set up Github issues properly. If you are going to spread fud then, well, be prepared to get nasty comments back.