-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reflect on our React-based JavaScript stack #197
Comments
Should we turn this into an issue that's more actionable? Or close?
|
I think this is plenty actionable. Let's set a time during R&D to have an intentional team discussion about what we like and dislike about our JavaScript tools. We did this for our devops stack, and it was very helpful in surfacing pain points and providing priorities for areas of improvement that we could measure proposed changes against. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're still in the process of building expertise in our preferred JavaScript frameworks, Gatsby and React, so this issue is for the medium to long term. Once we have developed sufficient and shared expertise in the core concepts and patterns of our stack, let's ask ourselves: Are our tools working for us? What do we like? What don't we like? Are there better (for us) alternatives? (One name that came up is Svelte.)
The text was updated successfully, but these errors were encountered: