grayrest

26 ms·

211.
by grayrest 11y ago
> This was a few months ago, things may have improved. Polymer improved substantially with the 1.0 release. It was basically a full rewrite so if you checked it out before then, you'll have to re-check.
212.
by grayrest 11y ago
The message I got from Persona was "hey we're developing this thing, it'll be part of Firefox." Sounded like a pretty good idea to me and the signal for it being ready so I could reasonably push for adoption. Then it got
213.
by grayrest 11y ago
> And there is not much to it, really. The two use the same model but are organized differently so it throws me off a bit. Re-frame chooses to hide the actual reduction step so instead of the big switch statement you have a bunch of regi
214.
by grayrest 11y ago
Happy to hear that. I'm not actively using it and I find the the docs are fairly good but written from the implementor's perspective so they tend to bury the lede. I didn't think it had the equvalent of Reagent's reactio
215.
by grayrest 11y ago
I wrote a 20k LoC bacon app in 2014 and had the same issue with being able to understand all the pieces individually but having trouble comprehending the whole system. I don't have non-architecture answers for how to organize code sinc
216.
by grayrest 11y ago
I'll answer these specifically for Clojure since they vary by language. > encapsulation Encapsulation is primarily a state control concept. It reduces the surface area of a piece of data to the object it's contained in. The red
217.
by grayrest 11y ago
It's about the same but everybody uses vim a bit differently so YMMV. I switched from emacs+evil to cursive+ideavim. My annoyance with evil is that `xp` doesn't work, my annoyance with ideavim is that the `{` text object is scope
218.
by grayrest 11y ago
IdeaVIM provides reasonably good vim emulation. You'll probably get annoyed by something (I have yet to find a vim emulator I think is as good as Vim itself) but I only had to make a few minor changes in my vim patterns to get it worki
219.
by grayrest 11y ago
It'll get there simply because the language is doing pretty well and lots of people write web servers but it's not there yet. Once someone figures out "the way" to do an internet-facing async http/http2/websock
220.
by grayrest 11y ago
This is on a 2012 MBA for a prod build. I see times of 140s or 180s on a fresh dev build. Times are lower on faster machines but still in the multiple-minute range. I'll tweak the build JVM settings tomorrow and see if that improves th
221.
by grayrest 11y ago
> non-lisp pretty-printer? Brandon Bloom's fipp[1] works fine but the Chrome Canary dev tools have support for object formatters. I get reasonable results on .170 just doing a (js/console.log a-map). [1] https://gith
222.
by grayrest 11y ago
I was roughly where you were at the beginning of the year. I've been in and out of the Clojure community for a couple years and decided to take a job writing clojurescript full time. App is around 15k loc and was initially in Om and ha
223.
by grayrest 11y ago
> Didn't Mozilla just drop their contract with Google, saying they no longer needed that revenue? There was a clickbait title that just came up but the contract came up months ago and Yahoo won the bid for the US default search prov
224.
by grayrest 11y ago
> pre Seamonkey naming Maybe you predate me but when I jumped on the Mozilla bandwagon at Gecko 0.7.1 the internal name for the suite was Seamonkey. It was only after Firefox that the group maintaining the suite started using the interna
225.
by grayrest 11y ago
My assumption was that writing the handful of sCU I think you'd need is simpler than handling coordination. You seem to have a reasonable understanding of the tradeoffs. > At that point, it seems you're not necessarily any bett
226.
by grayrest 11y ago
Putting everything in one map and naively rendering it is a pattern that comes from the clojurescript subset of the React community and it works because the cljs wrappers assume cljs' immutable datastructures and all implement shouldCo
227.
by grayrest 11y ago
I don't have a reference for this, but when it's come up in the past they've said size is not a primary goal for the project. A lot of the size comes from their internal event system that normalizes events cross-browser along
228.
by grayrest 11y ago
My wishes are much more prosaic. It's not clear to me just from reading your docs how I can extract data from a JSON file using the pattern this benchmark shows (top level key containing the data, other keys containing metadata about t
229.
by grayrest 11y ago
I always considered the quiet years up until 2005ish. After that we had XForms and the WhatWG hijincks to keep the web nerds entertained.
230.
by grayrest 11y ago
I've heard people talk about it but I'm not aware of anybody actually trying it. I know that Rich has stated a number of times that he's not interested in working on Clojure-in-Clojure.
231.
by grayrest 11y ago
I enjoyed your blog series on serde perf. One thing I noticed in this example was that the D example worked pretty much exactly like I want serde to work in that it was able to deserialize a subset of the overall document and the Coord stru
232.
by grayrest 11y ago
Clojurescript is the more "all the way down" of the two. It managed to self-host a few months ago so in theory you could write a backend and cross compile to your computing platform of choice. I know of a number of alternative tar
233.
by grayrest 11y ago
The JSON looks like this: {"coordinates": [ {"x": 0.65, "y": 0.23, "z": 0.91, "name": "fwgzd", "opts": {'1': [1, true]}, {"x": 0.4
234.
by grayrest 11y ago
Here's the "how so fast" explanation: https://github.com/kostya/benchmarks/pull/46#issuecomment-14...
235.
by grayrest 11y ago
The Clojurescript community are ahead but not by that much. To list specifics, cljs->babel+and immutable lib, figwheel->react-hot-loader, reagent->react 0.14 pure components, core.async->js-csp (or async/await). In terms of
236.
by grayrest 11y ago
The Elm and Reagent (Clojurescript) communities build apps this way. It's theoretically possible to do everything in render in practice you wind up wanting to do things in other lifecycle events (e.g. display a google map) in most apps
237.
by grayrest 11y ago
> if rust could compile within 5-10x the time go does, it would be much more pleasant to work with As someone who's been around Rust for a long time but writes very little code in the language, I'm looking towards the MIR work
238.
by grayrest 11y ago
The problem isn't the propagation, it's the propagation by default. He wants errors that occur in development to pop a stack trace as soon as the error occurs without needing to attach a .catch handler.
239.
by grayrest 11y ago
I wish the we were getting F#'s computation expressions+asynchronous workflows (monad sugar) instead of C#'s async/await.
240.
by grayrest 11y ago
The same region/ownership discipline that Rust provides to handle memory turns out to be useful in other contexts. One is resource usage: you have to close a file handle after opening it, etc. Patterns for cleaning up after yourself ar

More ›