Skinney

31 ms·

301.
Elm 0.19 brings better collections(dev.to)
4 points by Skinney 8y ago|0 comments
302.
by Skinney 8y ago
> Most compilers that target WebAssembly can also target asm.js, which is compatible with IE. asm.js is different enough that it's just not about adding a seperate asmjs "compatibility" target. On the top of my head you do
303.
by Skinney 8y ago
I know, I'm one of the people looking into it.
304.
by Skinney 8y ago
I think he was saying that during those 18 months of 0.19 development, everything was stable. 0.19 is very much a breaking change.
305.
by Skinney 8y ago
Your experience is different than mine, but I don't believe externs inference was in last time I built a cljs web app. I still use Clojure as a backend language (I'll never give up Datomic) and while writing code in Clojure is usu
306.
by Skinney 8y ago
> there's no details on how to do it manually. The document I linked too contains the language and std-lib changes between 0.18 and 0.19, for the rest you use new packages. If you don't want to upgrade that's fine, but you
307.
by Skinney 8y ago
It's in the release notes, as with every other open source project: https://github.com/elm/compiler/blob/master/upgrade-docs/0.1...
308.
by Skinney 8y ago
> This is almost never a problem since you simply use normal externs file for whatever library you are using. "almost never" and "simply use externs file (which you may or may not need to write yourself)" does underpi
309.
by Skinney 8y ago
WebAssembly is still far away from being any sort of default for web development yet (if only because IE11 doesn't support it). I also wouldn't be surprised if Elm compiled to wasm in the future.
310.
by Skinney 8y ago
Elm doesn't use node.js or npm.
311.
by Skinney 8y ago
Just glanced through the code for 0.19 (I originally wrote an issue about the advanced opts incompatabilities for 0.18) and the things which caused problems before are gone. That's not to say that there are not other issues, though.
312.
by Skinney 8y ago
The "problem" with ClojureScript's integration is that you have to be careful when integrating other javascript libraries (which ClojureScript encourage you to do to save code size) as they might not be compatible with advanc
313.
by Skinney 8y ago
You'll get a small batch of breaking changes, most of them will be automatically fixed by the elm-upgrade tool. The community will probably migrate to 0.19 faster than 0.18 or 0.17, which both had much more breaking changes than 0.19.
314.
by Skinney 8y ago
Every single version of Elm has had breaking changes. However, 0.17 -> 0.18 had an update tool that automatically fixed most of those changes, and a tool for that will be available for 0.19 as well. NoRedInk (where Feldman works) are alr
315.
by Skinney 8y ago
Why does it matter when the next release is coming, as long as the project is actively maintained?
316.
Elm: De-throning the List(dev.to)
2 points by Skinney 9y ago|0 comments
317.
by Skinney 9y ago
It's an easy thing to do in JS, it happens if you forget the `var`.
318.
by Skinney 9y ago
Spin up a new actor for every message? Actor's are cheap, right? And don't form cycles.
319.
by Skinney 9y ago
Only different major versions (that is, you can reference a/v1 and a/v2 in the same project, because the import path is different).
320.
by Skinney 9y ago
elm-format doesn't wrap long lines either. I'm not sure it would be a good thing if it did, to be honest.
321.
by Skinney 9y ago
Context is important here. Just one or two sections up it describes why having two different major versions of a package in a program can be a good thing (which is something dep don't provide, as far as I know).
322.
by Skinney 9y ago
So? My point is that most who relies on client-side code to render apps, does so in a way that integrates nicely with the browser. Most JS apps render html, they don't draw to a canvas. They could do that, but it would break a lot of f
323.
by Skinney 9y ago
WebAssembly doesn't change this. There's nothing preventing people from doing this with javascript (plain or asm.js flavored) and canvas/webGL, and yet no one does. It just doesn't make a lot of sense.
324.
by Skinney 9y ago
But why on earth would you do that? That would be like bypassing the native UI framework on iOS or Android. It gives a worse experience for users, and is likely more work for you, the developer.
325.
by Skinney 9y ago
Why? For almost everyone, it would be less work and give better results to just have a WebASM app render HTML. Except for "legacy" apps written in C++ and some native UI framework, why would anyone bypass using what is already the
326.
by Skinney 9y ago
I think it would be naive to believe that adding generics to Go would have no effect on the stdlib, third party packages, and ultimately how you write Go code.
327.
by Skinney 9y ago
Project Loom seems to be much better than async/await. Hopefully they manage to implement it.
328.
by Skinney 9y ago
Since `>` is a function, you can just read the function doc (you can do this by calling (doc >) in the repl): user=> (doc >) ------------------------- clojure.core/> ([x] [x y] [x y & more]) R
329.
by Skinney 9y ago
From what I've gathered, the new Firefox is fast because it makes better use of multiple cores. But is F57 still faster on a single core?
330.
by Skinney 9y ago
That place reserved for child molestors and people who speak at the theatre?

More ›