/explore
|
You are here 
|
ramonh.dev | ||
| | | | |
carmenh.dev
|
|
| | | | | Developer Relations, Technical Content and OSS | |
| | | | |
andreabergia.com
|
|
| | | | | This post is part of the Languages Opinion series. Languages opinion - part one - JVM Languages opinion - part two - Rust ?thispost Languages opinion - part three - Javascript and Typescript Welcome back to my mini-series about programming languages. In this post, we will talk about one of the most interesting programming languages that I have seen in a long while: Rust. | |
| | | | |
dehora.net
|
|
| | | | | Back in 2013, I started a series of posts on programming languages I found interesting. One of the languages I wanted to write about at that time was Rust. As often happens, life got in the way, and it's only now that I'm coming round to a long overdue post. This is one of a series of posts on programming languages and you can read more about thathere. | |
| | | | |
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. | ||
