ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Backbone’s built‑in Events mixin lets you decouple views and models with a publish‑subscribe bus. This guide walks through the basics, a global event aggregator, a to‑do list example, trade‑offs, and practical steps to adopt the pattern safely.
Learn how to use web3.js’ <code>pastEvents</code> with block‑range pagination to fetch all ERC‑20 Transfer logs reliably. A step‑by‑step guide, example code, trade‑offs, and best practices for Goerli USDC events.
Learn how Backbone.Events’ listenTo/stopListening prevents zombie Views and how a simple event bus enables clean cross‑component communication.
Learn how to use Backbone.Events namespaced listeners for attribute‑specific communication and avoid memory leaks by cleaning up views correctly.
Event Subscription Lifetime in C# A standard C# event holds a delegate whose Target property strongly references the subscriber. While the publisher remains alive, the subscriber cannot be garbage collected, even after all application references to the subscriber are dropped. Transition to Weak Listeners Replacing explicit -= unsubscription in IDisposable.Di
In Backbone models, the validate callback is designed to intercept attribute changes during set() or save() . If the callback returns an object or throws an error, the model is supposed to prevent the update and trigger the error event. However, there is technical ambiguity regarding the deterministic sequence of event firing when validation fails. While the
Backbone.Model → Backbone.View: Coordinating batch change alerts without notification noise The goal is to keep a Backbone.View responsive while a Backbone.Model receives many rapid attribute updates. Each call to model.set fires a change event by default, which can trigger a full re‑render of the view. Using {silent:true} suppresses these events, but then t
backbonejs
web3js
javascript
csharp
dotnet