4 ms·
- no private repos (the standard PKG manager assumes GitHub). You need to use another package manager - yearly updates in the official blog - it's very hard to
by frozenlettuce 7y ago
- no private repos (the standard PKG manager assumes GitHub). You need to use another package manager
- yearly updates in the official blog - it's very hard to convince a team when it smells like abandonware - besides not being. The fact that the language has a single centralist owner does not help (just look at the blog posts, it's always "I did this, and that", not "we".
- active work from the owner to shut down another PKG manager (Pine, if I recall correctly), because it allowed usage of """kernel""" modules
- k_bx 7y ago> - no private repos (the standard PKG manager assumes GitHub). You need to use another package manager Yes, but a minor point I'd like to make is that because of how Elm is organized, you just put stuff in your src folder and it immediately compiles (since there's no JS FFI etc.). So it's not as big of a pain as it might seem.