Hm yeah, so the name should be more specific I guess, since what this thread is about, is bringing better documentation in terms of transparency and communication. So communicating this name clearly makes it easier to understand for other people what this repo is about … ‘elm-discussions’ is quite generic, isn’t it ? I mean we already have a platform for all kinds of discussions, which is here ?
Later on, we can pr-merge this or even multiple workgroup repos (for different purposes) anywhere we want, like into the official community repos.
Nowhere close to being official. The site says “unofficial” at the bottom, and I don’t think elm-lang.org even links to it
I’ve created the repos:
But im not going to write the actual page, as I’m not a native speaker.
2 Likes
My solution has been less to fork and more to try to start from scratch.
For me the biggest pain point is no language similar to Elm on the server side. Reading up on Evan’s thoughts there, it might as well compile to assembly so that’s what I’m doing. Target platform elf64.
For naming, my core design concept to support a pure functional language is partly to stop using the word “function” thanks to ambiguity. My language will support “Lambdas” which are a mathematician’s idea of a function: zero side effects, same inputs always return identical outputs, and “Procedures” which are a software engineering idea of a function: a list of instructions that you blindly follow. Although I am liable to hobble the decision making power of the Procedures to help enforce putting the decision making into the lambdas, that are easier to test and make guarantees about.
Seeing as how the language centers around ineffectual brains paired together with brawn relatively bereft of executive functioning, I decided to call the language MasterBlaster.
Now I’ve no idea if I have the power to take this places or not, but it’s a boulder I push on my spare cycles and try to keep my skills sharpened, largely learning either the ins and outs of modern x64 assembly or weaving between competing internal expectations for the language or perfecting my lexing/parsing/generating/testing chops. 
1 Like
Some thoughts on content for a contributing to Elm site:
- How to build and test a core package.
I realise now, that the bugfix I contributed to elm/virtual-dom was never made into a PR. I’m fairly sure the bugfix is correct because it was quite trivial. But I had no easy way to try it out. Perhaps all I had to do was copy into the ~/.elm folder or something. Anyway, at the time it was a step too far, so I just posted the code into the GitHub issue and left it at that.
- How to build the compiler? Maybe someone already did this somewhere, never tried myself, so not really looked.
Obviously, if someone contributes a compiler bug fix, they are going to need to test it. I guess anyone getting that far is already quite knowledgeable about Haskell. Seen this question come up plenty times on Slack though. It would just be nice to have a README that is detailed enough to walk a complete beginer through from code checkout to having a working compiler.
4 Likes
That one I figured out already. This is for current Debian Stable (which does use quite old ghc).
; might need others also, but this is what I missed
$ sudo apt-get install ghc cabal-install
$ git clone https://github.com/elm/compiler.git
$ cd compiler
; not sure why this is needed, but without this worker is built instead of elm
$ rm -rf worker
$ cabal update
$ cabal new-build
$ cp dist-newstyle/build/x86_64-linux/ghc-8.4.4/elm-0.19.1/x/elm/build/elm/elm .
$ strip --strip-all elm
2 Likes
Thanks - that was easy enough! I’m also a long time Debian user (since 1994).
–
Occurs to me, maybe its time Elm had an official Debian package.
It’s even easier on linux. There’s a docker file in the repo which has all the info you need. compiler/Dockerfile at master · elm/compiler · GitHub Worked very well for me.
3 Likes
That doesn’t work in Debian Stable - the “Retrieve elm Linux binary” step fails.
I tested again with 2x sudo, which I forgot first time, but that still fails.
Anyway - I was suggesting that these kind of build instructions would make some good content for a contributing site, rather than that we need to get into the details here.
Hmm, too bad. I tried it on Manjaro Linux
RIP Topic 
1 Like
Another question that popped into my head: the core team prefers experience reports over feature requests, but it’s not clear to me where to submit such reports. Do they get read when they’re posted on Discourse? How do I know if it’s been picked up on?
We all know to submit bug reports on GitHub, but isn’t not intuitive if you should open a GitHub issue for an experience report. My intuition on GitHub issues is that they are for actionable items at least.
2 Likes
Just yesterday Evan said that he still works on Elm full time:
2 Likes
I’m so glad to read that Evan is still working on Elm full time 
But it doesn’t mean he’s paid for that 
2 Likes
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.