daveidol

26 ms·

271.
by daveidol 8y ago
Definitely agree, but I think the parent commenter was asking how to reuse redux-specific code, such as reducers, actions, etc.
272.
by daveidol 8y ago
Reducer, middleware, and "action creator" factories that take config will allow for a pretty high level of reusability. We have several internal redux libraries of generic reducers, middleware, etc. and they all export factories
273.
by daveidol 9y ago
Powerful for doing all the things one does on Snapchat? The point is it's a UX for power users (limited discoverability, but faster than a traditional button/modal based UI once you know it). I think it's a fair comparison.
274.
by daveidol 9y ago
What is a 'selfie app'? Is Facebook a 'selfie app'? What about Instagram?
275.
by daveidol 10y ago
Have you seen some of the things we are building for the web these days? Full applications, with multiple "pages", server-side rendering above the fold content, minified builds that load not only content--but code as well--on dema
276.
by daveidol 10y ago
I wrote a similar program in plain Java + Swing (and no other libraries) years ago, which I dumped on GitHub here (there are a few screenshots): https://github.com/idolize/ray-tracer
277.
by daveidol 11y ago
If you quit the app with the menu button then it is quit completely. Essentially, the "home" functionality works just like on iOS or Android. You're right that it is not always intuitive in situations when an app is hanging&#
278.
by daveidol 11y ago
Would you recommend a service other than email then? Which one?
279.
by daveidol 11y ago
Hyperscript is the same thing as JSX when used with React; just a different syntax. Either way you are "mixing markup and code."
280.
by daveidol 11y ago
Yes, they really are. Read the "Message Deletion and Retention" section: https://www.snapchat.com/privacy
281.
by daveidol 11y ago
You're not wrong: things do change quickly in the JavaScript world. But have you actually been following this stuff very closely? "Flux" was never a "well-known default," because there was no single "Flux"
282.
by daveidol 11y ago
Hey Ray! Glad to see the GWT team is still making strides :)
283.
by daveidol 11y ago
I mean... true. The title is a little click-baity perhaps (even though it is a direct quote), and this phenomenon of people reading a title/skimming an article and then spreading around inaccurate information is frustrating. But, I act
284.
by daveidol 11y ago
The first time I heard of async/await was actually with Microsoft C#; so I'm not too surprised to see them prioritize this feature in JS land. ...which is cool, because using async/await in C# made me realize how much simpler
285.
by daveidol 11y ago
Thanks for this! Very cool idea. I haven't looked closely enough - do you pre-render the pages somehow to maintain SEO?
286.
by daveidol 11y ago
If I understand spicyj correctly, I think he's saying in v0.14 a ref of React.DOM will now be the raw DOM node; but it will also contain a getDOMNode method (which just returns itself) in order to continue working for people expectin
287.
by daveidol 11y ago
You guys are the best :)
288.
by daveidol 11y ago
I'm very excited about this release! Question for other React devs out there: how long would you typically expect it to be before we can start migrating over? Will older React components designed for 0.13 still work if they don't
289.
by daveidol 11y ago
Awesome writeup! Sure, it's easier to setup your own web presence with "the cloud" today than it used to be, but this only further centralizes control of content to the big cloud providers. Not to mention the cost of bandwidt
290.
by daveidol 11y ago
I enjoyed it. The entire talk isn't about the history of open source - he eventually gets into issues about maintaining open source in modern day on GitHub.
291.
by daveidol 11y ago
Agreed - this is awesome! Also, if you didn't catch it, there appears to be a full web example using this library (as well as websockets) here: https://github.com/citronneur/mstsc.js
292.
by daveidol 11y ago
Great post- thanks for the writeup! I would love to see a post detailing some best practices, or even comprehensive setup guides, for instrumenting a full Node.js service. So far most of the information I've seen is very limited in sco
293.
by daveidol 12y ago
Agreed. I ditched iPhoto and switched to Unbound ( http://unboundformac.com/ ) a while back for this reason.
294.
by daveidol 12y ago
I would really love to see some code snippets with the example mentioned (or ideally an open source project).
295.
by daveidol 12y ago
Thanks for the suggestions. I've looked at immutable data structure libs some, but I haven't seen any real comprehensive examples showing the behavior you describe within the Flux pattern. Do you happen to know of any such example
296.
by daveidol 12y ago
One thing I would love to see some guidance on with Flux (and potentially with the patterns expressed in Marty.js) is how to handle the use case of Stores for a collection of items as well as a single item. Right now, if I create a Store fo
297.
by daveidol 12y ago
"I'm starting to think that it is easier not to track changes/state for forms anywhere if it can be avoided, and to basically extract all of the values out of the form manually via the DOM whenever they are needed" Can y
298.
by daveidol 12y ago
So how does this compare to actually using React/Flux? It looks like all the virtual DOM stuff no longer exists, which seems to me like you would lose a lot of the niceties of React. Why not just use the actual Flux architecture with B
299.
by daveidol 13y ago
What if someone has their smartphone out at the restaurant? Are they asked to put it away or leave for fear of everyone's privacy? Just because someone is wearing Glass doesn't mean they are constantly shooting photos you know...
300.
by daveidol 13y ago
You guys finished it! Come a long way since the FB hackathon. P.S. Love the title

More ›