"Ember CLI blueprint for initializing a Ember application with a module unification layout." Jargon is unfamiliar to people outside.
-
-
Replying to @samth @jlongster
That jargon sucks. I'm embarrassed of that, especially "module unification layout". That said, it's an internal detail, so diff.
1 reply 0 retweets 0 likes -
Replying to @wycats @jlongster
ppx is also internal OCaml jargon. Monad and applicative are no more jargony then data binding or borrowing.
1 reply 0 retweets 1 like -
Replying to @samth @jlongster
It's internal jargon in the elevator pitch of a project meant to be used directly by end users.
1 reply 0 retweets 0 likes -
And the fact that you think those jargons are equivalent is probably related to everyone's great surprise that monads aren't taking off.
1 reply 0 retweets 1 like -
Data binding and borrowing are terms carefully chosen to have some sort of intuitive meaning in English. One of these is not like the other.
1 reply 0 retweets 1 like -
Replying to @wycats @jlongster
This whole take is bad and not reflective of your usual level of thinking about things.
1 reply 0 retweets 1 like -
Replying to @samth @jlongster
You think that "borrow" has the same kind of jargony nature as "monad" despite borrow being an English word meant to analogize borrowing?
1 reply 0 retweets 0 likes -
Replying to @wycats @jlongster
I think "applicative" is no easier to understand than "monad" despite the friendly name and that helpful names matter less than you'd think.
3 replies 0 retweets 1 like -
Replying to @samth @jlongster
"applicative" is not very similar to "borrow" in the friendly name dept. All of
@nikomatsakis' talks have stick figures borrowing things1 reply 0 retweets 0 likes
Also friendly names matter a lot. There's a reason for the name/cache invalidation joke.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.