- Your own Kubernetes controller
-
A couple of years ago, to understand Kubernetes controlles, I developed on in Java from scratch.
- Types vs No Types - How Types Allow Code to Scale across Developers, Organizations, and Lines of Code
-
I started my professional career with Java and thus, I’m pretty much convinced that types are the way to go. However, the analogy with wiring is on point. If you need to convince your colleagues, I recommend this post.
- From Spring Framework 6.2 to 7.0
-
After all these years, Spring stands the test of time.
- Software architecture styles
-
One can debate the presentation format or the structure, but I like that it lists a lot of styles you can come across.
+ I agree with some of the arguments, but I fundamentally disagree with:
+
At the very least, your web app should start up normally while offline and any outgoing requests should be saved locally and sent when the network is back
+ Most apps do indeed need some kind of initialization, e.g., a list of countries. They can be cached, but they need first to be loaded online. One must be very careful when one’s opinion is worded.
- Preventing unauthorized automated access to the network
-
Interesting to see the massive downvotes and the nature of the comments.
- Abolishing Kotlin Context Receivers
-
The video shows the removal of a Kotlin marker context receiver.
I learned that context receivers are deprecated and will be replaced by context parameters. I wasn’t very enthusiastic about context receivers:
However, it’s not all unicorns and rainbows. In particular, I’m a bit worried that context receivers are going to be abused. Granted, it’s in general the case for every new feature for every language. Yet, I feel the potential for abuse is huge with this one. Only future will tell.
The fact that context receivers never made it pass experimental is telling. Context parameters seem to carry the same "magic" I was worried about.
Interestingly enough, context receivers will be removed from Kotlin before context parameters are introduced. There’s no way to refactor from one to the other.
- Context parameters from the language design perspective
-
I got interested in this new "context parameters" replacing "context receivers". This feature actually got through several iterations with a different name at each iteration: multiple receivers, context receivers, and now, context parameters.
- Microfrontends should be your last resort
-
Finally a post on microfrontends that I can get behind:
- It clearly states that you shouldn’t in most cases
- It clearly states the requirements
- It clearly states the pitfalls
- It clearly states the pain points that could trigger the move
- Patent troll Sable pays up, dedicates all its patents to the public!
-
I can’t stop laughing! Sable has been a bad actor for years, pestering companies, but it definitely has bitten more than it could chew and is now gone for good.
I’m a happy CloudFlare user and I love them even more now.
- Rust needs a web framework for lazy developers
-
It seems like the author wants Spring Boot in Rust.
- Building a Single-Page App with htmx
-
I’m interested in HTMX at the moment. The experiment described in the post is quite interesting; just don’t do it at home.