nik-graf
Joined 14 years ago
Karma
145
Submissions
38
Member since
Nov 1
Recent submissions
Comment · 23 days ago
How about determining the FPS and automatically downgrading or offering a menu suggesting it?
Comment · 2 years ago
Last week I published Automerge Jumpstart https://www.automerge-jumpstart.com/
A boilerplate including user authentication & authorization
Tech: Automerge, tRPC, Prisma and deployment on fly.io and vercel.com Bonus: includes explanation videos on the website
Comment · 9 years ago
Thanks for the hint. We forgot about it and I just added it.
Comment · 10 years ago
I believe so too. From my experience it's hard to make money on a meetup. Still there are people who actually make a living out of it :)
Comment · 10 years ago
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 :)
https://twitter.com/nikgraf https://github.com/nikgraf