/explore
|
You are here 
|
depth-first.com | ||
| | | | |
www.javaadvent.com
|
|
| | | | | And here we are again. For the third time in a row, we are back to the Java Advent, eager to discover what's new with WebAssembly from a Java developer perspective. Incidentally, since, as you know, I have a favorite topic (after programming languages and compilers, of course), it is also the third time [...] | |
| | | | |
leerob.io
|
|
| | | | | Why is Rust being used to replace parts of the JavaScript web ecosystem like minification (Terser), transpilation (Babel), formatting (Prettier), bundling (webpack), linting (ESLint), and more? | |
| | | | |
www.cesarsotovalero.net
|
|
| | | | | The web is (arguably) the only tech platform that has been continuously transformed and evolved at a global scale over the last 30 years. How was this possible? What can we learn from the past technical mistakes and successes? Over the years, I have witnesses the emergence of various web technologies. Some were revolutionary, while others didn't pass the test of time. In this article, I dive into the evolution of web technologies from the 1990s to the present. My focus is on the engineering paradigms that marked inflection points in web's history. Those who don't know tech history are doomed to repeat past engineering mistakes. | |
| | | | |
debugging.works
|
|
| | | a list of code snippets that explain how to analyze a core dump on Linux | ||
