I've been building multi-cluster Kubernetes for some time and things like External DNS and Ingress controllers per app are just non-starters. They always felt kludgy having K8S orchestrate things external to the cluster and their anti-patterns IMO.
I love how this post, almost to a fault, just jumps right in. No BS set up. Not even context set up. Just what you expected after reading the title. That's an art.
As for the context of the article, maintainability is almost always worth the cost of the function lookup. The proof here that the cost is almost non-existent means to me the maintainability is always worth the perceived (few cycles) impact unless this is real-time code.
Claude Code is pretty good at Swift + Swift UI. I created and have been iterating on a menubar app for myself that I plan to share with a small team. I'd prefer to do this native than go through a 3rd party solution.
I do have prior experience developing for iOS but that was pre-swift.
This is absolutely untrue. Code from JDK 8 runs fine on JDK 25 (just released LTS). It is true that if you did something silly that locks you into certain dependency versions, you may be stuck, but this is not the majority of applications.
Using Lambda functions stored in ECR has no impact on performance from my experience. AWS Lambda uses Firecracker under the hood, which builds a VM from a container image. It's likely that non-ECR image based Lambdas are actually packaged as a container image before being launched into a Firecracker VM.
What’s more interesting to me than the NPS scores are the free form comment section below the 0-10 rating.
Never mind that anything below X is considered neutral or a detractor. You asked a user / customer/ etc to rate you on a scale of 1-10 and then tell you why.
Want to know what you’re truly screwing up on? Take the feedback on your 1-6 scores seriously and you can find the low hanging fruit to take a product from mediocre to a great user experience.
That’s the true NPS value. It’s all about how you handle the feedback.
The same functionality could have been accomplished by just allowing us to specify the max number of concurrent instances of a function that can be active at a time. With proper request queuing the problem would be solved. As usual, AWS solves a problem they failed to design for by charging for an overly complex solution. Flame me if you want but there are K8s serverless frameworks that address this out of the box.
> Programming in C/C++, Java, Javascript, that's easy, anyone can write code. But having the skill of standing in a circle and saying what you've been working on, what you will be working on, and if you have any blockers, that takes pure talent.
I'd have to say Google's Tools are 100x better than they used to be. Android Studio is based on IntelliJ IDEA and they've done a decent job of getting emulator performance where it needs to be on good hardware.
That being said, I think Swift was a huge win to Apple developers who were unhappy with Objective-C. Xcode and the iOS simulator are still way ahead of Google's tools on performance.
On SDKs:
This is where Google is really blowing it and where Apple shines. Apple's SDKs tend to be well thought out and well documented.
Android's SDKs on the other hand are poorly documented and are fragmented into a mess. To expand a bit, there are new SDKs for new features on new hardware and tons of "compatibility" SDKs that have to be used to bring modern features to your app if you want to support old Android releases (you have to).
Android's SDKs show both a lack of direction and a rush to patch up the fragmentation mess. This isn't a knock at their hardware (Pixel, etc), which looks nice. There's just a general lack of coherency among their APIs and no clear path on how they're going to fix it.
TLDR;
It's fair to say Google is making progress making their developer's lives better but Apple (and it's community developed SDKs) still make a better developer platform and a better software to develop with.
As an US citizen, I no longer salute that piece of cloth or sing the national anthem at sports games. I don't even bother standing for it and encourage others to do the same to show our distaste for how our own government treats us.
I was disgusted in the 2000's when being against the Iraq war was not only being flaunted unpatriotic but not supporting our troops. That's BS. I support our troops and would rather not have seen them deployed to conduct Cheney's bidding.
I will sign the petition and if some asshole gives me trouble at the border for it, so what? I'm a US citizen and entitled to re-enter my country. F them.
"If patriotism is 'the last refuge of a scoundrel,' it is not merely because evil deeds may be performed in the name of patriotism, but because patriotic fervor can obliterate moral distinctions altogether”
~ Ralph B. Perry
Gave this a quick look. I'm much more a fan of Spring Boot (http://projects.spring.io/spring-boot/). Like Pippo, Spring Boot starts with a lot of auto-configured defaults that can get you off the ground quickly. However, the full power of Spring and its related projects are at your fingertips and you can reduce the amount of auto-configuration as your project becomes more complex. Also like Spring's stereotype principles more than extending a base "Controller" (in Spring, you annotate a POJO with @Controller or @RestController).
As mentioned previously, JAX-RS really shines for micro services. The same interfaces can be shared between client and server, making client development a breeze. Spring Boot supports JAX-RS services as well via a Jersey adapter.