Explore >> Select a destination
|
You are here 
|
steve-yegge.blogspot.com | ||
| | | | |
blog.quaddmg.com
|
|
| | | | | [AI summary] An article argues that dynamic programming languages are more suited for flexible, interconnected application environments using self-describing data formats, while static languages are better for robust, structured data processing. | |
| | | | |
c0de517e.blogspot.com
|
|
| | | | | Realtime rendering and videogame programming mostly, but I love computer science and visuals in all their forms. This is a notepad of my ideas. | |
| | | | |
existentialtype.wordpress.com
|
|
| | | | | While reviewing some of the comments on my post about parallelism and concurrency, I noticed that the great fallacy about dynamic and static languages continues to hold people in its thrall. So, in the same "everything you know is wrong" spirit, let me try to set this straight: a dynamic language is a straightjacketed static | |
| | | | |
jmmv.dev
|
|
| | | Dependency injection is one of my favorite design patterns to develop highly-testable and modular code. Unfortunately, applying this pattern by taking Rust traits as arguments to public functions has unintended consequences on the visibility of private symbols. If you are not careful, most of your crate-internal APIs might need to become public just because you needed to parameterize a function with a trait. Let's look at why this happens and what we can do about it. | ||
