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)
This is what happens when you only test your web app in super fast internet on a maxed out MacBook using Chrome.
Blueprint – A React UI toolkit for the web
171–180 of 214 posts
Re: Blueprint – A React UI toolkit for the web
#172Not 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.
Re: Blueprint – A React UI toolkit for the web
#173Hi 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
#174Not 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)
Re: Blueprint – A React UI toolkit for the web
#175Re: Blueprint – A React UI toolkit for the web
#176I saw no favicon and closed this thing immediately. Seriously guys, it's 2016 and you still don't have a favicon. Not having a favicon on your docs page is plain bad for a few reasons: 1. I have zero context about your page. If I don't have that 20x20 square on my tab anchoring me to reality, my 2 second attention span will have made me forget where I am even before I load your page on my internet-connected toaster o…
This is the sort of knee-jerk dismissal that the Show HN guidelines ask you to avoid when commenting here:
https://news.ycombinator.com/showhn.html
Favicons have their importance but it's just rude to swipe someone's entire work off the table this way.
Edit: Doh. Carry on.
Re: Blueprint – A React UI toolkit for the web
#177Safe to say it sux.
Re: Blueprint – A React UI toolkit for the web
#178Earlier 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…
I know everyone has their own favorite method, but one that I'm extremely satisfied with is using webpack > sass-loader > extract-text[1] to `include Styles from './MyComponent.scss'` in each component file, and then it all gets bundled up into a single css file per target (also great for eliminating dead CSS!). I use "layouts" at the root of my react hierarchy (under stores and routers and whatnot) and put my global…
Re: Blueprint – A React UI toolkit for the web
#179I saw no favicon and closed this thing immediately. Seriously guys, it's 2016 and you still don't have a favicon. Not having a favicon on your docs page is plain bad for a few reasons: 1. I have zero context about your page. If I don't have that 20x20 square on my tab anchoring me to reality, my 2 second attention span will have made me forget where I am even before I load your page on my internet-connected toaster o…
> I saw no favicon and closed this thing immediately. Seriously guys, it's 2016 and you still don't have a favicon. This is the sort of knee-jerk dismissal that the Show HN guidelines ask you to avoid when commenting here: https://news.ycombinator.com/showhn.html Favicons have their importance but it's just rude to swipe someone's entire work off the table this way. Edit: Doh. Carry on.
https://news.ycombinator.com/item?id=9238739
I'd agree that pokebowl's comment is a suboptimal way of getting that point across.
Re: Blueprint – A React UI toolkit for the web
#180Earlier quoted context omitted.
> I saw no favicon and closed this thing immediately. Seriously guys, it's 2016 and you still don't have a favicon. This is the sort of knee-jerk dismissal that the Show HN guidelines ask you to avoid when commenting here: https://news.ycombinator.com/showhn.html Favicons have their importance but it's just rude to swipe someone's entire work off the table this way. Edit: Doh. Carry on.
I mean, it's obviously satire, and it's taking a shot at something you've previously said is damaging to HN. https://news.ycombinator.com/item?id=9238739 I'd agree that pokebowl's comment is a suboptimal way of getting that point across.
Oops. I completely missed that.
This is what comes of moderating in haste.