Backstory A while ago, I got introduced to the Framework laptop and ended up purchasing one as my secondary dev machine. You are welcome to check reviews online, but what got me into it was the “open-source” attitude from a hardware perspective and the utter respect to the repair right. I am all for “making the best possible use of things”. The fact that Fedora runs great OOB on this machine (see this review) clears the last bit of concern.
Recently, I find myself quite a bit distracted when using Windows for work, with all social media and entertainment apps readily available, so I want a more focused working environment. I have not used Linux since I decided to do a fresh install of Fedora 34 when it first came out and failed. The live USB image behaved quite strangely that time, greeting me with only a blank desktop with no cursor and no installation prompt.
Angular is about to release v13! 13 days until... 😉 — Angular (@angular) October 22, 2021 One of the new features that excites me the most is the persistent build cache. In v12.1, this feature was introduced as an opt-in by the CLI via an environment variable NG_PERSISTENT_BUILD_CACHE=1. Now this environment variable has been disabled. Instead, this caching feature is now enabled by default and can be configured inside angular.
Background For the past few weeks, my major task has been refactoring the old step-wise drafting process of our app into a much more simplified one. Instead of dividing the drafting and submission process into several steps like Drafting, Tagging, Feedback and Finalize, the goal is to have one unified interface where the features previously scattered across different steps can be integrated in one UI by a plug-in manner, similar to how VS Code plugins add new functionalities to the Activity Bar and Side Bar.
Axios is no doubt one of the most popular libraries out there to make HTTP calls, but let’s not forget now we have something equally powerful built into our browser: the Fetch API. In this post, I am going to share my experience of how to achieve the common use case of interceptors with a Fetch-based HTTP client library named “ky”.
WSL 2 finally made its way to the slow ring of Windows Preview! I am sure you are excited about the improved I/O performance, but is there anything to watch out for? In this post, I am going to share with you my experience of setting up a web development within WSL2.