|
|
|
|
|
|
by xtian
1216 days ago
|
|
|
Why are you interested in having a discussion on any of this when you can just talk to yourself (i.e., write your own)? It’s really not that hard. Yes, Elm and its core packages had bugs and critical omissions that were outstanding for years, many of which affected our app. It was a running joke on our team to try to guess the vintage of the extant GitHub issue whenever we ran into a problem. I consciously fled the ecosystem and community many years ago so I don’t remember specifics anymore. And the repos were scrubbed of all past issues when 0.19 was released so we can’t go check either. If you appreciate implied threats for creating a package which gives people some (unauthorized!) control over their own destiny, then I can see why this comment wouldn’t trouble you. Have fun in the sandbox. |
|
|
I'm interested in systems which permit bug-free programming. Elm seems like a step in the right direction, bringing semi-obscure ideas closer to the mainstream. Lot of JS programmers got some exposure to Elm-like FP.
> you can just talk to yourself
I mostly do. (I'm a recluse, this account on HN is my primary channel of communication to the outside world.)
> (i.e., write your own)? It’s really not that hard.
I am writing my own system, and it's really not that hard.
> Yes, Elm and its core packages had bugs and critical omissions that were outstanding for years, many of which affected our app.
That sucks. But really, without any details your vague memories aren't much to go on.
> appreciate implied threats
I'm not sure what you mean, maybe I misread the message. It didn't sound to me like anyone was threatening anyone.
> Have fun in the sandbox.
Thanks! I will.