mlsarecmg

57 ms·

91.
by mlsarecmg 8y ago
JSX gets transpiled, not parsed. The effort is completely on the tooling side, there's no loading effort that changes JSX into functions. The main difference between your two snippets is that one is declarative and the other is imperat
92.
by mlsarecmg 9y ago
Web components are a regression, though. There's nothing in the slightest that would make interop possible. They just wrap a shadow root, and within you are greeted with a naked dom again, which calls for a framework to drive it. Imagi
93.
Why React needed yet another animation library. Introducing: react-spring(medium.com)
3 points by mlsarecmg 9y ago|0 comments
94.
Show HN: Create effortless page transitions with a new primitive in react-spring
4 points by mlsarecmg 9y ago|0 comments
95.
Show HN: The state of animation in React, introducing react-spring
5 points by mlsarecmg 9y ago|0 comments
96.
by mlsarecmg 9y ago
I think you're confusing something. You don't "build" dependencies, you consume them as pre-built modules. As a package author you use whatever you want (rollup, webpack, gulp, grunt, ...), but you will most likely publi
97.
Contextual: global setState, tiny Redux-like store and declarative transforms(github.com)
1 points by mlsarecmg 9y ago|0 comments
98.
by mlsarecmg 9y ago
You mean, you do that? I don't get it otherwise. http://www.npmtrends.com/react-native-vs-weex-toolkit Native is hard, React needed years to get it even nearly right, and it did that with the community's backing.
99.
by mlsarecmg 9y ago
This is how we are doing it in webpack, i think rollup can alias as well: webpack.config.js alias: { three$: path.resolve('./three.js') } and a local copy of three.js // Only export the th
100.
by mlsarecmg 9y ago
const { for, class } = this.props Will crash. It's just a bit inconvenient (and inconsistent for beginners) having to write: const { for: forHtml, class: className } = this.props Some react-like libs do allow it, but
101.
by mlsarecmg 9y ago
Actually many traditions have had circles that retain and sublimate the seed, very interesting topic. See more here: https://gist.githubusercontent.com/drcmda/84456b58765cf83144...
102.
by mlsarecmg 9y ago
> If it was just html I could write <label for=""> and not <label htmlFor="">, I could write <div class=""> instead of <div className=""> for and class are reserved statemen
103.
by mlsarecmg 9y ago
Not just mobile apps: Windows: https://github.com/Microsoft/react-native-windows Macos: https://github.com/ptmt/react-native-macos Linux (Qt): https://github.com/status-im/rea
104.
by mlsarecmg 9y ago
The points you've listed are the very reasons why i would prefer React actually ... - JSX fixed all the templating issues from 10 years ago, i see no reason to go back to dependency injection, scope loss, arbitrary code-in-html expre
105.
by mlsarecmg 9y ago
Honestly that is like saying Windows Phone doesn't need the apps. React has a self sufficient cross platform eco system. I don't think people using primarily web frameworks even realize the implications of that yet. React works ou
106.
by mlsarecmg 9y ago
Github and Npm are both used in China all the same. I don't know about firewall restrictions, many chinese companies publish directly on Github. React is the most used in China in polls as well (stateofJS), with some of the biggest nam
107.
by mlsarecmg 9y ago
See it in context. The fastest growing framework on npm right now for instance is Preact (as per official report posted by Lauri Voss last week), but Preacts userbase is so small that it could grow hundredfold with insane growth rates perce
108.
by mlsarecmg 9y ago
This is a featherweight component: const A = () => <div>hi</div> const B = () => <A /> Polymer is everything but light, it is a huge abstraction. It ships a template engine parsing arbitrary sy
109.
by mlsarecmg 9y ago
Stars are pretty useless for what they wanted to measure. Real-world data paints a different picture http://www.npmtrends.com/angular-vs-react-vs-vue-vs-@angular... Even searching Github for 'import React from 're
110.
by mlsarecmg 9y ago
Polymer is one of the worst offenders when it comes to treating backwards compat seriously, worse than Angular even. We're testing frameworks on projects internally to get an idea, Polymer is going through the third full rewrite. That
111.
by mlsarecmg 9y ago
Apparently this isn't just two guys: https://twitter.com/rauchg/status/951185263698391040 Another interesting bit: https://www.reddit.com/r/javascript/comments/7phc5q/a_fas
112.
by mlsarecmg 9y ago
There have been drop in replacements for react+react-dom before, like inferno and preact. They all have claimed perf benefits, though benchmarks usually don't mean much. The size differences have been meaningful in the past though. If
113.
by mlsarecmg 9y ago
I have the prior version and the trackpad is terrible compared to my MBP. Like devastatingly bad. It feels so odd coming back to that computer being forced to use a mouse. Using it longer than a minute with that trackpad makes me loose pa
114.
by mlsarecmg 9y ago
I don't think there's anything more user unfriendly and annoying than pagination. Pull/click/scroll to load have been made to help it. But that aside, the list isn't important. It could be dialog items, complex tree
115.
by mlsarecmg 9y ago
The list is an example, the cheapest one to make it understandable. Let it be 2000, or 100, filtered and pre-processed. It would still take longer than the 15 the user actually sees. The point isn't the list, but the primitive. I don&#
116.
by mlsarecmg 9y ago
All template engines do. JSX doesn't get compiled but transpiled which makes all the difference. Therefore it works with the language, uses latest es-drafts without problems, is 100% typesafe as it can work with other supersets like TS
117.
by mlsarecmg 9y ago
You can boil down react to virtually nothing. preact-compat turns it into 4kb. Redux + router don't add that much. The loading impact, if you watch out, code split, isn't the dire problem. As for laggy experience, Fiber is the o
118.
by mlsarecmg 9y ago
Like typescript, flow or even es-next. An optional DSL that transpiles to pure javascript isn't an obstacle to programming. A string-template with an arbitrary syntax is an obstacle on the other hand.
119.
by mlsarecmg 9y ago
The whole point is the artificial slowdown. Taking it out makes it meaningless, it prints a few blue bubbles. Scheduling is and always will be the biggest bottleneck. It is that kind of innovation that keeps react relative. As for a lean do
120.
by mlsarecmg 9y ago
As much as i want to like it, i have troubles thinking of templates as something that questions the status-quo. The other big thing seems to be loading effort, but react has gotten so small (react+react-dom = 29kb, react+react-dom-lite 15kb

More ›