Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
insin
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
44 ms
·
511.
▲
by
insin
12y ago
Not any more - once you can prerender the "SPA" on the server and use the same codebase to rehydrate it on the client and take over - which you can do today with React and soon with Ember - then with the right setup the "prog
512.
▲
by
insin
12y ago
Or make one app with an isomorphic base which gets progressively enhanced when JavaScript runs on the client.
513.
▲
by
insin
12y ago
Both: keeping a changelog and copying a section to the latest relase after tagging it, since they're both Markdown.
514.
▲
by
insin
12y ago
vmd [1] is handy for quick previewing, especially if you're editing for GitHub. If I had to jump out of my regular editor to write Markdown or reStructuredText, I probably wouldn't be using them. [1] https://github.com&
515.
▲
by
insin
12y ago
"He says gods like to see an atheist around. Gives them something to aim at." I love Small Gods :-(
516.
▲
by
insin
12y ago
> But what has [virtual DOM] got to do with reactive programming? Or embedding markup in JavaScript? It makes it possible to implement React's componentisation model in a performant manner. It allows React to not only work in all ma
517.
▲
by
insin
12y ago
As long as the constructor doesn't take multiple arguments [1], otherwise: [1, 2, 3].map(id => User(id)) [1] http://speakingjs.com/es5/ch15.html#_pitfall_unexpected_opti...
518.
▲
by
insin
12y ago
...and too few of the posts complaining about it mention strict mode or ES6 fat arrow syntax.
519.
▲
by
insin
12y ago
If you were to put the event bindings in the markup instead, some of the examples would look very similar to Riot 2.0 [1] tag definitions, although it uses a more Glimmer-like approach which only looks at the bits which can change based on
520.
▲
by
insin
12y ago
I haven't used semicolons in JavaScript in places they're not necessary for years now - the only rule that's mattered in practice [1] is lines starting with [ or (. [1] This is a white lie - there is one additional vital ASI
521.
▲
by
insin
12y ago
Make things. There's no substitute for having a concrete problem to solve, then hitting the docs, reading around and implementing a solution. You'll also find out what it's like when things don't work, which is somet
522.
▲
by
insin
12y ago
Personal logic bugfix: if ( thisLooksLikeJavaOrJavaScriptOr/* ... */ ) { youLikeCamelCase = true; votePoll( camelCaseFormatting ); } else if ( this_looks_like_python ) { you_like_under
523.
▲
by
insin
12y ago
Ripley would have just ran sideways.
524.
▲
by
insin
12y ago
Other than the docs: https://github.com/ryanflorence/react-training
525.
▲
by
insin
12y ago
Worth pointing out that you don't need a full Flux implementation to get the benefits of going sideways to an action module: https://github.com/ryanflorence/react-training/blob/gh-pages...
526.
▲
by
insin
12y ago
I'm in the middle of the most productive streak I've ever had working on pet projects, using a combination of an IDEAS.md file and the GitHub contributions calendar. IDEAS.md is always the leftmost tab in my Sublime workspace. Eve
527.
▲
by
insin
12y ago
It's ES6 shorthand literal syntax [1], equivalent to: module.exports = { route: route, routes: routes }; [1] http://ariya.ofilabs.com/2013/02/es6-and-object-literal-prop...
528.
▲
by
insin
12y ago
The XML-like syntax is just less work, mentally and physically: no need for commas between props, the props object and children, no need to carefully manage all those commas when editing, adding, deleting, moving and removing stuff later on
529.
▲
by
insin
12y ago
I tweaked React's JSX transformer to output Mithril-compatible code, so you don't have to deal with this sort of syntax: https://github.com/insin/msx Having done DOM building with nested function calls/a
530.
▲
by
insin
12y ago
Every function is published to npm as a module: https://www.npmjs.com/browse/keyword/lodash-modularized
531.
▲
by
insin
12y ago
There's a mixin proposal in the react-future repo: https://github.com/reactjs/react-future/blob/master/01%20-%2...
532.
▲
by
insin
12y ago
First I've heard of this too. Obviously "gwit" is pronounced as "jwit", right?
533.
▲
by
insin
12y ago
Toggling display of child components with an "if" attribute doesn't work if I change the expression to parent.component either - evaluating a component attribute declared in a parent in the context of the child is pretty surp
534.
▲
by
insin
12y ago
Seems like you'd have to include all possible components and toggle them based on a variable. It doesn't seem like you can apply an if attribute to a component directly - the second component here never disappears, but the first i
535.
▲
by
insin
12y ago
I did a quick tweak of React's JSX transpiler to output mithril-compatible code [1], as the above was the sort of syntax I was using JSX to get away from! return <html> <body> <input> <b
536.
▲
by
insin
12y ago
It looks like this could make use of React's context feature once #2112 [1] lands. I have similarish form components [2] which need to do this the hacky way in the meantime (cloning [3] their children in order to pass the form prop the
537.
▲
by
insin
12y ago
Alt+F4 or "the X button", shurely? (I'd probably answer with HTAs - handy, compact way to distribute small JS-based tools/apps if you work in a Windows-based office and can eat the IE9 restrictions)
538.
▲
by
insin
12y ago
Do you have some example use cases for your form descendants vs. event bindings issues? I'd like to see how they could possibly map to React form libraries.
539.
▲
by
insin
12y ago
And one thread saying exactly what I was thinking.
540.
▲
An Unconventional Review of AngularJS
(letscodejavascript.com)
8 points
by
insin
12y ago
|
0 comments
More ›