Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Blueprint – A React UI toolkit for the web

blueprintjs.com

Post reply on HN
Print view View original

121–130 of 214 posts

Re: Blueprint – A React UI toolkit for the web

#121

Post by jasonkillian »

caleblloyd wrote: post #110
jasonkillian wrote: post #105

Earlier quoted context omitted.

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

That's the right place to see examples - sorry that it doesn't work well on mobile yet.

Just as a caution though, the library, in general, is intended for desktop web applications. We haven't made mobile-compatibility a priority, although at the very least, yes, we would like the docs site to be at least usable on mobile!

Re: Blueprint – A React UI toolkit for the web

#122

Post by pointytrees »

jasonkillian wrote: post #105
boubiyeah wrote: post #99

Earlier 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.

"Feel free to make a PR."

This makes me cringe. Sure, encourage us to make a PR to implement a tri-state radio button if it doesn't exist. Don't encourage us to make a pull request to reduce a 10 second documentation page load time.

Re: Blueprint – A React UI toolkit for the web

#123

Post by bluejekyll »

Klathmon wrote: post #46
renke1 wrote: post #35

This looks really nice. However, what I really want for React is a style-agnostic component library that basically extends the regular set of HTML elements, but comes with no "visual" styling (other than really basic styling like the browser's default styling for , and the like). Only styling that is necessary for the component to function should be included. Of course, optional themes would be fine. Also, non-visual…

Styling is still "unsolved" with react IMO. Inline styles feel wrong, CSS alone isn't encapsulated enough to work with components correctly, CSS modules are TOO encapsulated which makes global styles and themes a royal pain, and adding another layer ala SASS or LESS feels like more of a "patch" vs a real solution. And none of them really solve style inheritance in any way that I'd call elegant. I end up using SASS an…

Yes, thank you. This has been my biggest problem with React as well. It feels like they are fighting against some of the most natural ways to use CSS in code. Which is too bad, b/c CSS is awesome, and React is awesome. But together it feels like they don't play well.

Re: Blueprint – A React UI toolkit for the web

#124

Post by lucideer »

jasonkillian wrote: post #105
boubiyeah wrote: post #99

Earlier 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 think given the gp, this is quite a perfect reply. 4.2mb of js on a text-oriented docs page is either an infrastructural problem or it's by design. Dismissing it casually as something that can be considered a simple "issue" solvable with a PR or two seems a pretty clear sign of "people who don't see performance problems".

I appreciate that it's open source, so inviting PRs and general contributions is cool, but there does seem a bit of a dearth in understanding of the problem.

Re: Blueprint – A React UI toolkit for the web

#125

Post by wickedjust »

caleblloyd wrote: post #110
jasonkillian wrote: post #105

Earlier quoted context omitted.

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

iPhone safari doesn't show the docs overview page in view (cropped pretty bad) + can't scroll the page at all.

Re: Blueprint – A React UI toolkit for the web

#126

Post by nthnclrk »

foo303 wrote: post #54

Not 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)

Just to add another anecdotal experience:

Performance is 100% acceptable and fluid on an iPhone 7 in Safari.

Re: Blueprint – A React UI toolkit for the web

#127

Post by Kiro »

revelation wrote: post #42
ggregoire wrote: post #33

Earlier quoted context omitted.

What are you talking about? - bootstrap contains a grid layout - semantic-ui contains a grid layout - bulma contains a grid layout - purecss contains a grid layout - tachyon contains a grid layout - skeleton contains a grid layout - milligram contains a grid layout - spectre contains a grid layout and the list goes on.

That's nice but their idea of grid is to hand you a bunch of fixed-sizes CSS you can slap on elements. That has very little to do with the actual layouting a UI toolkit like Qt provides for.

I don't know anything about Qt but if it's so good, why hasn't someone made something equivalent for web that just generates the underlying HTML/CSS?

Re: Blueprint – A React UI toolkit for the web

#128

Post by WhitneyLand »

Since you guys are taking a lot of insults here I want to try and offer you something constructive.

Having bugs is ok. Failing at mobile and performance is not. It melts away your credibility because doing these things right is table stakes.

This is all compounded by the fact that it's a toolkit that serves as base for other developers, rather than just a slow app.

Finally, your flippant response to criticism gives the impression that you don't understand or care about craftsmanship.

However, thanks for making the contribution. Look forward to trying your next major release.

Post reply on HN