Live data from Hacker News

Blueprint – A React UI toolkit for the web

blueprintjs.com

161–170 of 214 posts

Re: Blueprint – A React UI toolkit for the web

#161
I 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 oven's 7 segment display. Not. Cool.

2. No support for 7 segment or e-ink displays. WTF?? How am I supposed to use this for IoT applications, like my toaster oven[1] or my dishwasher.

3. This is how it shows up on my kindle: http://67.media.tumblr.com/tumblr_lhw2rvgsnu1qzhofn.jpg ARE YOU INCOMPETENT??

[1] See bullet point 1

[2] https://static.googleusercontent.com/media/research.google.c...

[3] http://jepsen.io/

[4] https://palantir.com/spying-on-my-shit

Re: Blueprint – A React UI toolkit for the web

#162
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…

[deleted]

Re: Blueprint – A React UI toolkit for the web

#163
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…

> "Styling is still "unsolved" with react IMO."

How about this simple way to decouple styling from components using CSS Modules (no inline styles needed):

  components/
  |__FooComp/
     |__FooComp.jsx
     |__FooComp.css
  css/
  |__components/
     |__FooComp/
        |__styleOne.css
        |__styleTwo.css
        |...

FooComp.css contains only the very basic formatting for the component which is needed for displaying it correctly out of the box. No styling/theming, just some raw universal formatting/structuring (if necessary at all). FooComp.jsx loads and applies FooComp.css internally using CSS Modules like this:

Inside FooComp.jsx:

  import defaultClasses from './FooComp.css';

  const FooComp = props => (
    
      
    
  );

  export default FooComp;
styleOne.css and styleTwo.css contain different (external) styles for FooComp. Now if you need to use FooComp with an external style you load both FooComp.jsx and the external style (again, using CSS Modules to load and apply the styles):

  import FooComp from 'components/FooComp/FooComp';
  import FooComp$styleOne from 'css/components/FooComp/styleOne.css';
and put them together like this:

  
This way you can easily use the same component with different styles.

> "CSS modules are TOO encapsulated which makes global styles and themes a royal pain"

You can still use:

  @import '../someGlobals.css';
or:

  .someClass { 
    composes: anotherClass from "./someFile.css";
    color: green;
  }
or:

  .someClass { 
    @apply --anotherClass;
    color: green;
  }
or:

  .someClass {
    background: var(--brandPrimary);
    color: green;
  }
or ...

There are plenty of options especially with PostCSS.

Re: Blueprint – A React UI toolkit for the web

#164

Earlier quoted context omitted.

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.

Perhaps it's a CSS issue. I've just noticed that when working only with CSS adding and removing classes in JS it's simple. All of the React frameworks feel like they don't meld well with that.

I will not claim to be a JS expert by any means. In my basic usage of HTML, JS and CSS; I find that I can manipulate the look and feel easier with Jquery. When I add in React, I get a really elegant MVC system, but loose the ease of adding and removing classes of different HTML elements.

Maybe I'm doing it wrong, but that's just my experience.

Re: Blueprint – A React UI toolkit for the web

#166
post #138

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.

I still can't imagine tying yourself to a system that precludes mobile. That seems like a terribly bad idea at this point.

Re: Blueprint – A React UI toolkit for the web

#167
Maybe I need to take a few layers of tinfoil off the old hat, and I suspect it's just good old fashioned open source generosity, but..

Given that it's from Palantir, is there any way this could become a security attack vector at scale?

Re: Blueprint – A React UI toolkit for the web

#168
post #167

Maybe I need to take a few layers of tinfoil off the old hat, and I suspect it's just good old fashioned open source generosity, but.. Given that it's from Palantir, is there any way this could become a security attack vector at scale?

Fortunately, it's open source, fully open to code review!

Re: Blueprint – A React UI toolkit for the web

#169

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.

"I agree that HN and other devs will be ruthless when it comes to perf." hahaha

The funny thing is, so many people don't seem to realise that ordinary end-users will be, too. End-users care about performance. Not all of them necessarily understand that what they care about is performance, but it all contributes to the experience. Even back I need the 90s there was much statistical evidence that the slower a website was, the lower engagement it received.

Re: Blueprint – A React UI toolkit for the web

#170

Earlier quoted context omitted.

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.

Even now, it's still pretty sluggish, all around. My machine is, I think, as big as can be expected (current gen i7, 16GB), though I am on a slow 4G network. But, as others note, it is gorgeous, and the API appears well thought-out, and very complete (or, at least, complete for the kinds of systems UIs I build).

Weird, because on my iPhone 6, it works fine with no detectable performance issues at all.
Post reply on HN