Maybe just me but I'm having a hard time seeing how this is substantially different from or better than bootstrap or foundation with some react-based wrappers like reactstrap. Seems like performance is an issue and you're just as tightly coupled to the framework as with bootstrap/foundation. Am I missing something?
Blueprint – A React UI toolkit for the web
101–110 of 214 posts
Re: Blueprint – A React UI toolkit for the web
#102Earlier quoted context omitted.
I saw this[1] recently by one of the guys from material-ui[2]. They're going to move to JSS. [1] https://github.com/oliviertassinari/a-journey-toward-better-... [2] http://www.material-ui.com/
I really like material-ui but am constantly bummed about their use of inline styles. Each component has multiple style props, lest you resort to "div > div > div:nth-child(2)" in your own CSS. Each "style" prop now has to be diffed by React too. Doing things like hover on mouse/touch events seems like it will never be as efficient as using ":hover". And when doing universal rendering, the amount of markup you send is…
We just wrote all our own inline styles to override their stuff. It turned out to be not that bad. We just set up a context object like theirs, and wrapped all the components we used.
Re: Blueprint – A React UI toolkit for the web
#103Very impressive! Keep up the good work.
Re: Blueprint – A React UI toolkit for the web
#104Earlier quoted context omitted.
React is supposed to be the "next big thing" and yet styling is still an unsolved problem. I'm amazed by the state of our tooling in front end web development.
I know it's fun to scoff at "those front end guys" and act like you know all the answers, but if you do know the "one true solution" to this please tell us. It's "unsolved" in the sense that all the current solutions feel wrong (but work great), and if that's the biggest problem front-end development currently has, then it's in a pretty damn good place.
I really don't know the answer. I'm a front end guy too.
But it just seems like we are all stuck on this collective transe of needlessly complicated, overly fashionable tools that struggle with the basics.
From what I've seen (granted, not much), animation and styling look like an after thought, which is surprising. But I'm weird, I still write bare CSS to this day whenever the decision is up to me. SASS is cool, but not enough to justify adding another lever to the machine, IMO.
Re: Blueprint – A React UI toolkit for the web
#105Not to sound like a bummer here, but I'm not sure what kind of computer is needed to open this webpage. Simply scrolling up and down that website causes my computer to almost freeze. Firefox 49.0 user here. I would profile it, but I'm afraid of having to restart the computer as a result. Edit: It looks amazing. (Still the performance issue is reproducible easily)
And the doc has 4.2MB of minified javascript. Jesus christ. Tooks 9 seconds to load the page. All credibility gone. Why would I use components made by people who don't see performance problems?
We're aware of this: https://github.com/palantir/blueprint/issues/39
Feel free to make a PR to improve things boubiyeah, we just haven't gotten to this issue yet.
Re: Blueprint – A React UI toolkit for the web
#106Re: Blueprint – A React UI toolkit for the web
#107Not to sound like a bummer here, but I'm not sure what kind of computer is needed to open this webpage. Simply scrolling up and down that website causes my computer to almost freeze. Firefox 49.0 user here. I would profile it, but I'm afraid of having to restart the computer as a result. Edit: It looks amazing. (Still the performance issue is reproducible easily)
There's an interactive animation in the header that really makes the page lag a lot when scrolling, spiking the GPU (look at the devtools, also scrolling is being tracked somehow) This is a common problem with landing pages that promote things. Developers should pay more attention to optimizing the main page that promotes the libraries in question, as it can turn down potential customers ;) I was looking at the other…
Although the docs don't seem to be responsive either.
Re: Blueprint – A React UI toolkit for the web
#108Earlier quoted context omitted.
And the doc has 4.2MB of minified javascript. Jesus christ. Tooks 9 seconds to load the page. All credibility gone. Why would I use components made by people who don't see performance problems?
We're aware of this: https://github.com/palantir/blueprint/issues/39 Feel free to make a PR to improve things boubiyeah, we just haven't gotten to this issue yet.
"I agree that HN and other devs will be ruthless when it comes to perf."
hahaha
Re: Blueprint – A React UI toolkit for the web
#109Not to sound like a bummer here, but I'm not sure what kind of computer is needed to open this webpage. Simply scrolling up and down that website causes my computer to almost freeze. Firefox 49.0 user here. I would profile it, but I'm afraid of having to restart the computer as a result. Edit: It looks amazing. (Still the performance issue is reproducible easily)
Works fine on my laptop in chrome on Linux. Perhaps it's using something that's less optimized in Firefox?
Re: Blueprint – A React UI toolkit for the web
#110Earlier quoted context omitted.
And the doc has 4.2MB of minified javascript. Jesus christ. Tooks 9 seconds to load the page. All credibility gone. Why would I use components made by people who don't see performance problems?
We're aware of this: https://github.com/palantir/blueprint/issues/39 Feel free to make a PR to improve things boubiyeah, we just haven't gotten to this issue yet.
Is there a demos section? Tried to load http://blueprintjs.com/docs/ on mobile (chrome and Firefox on Android), most of the page is cut out due to scrolling restrictions