amk_
Joined 12 years ago
Karma
860
Submissions
235
Member since
Aug 9
Recent submissions
Comment · 8 years ago
Here's one: https://medium.com/@mbaranovski/quick-guide-to-tdd-in-react-...
Comment · 8 years ago
Extracted boilerplate from some of my libs:
https://github.com/alexkrolick/react-lib-quickstart
Want to port this to a CLI eventually, too
Comment · 9 years ago
IMO its origins in the gaming community, and all the moderation features that grew out of it, make Discord a much better fit for open source communities than Slack. For example:
- Individuals can block and report other users
- There are tiered mod levels
- Per-community pseudonyms, but a single account makes it easier to track bad actors
Markdown support, including syntax highlighting, is actually better in Discord than Slack already, too.
If you haven't checked out an OSS community on Discord yet here are a few:
Comment · 9 years ago
A framework like Phoenix would be awesome. Even something more lightweight (Express-like) would be pretty handy. Clojurescript front-end, Clojure backend...
Comment · 9 years ago
CSS-in-JS libs like https://emotion.sh make "micro-componentization" even easier - pretty much every raw DOM element can be replaced by a domain-relevant/ui-relevant component type. Then if you need to add something beyond styles like state or complex render logic, the consumers don't even know about it because the reference is the same.
Comment · 9 years ago
Fastify is a similar project that aims to be faster than Express and adds a number of API improvements like baked-in schema validation for routes, logging, and async-by-default APIs.
Haven't used it in production but replaced Express with it in some side projects.
Since server.js is built on top of express it might even be possible to build a variant of it on Fastify instead and get those benefits as well.
Comment · 9 years ago
This would be a good checklist for anyone considering building a UI framework. This kind of thing is the reason Bootstrap & friends are so large - they do a lot for you.
Comment · 9 years ago
I have to agree, this will create a new component type every time the function is called, definitely causing a repaint and re-render of the subtree.
The "right" way to do this is re-implement `connect` as a render-callback and then use that to create a HOC, not the other way around.
https://github.com/juliankrispel/redux-connector/blob/master...
Here's a Codepen that demonstrates which component-creation methods are safely inlineable and which aren't:
https://codepen.io/alexkrolick/pen/WZwMYW
GIF of repaints: https://user-images.githubusercontent.com/1571667/30631908-f...
