Pinned Tweet
As they say that, if you are doing one thing you are missing many others. If you are using #react your are not using or falling behind in #angular and #vue. But you are still writing #javascript which matters more that getting in #beginner discussion of which framework is better.
I wish @goodreads had a option to add a note to "Want to read" book as
- Where did you find about this book
- Why should you read it
I wrote about how table sorting made easier with the combo of angular signals and httpResource.
-> Update the sorting signals
→ the resource re-runs automatically
-> Updates the UI
#angular #httpResource
Going to defaults rather than remapping window navigation in #neovim
View source is a string representation of the file. It is not the DOM. Your HTML file isn't the DOM.
DOM is a structure in memory.
HTML files isn't direct representation of DOM
No point of remapping one time shortcut in #vim . For example using default mapping for resize width (ctrl +w <) is just fine. Rather than searching for the mapping
This recent supply chain attack on chalk js monkey patched fetch and XHR api which kindly remembers me of #Angular 🙂
Samiullah Khan retweeted
🚀 The #StateOfHTML 2025 survey is now open!
➡️ Take it now: survey.devographics.com/en-U…
💡 Spending time to fill these out is an investment into your craft, as browsers use the results to make prioritization decisions.
You don't have to do it in one sitting (or even one device).
With #Angular new style guide to name components, I also want to drop Any prefix from component slector, third party components should come with prefix ao it won't collide with local components
Even today if you remove this tag, the mobile browser will assume that this website is made for pre 2007, optimized for desktop than mobile
It will be emulated in the viewport of 980 pixels wide.
2/2
Credits: @firt
I didn't know that it was Apple who came up with this meta
<meta name="viewport" content="width=device-width" />
for the launch of iphone, so that website made for mobile would fit to the mobile screen.
1/2
So #Angular service "providedIn: any" won't aut o destroy upon consumer destruction. Manual intervention required for clean up.
Does this mean dozen of service copies are floating around till the life cycle of app?


