This week's newsletter comes with no groundbreaking news, but just a heartfelt reminder that we're inching closer to my next big milestone of 3000 subscribers. Let's keep the Vue & Nuxt love flowing!
Vue School's legendary Free Weekend is back, and it'll be hitting your screens for 48 hours only from 23 - 24 March 2024. They make all 1,100+ lessons and 58 courses available to you for FREE.
Vue recommends to use computed properties instead of methods, if you want to cache the result. Let's take a look at an example using a method invocation:
Computed properties are cached based on their reactive dependencies. A computed property will only re-evaluate when some of its reactive dependencies have changed.
In comparison, a method invocation will always run the function whenever a re-render happens.
Why do we need caching? Imagine we have an expensive computed property, which requires looping through a huge array and doing a lot of computations. Then we may have other computed properties that in turn depend on list. Without caching, we would be executing list's getter many more times than necessary! In cases where you do not want caching, use a method call instead.
👉🏻 There are parallels between the struggles of dependency management in software development and the imposed societal expectations that often lead to burnout in life.
👉🏻 This article explores the various aspects of the localStorage API, its advantages and limitations, and alternative storage options available for modern applications.
👉🏻 An open-source desktop environment that runs in a web browser.
👉🏻 It can be used to create remote desktop environments and serve as an interface for various services, including cloud storage, remote servers, and web hosting platforms.
Comments? Join the discussion about this issue here.
Sunday, January 5, 2025 Update: Bluesky images work again and thus the Great Art on Bluesky channel is back. If you're on Bluesky please subscribe. # The crazy thing about Bluesky's API is they took already standardized things like links and enclosures, and after 20+ years came up with new definitions. Makes our apps more expensive to maintain, and we waste time and human wear and tear on stupid bullshit make-work. Developers are people, and our work is already horribly overly complex, we're working at the edge of comprehension, and what the fukc let's throw some more unnecessary complication into the mix. Arrogance, narcissism, whatever the source is, it's not a good way to introduce yourself. And, even better, after you go through the maze they break it, with an error message about legacy blob bullshit. They've already done this, and they're just getting started. It's why I say they should just adapt to RSS instead of trying to forc...
评论
发表评论