I ran into an issue that slowed me down: when serving the app, Angular CLI’s build cache was preventing updates to the JS and WASM files from being picked up. The build reused a cached version, which meant I couldn’t test changes without restarting or clearing the cache manually.
After a decade of working with TypeScript, my pointer arithmetic skills had become rusty. While I had spent the last few months working with C and C++, my experience is that organizing lessons learned—and relearned—helps fill gaps, and writing an article is a great way to reinforce that.
As someone deeply involved in developing modern browser-based multimedia applications, I recently set out to integrate Web Audio with C++/WebAssembly to optimize an audio-processing workflow. On paper, this seemed like a promising approach—leveraging the power of WebAssembly for performance-intensive tasks while taking advantage of the flexibility offered by
For years, advanced audio processing in the browser has been well within reach, thanks to the powerful Web Audio API—a go-to solution for web developers building dynamic and innovative audio applications. But while creating audio has become simpler than ever, exporting it seamlessly remains a surprisingly tricky challenge in
Combining the descriptive qualities of enumerated types and the easy-to-use nature of strings. During a code review, something that sticks out when the code is full of ad-hoc string checking. For example, implementing a blog engine with three types of roles can start with a check if the user is