sebmarkbage

7 ms·

1.
by sebmarkbage 5y ago
My work seems to have made you angry which makes me sad. You’ll at least be happy to learn that useEffect will be sync if the render itself was sync in React 18. Ofc if you do an async render those effects won’t work anyway and you need to
2.
by sebmarkbage 8y ago
I think this misses the point of what a senior developer is. Nobody builds a huge thing by themselves better than multiple people can. Being a senior developer is enabling a few other people to do their best work.
3.
by sebmarkbage 9y ago
Not quite. This PR is almost ready to do it. https://github.com/facebook/prepack/pull/397 Currently it is blocked on Map/Set support in the output which is an outstanding issue. We could also try it with
4.
by sebmarkbage 10y ago
(I'm "Sebastian".) It meant to read C. It definitely wasn't C++. However, now I'm curious if I'm confusing it with the later Amiga games. I'll need to look into this. I was 8 years old at the time. :) Note
5.
by sebmarkbage 10y ago
Yea, this is clearly not enough to be a standard but we don't really know of a standard for this and it is not really our primary expertise. If Sentry or others that understand this problem space better create a standard format, we wou
6.
by sebmarkbage 10y ago
If it spread to a become a defacto standard format, wouldn't that be a good thing? That way you only have to deal with this once and it will work everywhere. At that time, the size/parse time will have much greater impact because
7.
by sebmarkbage 10y ago
Parse time is the new bottleneck of modern client-side web apps. Of course React on its own isn't going to move the needle but if other libraries follow along it just might. With better, more expressive error messages without paying th
8.
by sebmarkbage 11y ago
Note that the stateless part is mostly just a stepping stone to a stateful variant. https://github.com/reactjs/react-future/tree/master/07%20-%2...
9.
by sebmarkbage 12y ago
React.DOM is still in 0.13.
10.
by sebmarkbage 12y ago
The point of this is exactly to reduce the library size AND getting to a stable 1.0 release. By making the class system optional, it becomes an optional dependency which reduces the library size. Supporting only createClass in a stable 1.0
11.
by sebmarkbage 12y ago
This is actually a way to eventually reduce the size of the library since it makes the class system optional. We're definitely considering optional module based systems instead of OOP, but it's still too early. https://
12.
by sebmarkbage 12y ago
This is actually an anti-pattern that we're explicitly trying to get rid of. The fewer components you have, the fewer optimization hooks you have. This also have subtle changes in semantics, and disables local optimizations in the cons
13.
by sebmarkbage 12y ago
Yea, note that mithril is on that list. The syntax was where people unified. There wasn't agreement on semantics and this is moving closer to that. It's possible that this will eventually unify again. E.g. around a replacement for
14.
by sebmarkbage 12y ago
In CoffeeScript it might look something like this: element = type: 'div' props: className: 'container', children: [ type: 'span', props: className: 'foo' type: CustomClass, props: classNa
15.
by sebmarkbage 12y ago
Hi, this was a tough call for us to make. We wanted to everything we could to avoid extra bloat for everyone. In the end, most people tend to use some kind of extra helper, even if it's not JSX. E.g. a custom library or another third p
16.
The Design Philosophy Behind React – Minimal API Surface Area(2014.jsconf.eu)
3 points by sebmarkbage 12y ago|0 comments
17.
by sebmarkbage 12y ago
The difference is that if you use Object.observe to track changes, then you don't have the ability to hold onto the previous version of an object and know what the old value was. This is important for animations where you want to anima
18.
React Developer Tools, a Chrome Extension for debugging React JS Components(facebook.github.io)
35 points by sebmarkbage 13y ago|1 comments
19.
by sebmarkbage 13y ago
We have a tool that does Canvas drawing from React too. Currently some pieces are cached in retained mode but it's just an implementation detail for certain performance characteristics. https://github.com/facebook/
20.
by sebmarkbage 13y ago
React exposes event handlers and setState methods which are seemly mutable and Object Oriented. This is because React is designed for large scale organizations and to be approachable by a broad developer base. However, once you have certain
21.
by sebmarkbage 13y ago
React does the diffing on the output (which is a known serializable format, DOM attributes). This means that the source data can be of any format. It can be immutable data structures and state inside of closures. The Angular model doesn&#x2
22.
by sebmarkbage 13y ago
Consider the architectural difference of React vs. one of the similar "view model" frameworks. It's similar to the difference between Git vs. SVN. Other view model frameworks typically track all changes to the view model by explicitly firin
23.
by sebmarkbage 14y ago
Here's an implementation in WebGL http://blog.calyptus.eu/seb/2010/11/webgl-not-just-for-3d/