/explore
|
You are here 
|
cowlark.com | ||
| | | | |
mko.re
|
|
| | | | | [AI summary] The author shares an experimental hobby project involving a Forth compiler and interpreter for WebAssembly, discussing its design, implementation details, and performance benchmarks against native and JavaScript versions. | |
| | | | |
blog.valentin.sh
|
|
| | | | | [AI summary] An article arguing that 'vibe coding' is a poor developer experience because relying on AI agents to generate code without writing it manually is analogous to maintaining generated metaprogramming output, which is inferior to using proper software abstractions. | |
| | | | |
zserge.com
|
|
| | | | | Compilers is fun. Want to write your own one? Part 1 - lexer. | |
| | | | |
etherealwake.com
|
|
| | | When writing a freestanding application, it's generally necessary for the firmware engineer to handle runtime initialization. Even when a library like newlib includes a rudimentary implementation of crt0.o, initialization is a very application-specific process owing to the need to initialize hardware, memory, and other loading tasks. In this essay, we examine the current and historical implementation of executable initialization, finishing with a minimal implementation usable with firmware applications. Note: Most firmware applications need to address the initialization of .data and .bss from nonvolatile memory. That is not addressed in this essay. | ||
