Let's chat about the latest Kubernetes discourse, where some people decide to call it out for using DNS for service discovery. First, DNS for service discovery is just fine; but not without its challenges. Let's explore a little.

If don’t qualify the name, you get up to 10-20 DNS queries from the Pod every time an inter service request is made and that hammers CoreDNS under heavy load. Ask me how I know. Maybe it’s different if you’re on Solo/Istio. Is that the point being made? 🤷

What is something that helped you take a significant leap in your career? Technology or piece of advice... 💬

Today is a very sad day. Bram Moolenaar of vim fame passed away. I feel like I grew up as a programmer with vim. He will be missed greatly. groups.google.com/g/vim_anno…

Technology can be so much fun, but then you realize you also have to make money. What a downer.

Bw-Tree is a variant of B -Tree that aims to provide better performance for "modern multi-core machines." I was surprised how simple it is conceptually. But of course implementing a Bw-Tree sounds tricky indeed. 1/

"Scala is failing because of bad marketing." Bad take. Nokia had great marketing, but they lost smart phone wars because of product. ChatGPT had no marketing at all, but hit 1 million users in 5 days. "Scala is failing because of monads." Bad take. Developers don't avoid Java because the FunctionalJ library exists. Rather, if they don't like functional programming, they'll avoid FunctionalJ. "Scala is failing because of chance." Bad take. JVM languages that consistently focus on industry needs (not academia) and offer a compelling & unique package to industry end up succeeding. "Scala is not failing." Bad take. You're lying to yourself or believing bogus growth charts like the one put out by the Scala Center. Scala has been shrinking since 2017, and much more rapidly recently. "Scala is failing because of JVM." Bad take. JVM is hurting in the days of cloud-native, but it's still gigantic and Kotlin demonstrates you can grow even if the overall JVM market is not growing. "Scala is failing because of Kotlin / Java." Kotlin / Java becoming a better Java indeed could decrease the rate of growth, as more potential users choose Kotlin or Java, but wouldn't explain a mass exodus from Scala as we are seeing. "Scala is failing because it lacks a direct-style stack." Bad take. Kotlin started to succeed with Spring long before it had Ktor. Because Scala runs on the JVM, people can use existing stacks like Spring, Micronaut, and Quarkus. "Scala is failing because of complexity." Bad take. Complexity does indeed affect adoption, but C is the most complex mainstream language in the world, and still manages to come in 5th. A complex language that meets industry needs can still succeed. "Scala is failing because of drama." Bad take. *cough* Rust Foundation *cough*. Drama is tiresome but most developers don't know or care about stupid drama. Languages and ecosystems that brilliantly solve real pains in an industry-focused way get traction. ----------------- Scala is failing because it has not met the needs of industry. With Scala 3, it has taken many steps backward, lost the trust of many companies, contributors, and developers, and shows signs that it will not learn from these mistakes and will never prioritize industry over academia. If we want Scala to succeed in industry, then it must cater first and foremost to industry, and that means cleaning house, radically refocusing, and clearly and publicly committing to a new future for industrial Scala.