biscarch

5 ms·

1.
by biscarch 9y ago
All functions in Haskell are single-argument functions. Multiple arguments are syntactic sugar. The syntax sugar can make it confusing to talk about but if you define an `add` function that takes two arguments x and y: add x y = x + y
2.
by biscarch 9y ago
All functions in Haskell are curried by default Your `add2` uses a tuple instead of currying whereas `add1` is already curried. In ghci: Prelude> (+) 3 4 == (+ 3) 4 True So you could have an `add3` just by applying 3 as the
3.
by biscarch 9y ago
windmove is probably it -- https://www.emacswiki.org/emacs/WindMove
4.
by biscarch 9y ago
link-rest fits the use case where you might not be able to transition the REST endpoint to be behind a GraphQL API (and thus be server-side resolvable which is definitely preferable) due to organizational or other concerns.
5.
by biscarch 9y ago
I've been super excited about Chrome headless but haven't had a chance to dig into using it yet. The api here looks amazing for getting started without getting lost in the weeds. It'd be fairly trivial to hook this up to a Sl
6.
by biscarch 10y ago
I think my intent might have come across wrong here. The "states" aren't related to container/dumb components or data-fetching/selection logic. They're purely about rendering the state for a given segment of th
7.
by biscarch 10y ago
Loading (and error, etc) state should be the responsibility of the component doing the content rendering, not the parent. So the ConditionalSpinner component: <ConditionalSpinner renderIf={data}><PersonRenderer person={data.pe
8.
by biscarch 10y ago
FWIW webpack's docs are getting much better for v2
9.
by biscarch 10y ago
You can use something like dataloader[0] or haxl[1] to help with this issue. [0]: https://github.com/facebook/dataloader [1]: https://github.com/facebook/Haxl
10.
by biscarch 10y ago
You link to a comment which indicates serialization is a potentially breaking issue. This is a tradeoff that does not affect the routine behavior of redux but may affect advanced use cases such as allowing user upload of action history for
11.
by biscarch 10y ago
It is possible to use Symbols instead of strings, which yields some nice improvements in terms of no longer allowing construction of actions with potentially misspelled strings, etc.
12.
by biscarch 10y ago
If you go the docker-machine route, you can do the following. brew install docker-machine docker-machine create --name myserver ...digital-ocean-options eval $(docker-machine env myserver) docker ps that is: * install d
13.
by biscarch 10y ago
Right, except support for that has to be built into the static site generator you're using. In the React case, the user can choose how they want to do it without the SSG author caring at all. I will also say that in the case of frontma
14.
by biscarch 10y ago
Having React on a static blog makes it easier to share component libraries that you've built up on other projects (perhaps SPAs) with said static blog. It also allows the use of React's ecosystem, such as react-helmet[0], which ma
15.
by biscarch 10y ago
As someone who is also building a React-based SSG, what do you believe makes sitegen's design superior to other React SSG's?
16.
by biscarch 10y ago
Location: SF Remote: Yes/Preferably (6+ years of remote experience) Willing to relocate: No Technologies: JS(Babel), React, Haskell, Docker Résumé/CV: christopherbiscardi.com/resume.pdf Email: chris@christopher
17.
by biscarch 11y ago
React Router has been iterating towards better APIs for advanced use cases (server-side rendering, code splitting, relay (and other lib) integration, etc). Having used it in projects spanning the above use cases, the evolution of the API ha
18.
by biscarch 11y ago
I've been using lost for a few months now. Even if you don't use it it's worth taking a look. (built with PostCSS)
19.
by biscarch 11y ago
We use it at $work in an "isomorphic" context along with react-router[0] and fluxible[1]. I'm very happy with it and the ecosystem developing around it. Using React also provides an interesting lead-in to native apps with rea
20.
by biscarch 11y ago
For Haskell, Hayoo[0] works well [0]: http://hayoo.fh-wedel.de/?query=.%3A
21.
by biscarch 12y ago
The link for OSX points to `new-www`.haskell.org. I'm sure the old site still links to haskell platform.
22.
by biscarch 12y ago
After looking into this I've come to the conclusion that rewriting the JavaScript to handle events through React's system is the best way to include Foundation's JS components. (This is something I'm planning to do with
23.
by biscarch 12y ago
You could use this list to discover [other keyword] if you are unfamiliar with the landscape. (For example, Isomorphic applications)
24.
by biscarch 12y ago
I find it no more complicated than things such as figuring out things like clearfixes were in the beginning.
25.
by biscarch 12y ago
Thanks for starting this. It's currently making my life much easier.
26.
by biscarch 12y ago
As an additional datapoint, Haskell's Snap Framework implements O(log n) routing like this: https://github.com/snapframework/snap-core/blob/master/src/S...
27.
by biscarch 12y ago
Agreed, but there are some issues there as well. (The "database" row could easily be labeled "postgres" for example).
28.
by biscarch 12y ago
Are you saying that large SQL strings isn't a code smell if the application is dynamically putting them together? That seems like DSL/Query Builder territory to me. Perhaps you could share an example?
29.
by biscarch 12y ago
That is actually currently being contested by React and .jsx. That said, I've seen multiline abused for writing SQL queries as well, which would have been better off being written in a separate .SQL file and `fs.read` into a string wit
30.
by biscarch 12y ago
https://twitter.com/chrisbiscardi Haskell, JavaScript, YouTube, building things. (Willing to help anyone learning Haskell. Just tweet at me.)

More ›