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

151–160 of 214 posts

Re: Blueprint – A React UI toolkit for the web

#151

Post by obituary_latte »

jasonkillian wrote: post #121
caleblloyd wrote: post #110

Earlier quoted context omitted.

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!

The meta viewport is breaking the docs site.

    var gt = document.getElementsByTagName('meta');gt[3].content='';
Fixes it for those in a rush to see it. There is a "view source" app in the AppStore that allows you to inject js.

Re: Blueprint – A React UI toolkit for the web

#152

Post by realusername »

adidahiya wrote: post #120
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)

Hi folks, I'm one of the developers of this project -- we hear your perf concerns loud and clear and are tracking the issues :) As mentioned elsewhere in this thread, this page was released a little too early while we were still playing around with animations in the header. I've gone ahead and disabled them for now, so you should see leaner CPU utilization now. Thanks for your comments.

There still seems to be some display issues on the header, this is how it looks like on my phone: http://oi64.tinypic.com/125miwj.jpg (and it's blinking).

Re: Blueprint – A React UI toolkit for the web

#153

Post by rpwverheij »

This looks really nice and well set up. I love the fact that you chose typescript and bundle a good definitions file. I totally understand homepage performance was not on the agenda yet, and its really no big deal to me, but I have to agree with others on the mobile support: this sadly crosses blueprint of my list for 99% of my work, if not all. Will be coming back to see where to project is going though!

Re: Blueprint – A React UI toolkit for the web

#154

Post by boubiyeah »

bluejekyll wrote: post #123
Klathmon wrote: post #46

Earlier quoted context omitted.

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.

Why? They actually can play well, at least, just as well as standard HTML + CSS.

It's just that people are now trying to componentize everything, including styles, so it's a new requirement we didn't have before. Put another way, one could say that now that we have a good solution for client side rendering, we then turned to good old global, cascading, hard to maintain CSS to try and fix that guy next.

Re: Blueprint – A React UI toolkit for the web

#155

Post by serb348 »

minimaxir wrote: post #135
TheAceOfHearts wrote: post #87

I see a few comments bringing up mobile. There's already many mobile-friendly UI frameworks; not everything has to be mobile-first. Yes, in many cases it makes sense to go for a mobile-first approach, especially with consumer-facing applications. Mobile is huge and apparently it's still continuing to grow. At the same time, there's many legitimate cases in which you want to optimize for desktop. For example: consider…

For internal projects/webpages (similar to Google Data Studio as mentioned), where you would expect the user to only be using it on a desktop, having no mobile support is fine. But for external projects/webpages in 2016, where atleast 1/3 of usage can come from mobile devices, having a lack of mobile support is a complete, 100% nonstarter. And there are plenty of competing React UI frameworks with mobile support alre…

Such As?

Re: Blueprint – A React UI toolkit for the web

#156

Post by godDLL »

CSDude wrote: post #138
WhitneyLand wrote: post #128

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 t…

Not all things are supposed to be mobile. All the products we write are supposed to run on a large display for our case.

That might be so, but the rest of the world cares deeply about mobile, even to the point of caring about mobile first. You should get onboard.

Re: Blueprint – A React UI toolkit for the web

#157

Post by ergo14 »

Fifer82 wrote: post #118
xliiv wrote: post #30

Earlier quoted context omitted.

+1 for web components and Polymer https://beta.webcomponents.org/

A lot of people go on about Polymer, but no one actually uses it?

Hm, some of the biggest enterprises in the world and industry leaders use it.

I'm not sure why this is repeated on HN all over and over.

https://youtu.be/VBbejeKHrjg?t=9m32s

Re: Blueprint – A React UI toolkit for the web

#158

Post by impostervt »

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)

I opened the page and noticed my brand-new laptops fans started screaming. Open Top -> FF is at 106% of CPU. Wth?

Re: Blueprint – A React UI toolkit for the web

#159

Post by literallycancer »

jasonkillian wrote: post #75

Hi all, I work at Palantir and worked on Blueprint (although I'm currently working on a different project). Happy to answer any questions you have about it. Just a note - we didn't intend to heavily publicize the project quite yet. For example, the docs site is still a WIP, so apologies if it causes issues for you on mobile devices.

Just a nitpick, but when looking at the docs, I can't move with Page Up/Page Down unless I click in the "content column/area", kind of annoying when one navigates using the left bar and then can't move around (on no-mouse setups, e.g. trackpoint + keyboard). So you might want to look at that.

Otherwise no issues (older laptop i5/chrome), so I guess you guys mostly fixed that by now.

Re: Blueprint – A React UI toolkit for the web

#160

Post by meowface »

adidahiya wrote: post #120
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)

Hi folks, I'm one of the developers of this project -- we hear your perf concerns loud and clear and are tracking the issues :) As mentioned elsewhere in this thread, this page was released a little too early while we were still playing around with animations in the header. I've gone ahead and disabled them for now, so you should see leaner CPU utilization now. Thanks for your comments.

Looks like a great project, but the landing page is still very scroll-sluggish for me on a 2015 MBP with Chrome.
Post reply on HN