I would expect the impact of cpu limits to be different between K8s providers. I have only used memory limits. If I had a pod that tended to be very cpu intensive, I would schedule it on it's own node group.
Does my opinion on SQL and ORMs matter anymore? What does Claude think about ORMs an SQL? So far Claude seems to be content with my existing patterns of using JPA/Hibernate. We've been having this conversation since the early 2000s. Will we have it next year? Maybe just for fun... to pretend we are still relevant :(
I have a verizon watch only account. I was able to get the new app working, but it was a struggle. I think it worked on the 3rd or 4th attempt. I had to start over and lost all of the contacts that were connected to the watch. Fortunately, there were only a few.
Overall, the Gizmo watch has been nice to have, but it leaves a lot to be desired. It's surprising that there are not better products in this market segment.
I didn't realize Apple had a kid mode. Of course I see Apple watches everywhere, but I haven't talked to any parents about them. When we got the gizmo 3ish years ago, it was popular with a lot of kids around here. I wasn't hearing of kids using the apple watch. The gizmo is nice in that they can call us and that their contacts are limited. I really don't want to have more features than that. I'm just surprised that it feels like an "unpolished" set of features.
You literally can't set up am Apple watch for kids without a parent-owned iPhone. It's the kind of vendor lock in thst all other companies get immediately chastised for, but Apple always manages to get a pass. I hope they pay their marketing teams adequately for those amazing ways in which they twist public perceptions.
I don’t like that aspect either, to be clear, but the majority of American parents use iPhones and don’t have any plan to leave the platform, and there are other kids smartwatches on the market not made by carriers.
With Google moving their smartwatch efforts to the pixel brand I'm worried about longevity here. It also has a lot of the downsides of the Gizmo: 20 contacts max, texting only through the app, can't interact with friends. If I'm going to get new ones for the kids I'll probably do a TickTalk or Cosmo that don't have these drawbacks.
I almost started talking about how I think the best solution is really just a customized/locked down normal smartphone but I’m not sure how helpful that is to the discussion.
I use both SQL and ORMs every day. I've used hibernate since 2004. I've certainly had some difficult times with it; but overall it is a net positive. I find that it generally works well and saves a ton of time as long as I stick to my known patterns.
There's a mass delusion in the industry that using Kubernetes has to be hard, grossly over complex, and is always wrong if you are not Netflix scale. Is the system as described by the author significantly less complex and better than a small Kubernetes system? Sounds like they went through a lot of work to get it to their desired state.
Rolling your own zero-downtime deployments is as about as a good idea as rolling your own security... it's not a good idea.
I run our small system on a single EC2 instance with K3s. It runs a half-dozen or so services and does it quite well. I don't think it is particularly complex or over engineered. I like how easy it is to maintain the configuration in a helm package and quickly deploy it in different environments.
There is a learning curve for doing K8s well, but that's true for any non-trivial system.
I've been using Macbook Pros for a long time. I usually spend 3-4k on them. I recently purchased an 14" Asus ZenBook for $1300 and loaded Omarchy Linux on it. I wanted to have something less expensive and lightweight for traveling. I really like it a lot! I notice that it is a little slower than my Macbook Pro, but the performance completely acceptable for most things.
laptops seem kinda solved now? for every cpu vendor and every os theres now a great option that just, works, so everyone can just use what they like and not be at a disadvantage due to not knowing the latest developements in the space, or due to habitual preference. Good type of boring
Some people get entirely too dogmatic about their “XYZ is wrong, don’t do it!” beliefs. At the time I implemented JWT in our system, many years ago; it was the most straightforward way to solve the problems that I had. I read about the pitfalls and have yet to experience any of them. So in short.. “no regrats” from this heathen.
Isn't JWT's main benefit being a standard interchange format? 3 parts: header, payload containing user info, signature from whatever authenticated the user. Can be encoded for URLs and decoded to JSON. Seems pretty innocent to me.
I maintain a system I created in 2004 (crazy right). Not sure how we lived; but at the time, emojis were not as much of a thing. This has come to bite me several times.
I don't like being negative and I always appreciate open source / free software but..
I tried using it in a small k8s cluster on digital ocean. Initial installation using the recommended helm package was easy enough. However, it only saved a very short period of log data. I spent a fair amount of time searching docs and the web about how to increase the storage, with no luck. Such an obvious and common need should not be so difficult to configure. You should not have to deep dive, reverse engineer, and read source code in order to solve such simple problems.