Content pfp
Content
@
0 reply
0 recast
0 reaction

sourav currently at DevCon pfp
sourav currently at DevCon
@sourav
a nice take on front-end frameworks! πŸ‘‡ https://www.abeautifulsite.net/posts/thoughts-on-framework-churn/
5 replies
0 recast
2 reactions

typeof.eth πŸ”΅ pfp
typeof.eth πŸ”΅
@typeof.eth
I think the takeaways for me are: - There's costs and benefits to frameworks - There's costs and benefits to metaframeworks - Btw, you don't have to use all metafw features - There's ways to build things that make code more portable, they're worth looking into - Try not to rewrite your app, even though it's fun
1 reply
0 recast
3 reactions

typeof.eth πŸ”΅ pfp
typeof.eth πŸ”΅
@typeof.eth
Agreed there's a cost to frameworks, but it's also a little sus to me to code like you might need to replace your framework later on. It doesn't happen enough to spend _too_ much time thinking about it. Metaframeworks are worth the cost IMO. I don't wanna go back to webpack configs and RYO deploy scripts.
1 reply
0 recast
2 reactions

Gabriel Ayuso pfp
Gabriel Ayuso
@gabrielayuso.eth
As always, it depends. I love using minimal frameworks and decoupled libraries but end-to-end solutions can help you iterate quickly and focus on the product and not the tech. The Rails documentary makes some good points on this. https://youtu.be/HDKUEXBF3B4?si=NN81NsGRbxfYfzsy
1 reply
0 recast
2 reactions

Phil Cockfield pfp
Phil Cockfield
@pjc
Damned if you do. Damned if you don’t. Nice essay! πŸ‘πŸ™πŸ» internalising these creative tensions I feel is so important to make calculated and conscious calls as we go. β€œYa have to do <something>” AND that <something> will bite you in the ass.
1 reply
0 recast
0 reaction

Spencer pfp
Spencer
@spencer-sch
I've been more and more interested in headless UI components and really like the idea of the flexibility of web component based components. I hadn't heard of Shoelace before and now thoroughly intend to use it. Thanks for sharing the article!
2 replies
0 recast
0 reaction