1. Why Beskid Exists
Opinionated context for the language—why the industry stack is broken and what Beskid refuses to repeat.
Why Beskid Exists
TLDR: Why not? It’s not hard to overthrow the tech stack in identity crisis…
Beskid exists because I’m done with C#/.NET’s abstraction sprawl and runtime identity crisis. This chapter is an opinionated essay with receipts. It is informative, not normative—if you want enforceable rules, open the Platform specification.
I tried to build a form generator with Blazor, ended up with rewriting C# in Rust, because that’s a logical next step when you doubt sense of existence.
What you will find here
Section titled “What you will find here”| Section | Topic |
|---|---|
| 1.1 My story | Personal context. |
| 1.2 Current state of languages | C#, Java, Go, and why Rust/Zig are not daily drivers. |
| 1.3 SOLID, DRY, and the failure of DDD | Good principles weaponized into ceremony. |
| 1.4 Trauma — by developers, for developers | Ecosystem fracture, designer fantasy vs field reality. |
| 1.5 Are we really standing on the shoulders of giants? | Compilation history, VMs, JIT, and cognitive traps. |
| 1.6 segfault or not to segfault | Memory models, GC, ownership, and why Go is almost right. |
| 1.7 Why are we making this so hard? | Business reality vs engineering theatre. |
| 1.8 Conclusion | What Beskid is actually trying to be. |
Not into the philosophy?
Section titled “Not into the philosophy?”
Fair. Skip to 01. Tooling and Editors and treat Beskid as a tool until the existential dread becomes useful background.
Start the chapter
Section titled “Start the chapter”Begin with 1.1 My story or jump to 1.2 Current state of languages if you do not care about autobiography.
