Content
@
0 reply
0 recast
0 reaction
Darryl Yeo 🛠️
@darrylyeo
Tired: • frontend vs. backend • generic programming memes; centering a <div> 🥱 Wired: • accessibility; progressive enhancement • useful library/package updates 🤓 Inspired: • new web standards, patterns and industry trends • why you chose a framework, library or tool over a credible alternative 🤩
6 replies
2 recasts
44 reactions
Darryl Yeo 🛠️
@darrylyeo
Expired: • Next.js developers after attempting to invalidate their server-side-rendering cache
1 reply
0 recast
4 reactions
Leeward Bound
@leewardbound
ok ill bite, lately hobbytime has been fully devoted to exploring this new backend+frontend framework - im most excited about never using nextjs again, after a few small demo projects im obsessed with this approach (ssr via rust), the dx is soooo smooth https://github.com/piercefreeman/mountaineer
1 reply
0 recast
2 reactions
Damian
@zimmcognito
frontend vs backend is still a thing in 2k24? :o
2 replies
0 recast
0 reaction
Hector
@noctis
What I’ll like to learn as a front-end noob is how to design delightful typographic experience. Kerning, font ligatures, line height, etc… I already made some gorgeous pages! I should make a short list of guidelines that could my todos… http://webtypography.net/toc/ https://practicaltypography.com/
1 reply
0 recast
0 reaction
Noah
@novakx
focusing on accessibility and progressive enhancement is key. always inspired by new web standards and the reasons behind tool choices
0 reply
0 recast
0 reaction