This is just the beginning!
Read our launch post
Bristol JS returns with Max Stoiber & Sarah Dayan
61
Attendees
2
Talks
Attendees
61 people are attending this event
Hey Bristol JS... sorry we've been away for so long.
We've missed you all so much in our extended break but we're really excited to be back and have quite the event to kick things back off.
This August we have the amazing virtual event with Max Stoiber and Sarah Dayan giving talks.
If all goes well we're hoping to kick off in-person events from September. Please let us know in the comments what talks you'd like to see us cover and if you're interested in giving a talk.
We've missed you all so much in our extended break but we're really excited to be back and have quite the event to kick things back off.
This August we have the amazing virtual event with Max Stoiber and Sarah Dayan giving talks.
If all goes well we're hoping to kick off in-person events from September. Please let us know in the comments what talks you'd like to see us cover and if you're interested in giving a talk.
Talk #1
GraphCDN - How to edge cache GraphQL APIs
For years, not being able to cache GraphQL was considered one of its main downsides compared to RESTful APIs. Not anymore. GraphCDN makes it possible to cache almost any GraphQL API at the edge, and not only that but our cache is even smarter than any RESTful cache could ever be. Let's dive deep into the inner workings of GraphCDN to figure out how exactly we make this happen.
Max Stoiber
Talk #2
Learning from the Mistakes of a v1
In early 2018, I published Dinero.js, the Moment.js for money. After two years of existence, 29 releases, 3.6k stars on GitHub, and peaks at over 6k downloads per day on npm, it's time to release a v2 to fix the design issues of the v1. But how do you craft an impactful new major version?
A v2 usually marks a turning point. If you think of your favorite projects, they all probably started becoming interesting around their second iteration: Vue.js, Magento, Symfony, Angular, etc. A v1 is often experimental. It's an excited new kid on the block, coming with big ambitions but numerous flaws. It has no experience in the real world, but it thinks it knows everything and wants to do it all. That's the case of Dinero.js, and it's time for it to grow up.
In this talk, I'll go over the most significant issues of the v1, why they happened, and how I intend to fix them. I'll explain how I approached this v2, what kind of feedback I used to design it, and how going with a design-driven approach
A v2 usually marks a turning point. If you think of your favorite projects, they all probably started becoming interesting around their second iteration: Vue.js, Magento, Symfony, Angular, etc. A v1 is often experimental. It's an excited new kid on the block, coming with big ambitions but numerous flaws. It has no experience in the real world, but it thinks it knows everything and wants to do it all. That's the case of Dinero.js, and it's time for it to grow up.
In this talk, I'll go over the most significant issues of the v1, why they happened, and how I intend to fix them. I'll explain how I approached this v2, what kind of feedback I used to design it, and how going with a design-driven approach
