[1]: https://blog.bullettrain.co/teams-should-be-an-mvp-feature/
138 karma · joined December 16, 2017
[1]: https://blog.bullettrain.co/teams-should-be-an-mvp-feature/
I used it for more complicated components like a mobile nav with animations, and for some re-usable pieces like a subscribe form. The downside with Alpine.data is that it splits the HTML from the JS, so developing and refactoring was a bit of a pain, and caused errors because of old variables I accidentally left in the HTML (whereas Preact/TSX would give me an in-editor error).
It also didn't really mitigate the need to wire up all the pieces your data component exposes into an HTML correctly. Though, this was working inside a simple PHP-based templating engine — maybe one that supports better snippets with parameters would make that part of the experience better.
For lightweight front-end tooling, nothing has unseated the ease of Preact for me.
I wrote a post about that here: https://rosszurowski.com/log/2022/makefiles
Glad you like it! The text styles are custom, and the layout is built using an in-house CSS framework not unlike Tailwind [1].
But if you'd like to build something similar, you could get pretty close by using something like Tailwind and building with Rasmus Andersson's lovely (and open-source!) Inter type family [2], which we use throughout the site.
Anyone know why that would be the case? I'm trying to not assume malice (eg. maybe it got misflagged?) but it certainly feels like censoring and is yet another push for me to drop Messenger too.