This is a weekly roundup of awesome DEV comments that you may have missed. You are welcome and encouraged to boost posts and comments yourself using the #bestofdev tag.
I go cross-eyed dealing with regex, but this is an excellent reference I'm definitely coming back to. I almost always head to regex101.com whenever pattern-matching starts to devour my brain.
After reading Load Pages Instantly with instant.page, @solkimicreb
very respectfully offered some additional context and a recommendation in response to the post. These sorts of exchanges are incredibly valuable for everyone involved:
I see this repo frequently nowadays and I feel like I have to go a bit against it. Sorry. 😕
TLDR: This goes nicely with some server rendered and static pages but not so nicely with SPAs.
Prefetching is an amazing tool but it is meant to be used selectively, in context-specific use cases. Making all links into a prefetch one is not a good idea, if it would be the browser devs would have done that instead of giving us an API.
This does prefetch pages on hover but prefetching a page only involves fetching the entry point (index.html), it does not fetch secondary resources. A lot of modern pages have tiny index.html files and huge secondary bundles (JS and CSS). In this case prefetching has no impact and server push or a PWA could be utilized better.
Most SPA routers use 'fake'
a tags (with prevented default event handling) under the hood for client-side routing. This is done to combine the best parts new-school and old-school routing - like keeping the right-click 'Open in new tab' functionality. Prefetching on hover events over these 'fake'
a tags will simply fetch your SPAs index.html once more. This is just added network traffic with zero value.
There are so much more that can be prefetched, apart from links and whole pages. Just always pay attention when you add a new resource and decide if it benefits from prefetching. It is usually not a big overhead.
I think this is a witty idea and the code looks very clean though. Also props for raising awareness regarding the newish prefetch capability!
EDIT: I wrote this based on my personal experience, without getting into the spec. Please correct me if I mentioned something incorrect.
Short and sweet, @nektro
offered a recommendation in response to What are some Browser plugins that you can't live without ?:
All browsers should come pre-installed with uBlock Origin.
In a wonderful article, 6 Mistakes You Might Be Making As A New Web Developer & How To Avoid Them, @hamatti
selected one point where their opinion differed. It led to a productive discussion, and even an update to the original post!
I do disagree with this however
There are different approaches to learning. I started from a very theoretical point of view and wanted to have good base understanding before moving forward. I ended up not building a lot of things because there was always so much to learn.
I tried to understand the
So I would say that both approaches are fine for a beginner developer, it all depends on what's the best way for you to learn.
answered After you start a new job as a software developer/engineer, how long it took before you feel you are very productive? by talking about the ramp-up time involved in most jobs:
My first role, I will say took about 3 months before I felt like I was contributing. I'd have some small wins, but then I'd feel like I wasn't able to contribute when it mattered most. Granted I was a junior developer, and was not used to working in an environment with other developers.
To be honest, I still feel like it takes me about the same amount of time to get fully spun up on a new role, but this also entails more responsibility outside of just developing software, such as working with product owners/stakeholders to understand the road map forward. It seems like the more experience I get the more responsibility I take on. I'm curious to see what others say.
See you next week for more great comments ✌