If we’re going to build a full JavaScript framework from scratch, we need to start somewhere. Personally, I like having tangible results up front, so let’s start with the bare-minimum needed to create a visible webpage — let’s start with the rendering engine!
Web development frameworks are the backbone of modern full-stack engineering. In modern web dev, nearly every project starts with a choice of framework, and builds every further decision atop that.
On the surface, it might be easy to compare & contrast the differences between e.g Vue and React, but to effectively evaluate and use either of them requires a much deeper understanding.
In this blog series, we’ll dive deep into the core concepts used by web dev frameworks and build our own from scratch atop those principles. At the same time, we’ll leverage the latest features modern browsers have to offer.
This is Effectual Web Development.
I had too much time on my hands during a flight and decided to answer the question: “How hard would it be to write a compiler in TypeScript’s type system?”
Unsurprisingly, this led me down an incredibly cursed Rabbit-hole that I have graciously documented for your abject horror enjoyment!
You can find all of the source code here.
Although I ended up not spending much time on this year’s RWCTF, I did (with the help of my awesome teammates) solve one problem: RWDN. The intended solution involved a bug in one of their middleware handlers that was designed incorrectly and allowed attackers to bypass a crucial check. However, I found that there was an alternate bypass that would have worked even if their code was correct. Let’s discuss what the bug is, and why it could be a problem for “real world” applications.
Much like the rest of the world, DEF CON CTF returned this year in a hybrid online/in-person format. For those who wanted it, space was reserved on the game floor to hack amidst the other teams that came to Vegas. For the rest of us who were still a bit nervous about large crowds, the infrastructure would be hosted online and accessible from anywhere in the world. Torn between the two choices, we opted this year for a middle ground: all of us together, but in a house 300 miles away.