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.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/lazarv/what-we-lose-when-everything-is-a-wrapper-42e4 |
| Publication time | Sun, 17 May 2026 20:27:49 +0000 |
| Retrieval time | 2026-05-17T20:33:20.987Z |
| Last seen | 2026-05-17T20:33:20.987Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Srcm1JFNtbDC |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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)
