I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
I wrote it before I started working at DEV and I believe it was my now co-worker @jacobherrington
that integrated parts of that article into the DEV docs . Since starting at DEV I’ve also updated the docs related to the frontend, including webpacker 4 upgrades.
Other things that we do in the frontend to make things faster are leveraging service workers as well as dynamic imports. You can dynamic see imports in action in for example the onboarding process or the logged on feed.
In regards to reusable components, we use Preact components mainly for the logged on experience. The only exception to this I believe is search.
Something that I would like to experiment with during the next cooldown period or the following one is server-side rendering Preact components in a Rails app as it is possible. I put the question out on Twitter and the creator of Preact, @_developit
chimed in that it was possible.
Great links! Just finished reading the frontend brain dump, planning to read the others as well.
Thank you so much for using React/Preact in various modules of the site dispersed in different places, instead of a SPA. I believe this is the right way to go for content-based web apps. Too many tech startups default to React and SPA just because that's what everyone else is doing, and perhaps in some ways it's "easier" to just go full SPA when you already want to use React (for organizational and team-scaling reasons). When React modules are small and separate on a page, they are really snappy. When it's a SPA and entire pages changes, it feels way more sluggish than what you do with Instant Click and HTML outputs from server. I wish what you do is the standard across the web among content sites.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This article might interest you Bigi. It talks about the frontend stack including InstantClick.
dev.to’s Frontend: a brain dump in one act
Nick Taylor (he/him) ・ Apr 23 '19 ・ 8 min read
I wrote it before I started working at DEV and I believe it was my now co-worker @jacobherrington that integrated parts of that article into the DEV docs . Since starting at DEV I’ve also updated the docs related to the frontend, including webpacker 4 upgrades.
Other things that we do in the frontend to make things faster are leveraging service workers as well as dynamic imports. You can dynamic see imports in action in for example the onboarding process or the logged on feed.
In regards to reusable components, we use Preact components mainly for the logged on experience. The only exception to this I believe is search.
Something that I would like to experiment with during the next cooldown period or the following one is server-side rendering Preact components in a Rails app as it is possible. I put the question out on Twitter and the creator of Preact, @_developit chimed in that it was possible.
@ben also has some great posts about making DEV fast.
Making dev.to Incredibly fast
Ben Halpern ・ Feb 2 '17 ・ 5 min read
What it Takes to Render a Complex Web App in Milliseconds
Ben Halpern ・ Aug 18 '17 ・ 4 min read
Instant Webpages and Terabytes of Data Savings Through the Magic of Service Workers ✨
Ben Halpern ・ Dec 18 '19 ・ 5 min read
Thanks for showing DEV some love and looking forward to your next article! 👋🏻
Great links! Just finished reading the frontend brain dump, planning to read the others as well.
Thank you so much for using React/Preact in various modules of the site dispersed in different places, instead of a SPA. I believe this is the right way to go for content-based web apps. Too many tech startups default to React and SPA just because that's what everyone else is doing, and perhaps in some ways it's "easier" to just go full SPA when you already want to use React (for organizational and team-scaling reasons). When React modules are small and separate on a page, they are really snappy. When it's a SPA and entire pages changes, it feels way more sluggish than what you do with Instant Click and HTML outputs from server. I wish what you do is the standard across the web among content sites.