What We Lose When Everything Is a Wrapper
The article discusses the complexities of modern software development, particularly the reliance on multiple layers of dependencies. It reflects on the author's experience porting Wolfenstein 3D to HTML5 without using external packages, emphasizing the clarity that comes from owning the entire stack. The piece argues for a balance between utilizing dependencies and understanding their impact on the development process.
- ▪Modern software often relies on multiple layers of dependencies that can obscure understanding.
- ▪The author ported Wolfenstein 3D to HTML5 without any external dependencies, focusing on the direct use of JavaScript and canvas.
- ▪This approach allowed for a clearer understanding of the code and its complexity, as it was tailored specifically to the problem at hand.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1115191) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Viktor Lázár Posted on May 17 What We Lose When Everything Is a Wrapper #architecture #javascript #gamedev What a 14-year-old HTML5 Wolfenstein 3D port taught me about owning the stack A recent Primeagen video sent me back into an old feeling: the strange discomfort of realizing how much of modern software is now built around things we do not really own. Not in the legal sense. In the practical sense.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
