mlsarecmg

10 ms·

61.
by mlsarecmg 8y ago
I googled that, looks like an issue in FF: https://github.com/mrdoob/three.js/issues/9716 Basically i just channel through regular three without creating much of a dependency. If it doesn't work in react
62.
by mlsarecmg 8y ago
Glad to hear that. If you need anything, ping me on github, i'm open to add functionality.
63.
by mlsarecmg 8y ago
That would be one of the things i would love to explore. Does three do this automatically or is there something the app needs to specifically calculate?
64.
by mlsarecmg 8y ago
I ran it both in Chrome and Firefox, seems to be working. Could i bother you for error logs?
65.
by mlsarecmg 8y ago
This we had in place, but without react driving the scene we used manual Redux subscribes. Every change meant figuring out what part of the scene graph needed to be added/removed or changed. Basically the same problem one would face wi
66.
by mlsarecmg 8y ago
I just started a week ago, didn’t polyfill the demos, but will do it when i get around it, nothing in there that wouldn’t work in FF. Would be super happy for GH issues (for instance error logs).
67.
by mlsarecmg 8y ago
with managed i mean that the view is now merely a reflection of state. Basically just like with the dom: {condition && <div>hello</div>} The div is there as long as the condition is true. But of course it c
68.
by mlsarecmg 8y ago
Hey that's amazing, and your tool is really advanced! It's exactly the purpose of this, we're making a cad system as well and it's been hell with the current way of how we chose to do it. We're using redux and getti
69.
by mlsarecmg 8y ago
I do a lot of 3d stuff at my job, first openGL, then three, but it's too easy to make a mess with the inflating approach and unmanaged variables everywhere. I hope this will make a difference.
70.
by mlsarecmg 8y ago
PS. Full code for the demo: https://codesandbox.io/embed/ly0oxkp899
71.
Show HN: Mixing WebGL and HTML, Both Rendered Out in React(subdued-health.surge.sh)
129 points by mlsarecmg 8y ago|32 comments
72.
by mlsarecmg 8y ago
You would use them as you always did. You have raw access to everything. But if you want loading results to be managed, put them into useEffect/useMemo and render out the results. For instance i've just made a text-sprite componen
73.
by mlsarecmg 8y ago
Would help in the same way that react-dom helps the dom, especially performance. React basically manages the scene, only updating the parts that change. As for processor speed, React only mounts/unmounts, it maintains THREEs performanc
74.
Show HN: Three and React = react-three-fiber, a new renderer based on Fiber(github.com)
15 points by mlsarecmg 8y ago|4 comments
75.
by mlsarecmg 8y ago
JSX is a dsl, like typescript or flow, it doesn’t change or affect your code, all assumptions stand, it doesn’t break scope. Vue templates are not a dsl , they break all assumptions and your scope. There is no difference between Vue and an
76.
by mlsarecmg 8y ago
Hocs had several problems, they couldn't access context, re-using one result in another is hard, they create a new component for every thing you want to do, etc. Take this example for instance: https://codesandbox.io/em
77.
by mlsarecmg 8y ago
Here's something that Swizec Teller wrote after having to use it on a project: https://medium.com/@swizec/some-thoughts-on-vue-after-deploy... In essence, many things you take for granted do become harder because
78.
by mlsarecmg 8y ago
You style components in React like you always did before. That's the whole thing about it, it never changes what you know. ... Unless you decide using a more modern approach like styled-components et al.
79.
by mlsarecmg 8y ago
Nah, this has nothing to do with that. If you pass an anonymous fn to a pure-component its shouldComponentUpdate part flags it for re-rendering since the property is new every time, which can be a problem depending on how large its payload
80.
by mlsarecmg 8y ago
This one was pretty good and goes into deeper details instead of just claiming x is better than y: https://medium.com/@swizec/some-thoughts-on-vue-after-deploy... The fundamental difference between React and Vue is vis
81.
by mlsarecmg 8y ago
Well i give you that, css is what it is, but even with basic css knowledge, making a dropdown appear anywhere you want is not hard: https://codesandbox.io/embed/w7499vxrzk It could be better, but it's even got a p
82.
by mlsarecmg 8y ago
Xaml and Wpf? Qt? I am honestly asking you, have you worked with React before? XAML has a learning curve of 2 years and more to get to expert level. I developed with it for more or less 5 years and i still have nightmares. Qt and the others
83.
by mlsarecmg 8y ago
The view and the presentational code that builds it are one, they belong to the same presentational layer and always have been. To artificially separate them was a major mistake of the old paradigm. Older approaches, like Knockout, Angular,
84.
React-spring goes universal: animate anything on any platform(twitter.com)
2 points by mlsarecmg 8y ago|0 comments
85.
by mlsarecmg 8y ago
It just doesn't look comparable to the example i've posted. They were really, really simple, so if QT is the same, i would love to see it do the same. As for imperative registration, didn't you just link me to it? If they wer
86.
by mlsarecmg 8y ago
And that is what i suspected and what i've seen in all examples i have browsed through so far. The enabled prop wasn't the point, it demonstrates functional composition. All of the above uses old, traditional layout inflating, dep
87.
by mlsarecmg 8y ago
From what i've seen this is layout inflating, you have a template and you fill it imperatively. Which would be one of the oldest paradigms we have. Maybe i am getting this completely wrong, forgive me in that case, but in all examples
88.
by mlsarecmg 8y ago
This seems like a misunderstanding of what React is. JSX is not a template. It is a DSL or superset with direct access to the presentational layer. It gets "transpiled" away in the building phase. React components are not imperati
89.
by mlsarecmg 8y ago
XAML is a template, JSX is a DSL. A template kills scope, duplicates coding semantics, messes up app flow with bindings and needs dependency injection to get local scope back - all of this has been solved with JSX, which now pretty much ful
90.
by mlsarecmg 8y ago
The transpiler is a build build (a babel plugin), it isn't even a part of the application nor does it run while loading. The snippet above turns into a bunch of nested functions.

More ›