HN user

nik-graf

144 karma

Passionate about Software Architecture, UX, Skiing & Cycling.

https://twitter.com/nikgraf https://github.com/nikgraf

Posts17
Comments17
View on HN
news.ycombinator.com 5y ago

Show HN: End-to-end encrypted notes app

nik-graf
6pts0
nikgraf.github.io 6y ago

Show HN: GraphiQL Spark – allowing you to demo a schema without an endpoint

nik-graf
3pts0
egghead.io 8y ago

Leverage New Features of React 16 – free 17min Egghead video course

nik-graf
1pts0
nikgraf.github.io 9y ago

Show HN: Star Wars opening craw built with React VR

nik-graf
2pts0
github.com 9y ago

Serverless private npm registry using AWS Lambda and S3

nik-graf
1pts0
github.com 9y ago

A collection of ReactVR experiments

nik-graf
57pts6
medium.com 9y ago

How to run a Meetup – Lessons learned running React Vienna for a year

nik-graf
96pts17
www.facebook.com 10y ago

You Can’t Make a Billion Dollars with Your Startup (Kent Beck)

nik-graf
1pts0
github.com 10y ago

Show HN: DraftJS Plugins: Slack-Like Emojis, FB-Like Mentions and Stickers (Web)

nik-graf
15pts2
nikgraf.github.io 11y ago

Show HN: Belle – Configurable React Components with Great UX

nik-graf
54pts12
medium.com 11y ago

Stories and lessons learned from Partners and Founders at YC (Startup School Europe)

nik-graf
7pts1
medium.com 12y ago

How to re-issue a SSL Certificate for App Engine (with RapidSSL)

nik-graf
1pts0
medium.com 12y ago

App Engine and Heartbleed

nik-graf
1pts0
medium.com 12y ago

How to speed up your Development Process with Minimum Marketable Features

nik-graf
1pts0
www.meetup.com 12y ago

Event: Hacking with Dart Experts in SF on tomorrow

nik-graf
2pts1
www.nikgraf.com 13y ago

Getting Started with Polymer.dart

nik-graf
1pts0
www.nikgraf.com 13y ago

JavaScript Error Logging in Minutes

nik-graf
30pts12

I have met skidding last February when this was project was in its early stages. We walked through Cosmos and it definitely was an inspiration to Carte blanche. Skidding even helped us to design the initial props form: https://github.com/carteb/carte-blanche/issues/47

Cosmos in my opinion is a fantastic tool and covers even some areas we haven't touch yet, but planning to do soon like injecting/manipulating the internal state of a component.

While there a many more differences these are probably the most interesting ones:

- The core of Carte blanche is a Webpack plugin. By hooking into the main compilation of Webpack Carte blanche can identify your components and list them in an application living within your running server on different URL path. The coolest part from my perspective is that we inherit all your webpack settings by default. No need to configure your loaders. Cosmos in comparison is a separate app.

- In Cosmos your need to write your examples by hand. Carte blanche reads out your propTypes/Flow types and allows us to generate a form input for each of your properties including nested structures like a person object containing an avatarUrl, firstName & lastName. This approach allowed us to create some kind of UI fuzz-testing feature in the interface. While I believe that it's important to focus your efforts designing/developing for the most likely cases it's also relevant to cover edge-cases. Fuzz-testing is a great way to discover them.

I hope this help. Let me know if you any other questions :)

Hey Iwein, there are couple fundamental issue with the way we style HTML elements today. CSS is exposing every declaration into a global namespace. This makes it to eliminate dead code as it is hard to figure out where it is used. Many techniques like BEM were invented and declared as "the right way" to do styling.

I don't know if inline-styles defined in JS are the end-game, but working with it in combination with building components turned out to be working way better for us than using CSS.

If you want to know more about it I highly recommend this slidedeck: https://speakerdeck.com/vjeux/react-css-in-js

Sorry for the late reply.

Right now there is a lot of stuff happening to simulate Web Components. Going forward they will become a W3C Standard and we can reduce the complexity. You might want to look at the current Draft https://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/...

What’s happening at the moment is that the output for <x-loading></x-loading> is:

    <span is="x-loading">
      <style>
        @-webkit-keyframes x-loading-dot {
          0% {
          opacity: 1;
          }
          50% {
          opacity: 0;
          }
          100% {
          opacity: 1;
          }
        }
        .x-loading-one {
          opacity: 1;
          -webkit-animation: x-loading-dot 1.3s infinite;
          -webkit-animation-delay: 0.0s;
        }
        .x-loading-two {
          opacity: 1;
          -webkit-animation: x-loading-dot 1.3s infinite;
          -webkit-animation-delay: 0.2s;
        }
        .x-loading-three {
          opacity: 1;
          -webkit-animation: x-loading-dot 1.3s infinite;
          -webkit-animation-delay: 0.3s;
        }
      </style>
      <span class="q-x-loading" style="color: rgb(80, 80, 80);">
        <span class="x-loading-one">.</span><span class="x-loading-two">.</span><span class="x-loading-three">.</span>
      </span>
    </span>
If a component like the overlay also contains logic the code will be added to your compiled and minified JavaScript output.

For blossom.io/bee you can find the compiled output here https://www.blossom.io/bee_documentation.html_bootstrap.dart...

Thanks for sharing your experiences and insights!

Universities do a great job teaching abstract concepts and doing research. Web became a great and wide spread platform. Sadly they often dictate students not to work with web-technologies. It's possible to teach the concepts and at the same time use state of the art technologies.

I believe there is plenty of room for improvments in universities. I would love to see distributed revision control systems as a standard for student projects.

It's great to see people like you challanging the status quo and try improve the environment.