davidkpiano

12 ms·

91.
by davidkpiano 9y ago
I thought this article was about finite state machines at first!
92.
by davidkpiano 9y ago
Hey HN, the Glimpse Team at Microsoft worked hard to release this tool which we think will be extremely useful for Node.js developers! Think of it as a debugging and diagnostics tool for your entire stack - all the way down to your database
93.
Show HN: Project Glimpse from Microsoft – Full-Stack Node.js Web Diagnostics(node.getglimpse.com)
8 points by davidkpiano 9y ago|6 comments
94.
by davidkpiano 10y ago
I compile the Sass files separately (using Node-Sass) and require the generated CSS file.
95.
by davidkpiano 10y ago
> IMHO SASS covers almost all cases of CSS "at scale". Absolutely right. I covered this in a blog post I wrote over a year ago (which still applies today): http://hugogiraudel.com/2015/06/18/styli
96.
by davidkpiano 10y ago
Made it all the way through! Really fun, please make more levels!
97.
by davidkpiano 10y ago
CSS Modules is still a "naming convention," just one that is auto-generated for you. Naming conventions in CSS are as much of a good practice as naming/linting conventions in JS.
98.
by davidkpiano 10y ago
I'm working on it, I promise! I have been doing a LOT of work on forms in React and Redux, and have been putting all of my ideas into a library called React-Redux-Form: https://github.com/davidkpiano/react-redux-fo
99.
by davidkpiano 10y ago
You should take a look at https://github.com/davidkpiano/react-redux-form - solves many of your problems listed (batches actions when possible to prevent log spam), and V1.0 will be even simpler/more performant.
100.
by davidkpiano 11y ago
It does not need to be replaced, and it's highly impractical for it to be replaced since it's such a core part of all web browsers that's not going away anytime soon. Are you suggesting we style with JavaScript?
101.
Show HN: CSS Animated Husky(codepen.io)
37 points by davidkpiano 11y ago|1 comments
102.
by davidkpiano 11y ago
Hm? Can you give an example where you would need to use an imperative API? Plus, .run() is imperative.
103.
by davidkpiano 11y ago
Those aren't problems with CSS - those are problems with how Facebook architected _their_ CSS. A lot of those don't apply to well-architected projects.
104.
by davidkpiano 11y ago
Exactly. Use PostCSS in conjunction with preprocessors.
105.
by davidkpiano 11y ago
This is the kind of thing that PostCSS should really be used for: responsible transforming of existing CSS without inventing new syntax or doing invisible "magical" transformations. Or trying to emulate built-in features from ot
106.
by davidkpiano 11y ago
If you want to truly customize the way you use preprocessors for typography in your web projects, here's another approach: https://scotch.io/tutorials/aesthetic-sass-3-typography-and-...
107.
by davidkpiano 11y ago
There is a difference, though. The above code is still executable in that it renders the proper styling via JS at run-time, rather than at "compile" time (i.e. when it is preprocessed).
108.
by davidkpiano 11y ago
Look at the source. It's quite literally inline styles .
109.
Show HN: CSS-only Calendar App Concept (Chrome-only)(codepen.io)
7 points by davidkpiano 12y ago|0 comments