I’ve very much enjoyed all of my experiences with Deno and I’ve wanted to share that experience along with frequent questions I’ve been asked.
I’ve been thoroughly enjoying my time writing Deno, and I’d like to open up my development publically to help keep me accountable as well as to provide a view in to what Deno development looks like. I’ll be developing a web worker backed, radix tree based, routing + web application server with middleware support, live on Discord on a regular schedule.
Debugging Deno applications inside VS Code is actually pretty straightforward with the right launch config. Use the below
.vscode/launch.jsonconfig to debug your entire deno application, debug all of your deno tests, run a single test file, or just the specific test case that you have currently selected.
Amateur Extra Query Tools is a great website for querying the state of callsigns in any way you might want. For instance looking for upcoming expiring 1x2 callsigns.
Azaleas in full bloom
Some golden hour photos from the river at Raccoon Mountain
AsciiFlow2 is a really awesome tool that embed an ascii monodraw style editor inside VSCode.
TL;DR Read your prospective dependency’s source. You might find evals for no reason.
An interesting exercise in masochism, but also fun in a way. Since you can’t directly include Objective-C APIs in C the author took to straight up using the C level Objective-C runtime calls to perform message passing under the Objective-C runtime. Have a read through the code for yourself to see how it’s done.