ok it was fun. claude code was able to create a kubernetes cluster visualization inside an omniverse
next step is to go with VR implementation and a shotgun :D
🦔 HP launched a gaming laptop subscription where you pay monthly but never own the hardware. The high-end option is $130/month for an RTX 5080 Omen Max 16. That same laptop costs $2,110 to buy outright, meaning you'd pay the full price in about 16 months but still own nothing.
If you cancel after the first month, you face hefty fees. Canceling the top-tier subscription in month two costs $1,430 plus you have to return the laptop. You can only cancel for free after 13 months, by which point you've paid $1,690 and still have no laptop.
HP's justification: "The traditional upgrade cycle keeps most gamers perpetually one step behind. But with access to a new laptop every year, your subscription breaks that cycle completely."
My Take
This feels like the logical endpoint of the subscription economy. You pay forever, you own nothing, and the company frames it as doing you a favor. HP is betting that people are so conditioned to monthly payments that they won't do the math showing they'd pay full price in 16 months and keep paying after that.
Memory chip prices are up 60% because data centers are consuming everything. Hardware costs are rising. And now HP is using the affordability crisis to push a model where you never build equity in anything you use. We've seen this with software, streaming, cars, and now gaming hardware. The pitch is always about flexibility and staying current. The reality is you're perpetually renting your life from companies that figured out recurring revenue beats selling you something once. At least when you finance a laptop you eventually own it. I don't know how we got to a place where "you will own nothing" stopped being a dystopian warning and became a business model.
Hedgie🤗
Did you know your MacBook has a sensor that knows the exact angle of the screen hinge?
It’s not exposed as a public API, but I figured out a way to read it and make it sound like an old wooden door.
If you are running in Azure App Service your WebJob as "dotnet $dll" in run.cmd it means you are running 32bit dotnet from a wrong "$PATH". Check it. Make it right - "c:\program files\dotnet\dotnet.exe $dll"
hell no, man. from any perspectives it's bad idea. can't even imagine why do you need a such thing. for what reason? just to collect people with the same passport? hm. again for what reason you needs to collect them? bruh
Long time ago when i was forced to go in to army(18+ years he-he) i spend month in a sorting center, after that spend one week at my home city military facility as a member of a crew, after that by my wish return to sorting center, got papers by a health state and return to home
If you think your service is consuming so much cpu and ram because "business logic" - go to hell. it just means your technical implementation is shit as fuck
AI and dotnet traces help me to find why dotnet project is slow but I still think it's a job for developers not for a devops with pain in the ass which see how app with 100rps use more than 1 full core
Imagine you have like millions of requests in a day. Ok. Great for you. But drop it down like 6m requests if drop down to a seconds level is ~70rps. Your services not "high load". You should not see your service have more than 2 instances\containers running just for redundancy
Clouds\k8s makes our lives easier and makes us lazy to hard optimize services. We always can scale things. Sure. It just means you pay not to developers but to clouds or to devops engineers.
Was added to project as a DevOps. Spent a lot of time to just figure out why all services work slow. Sure if developers even can code well they don't give a lot of attention on a basic things like in previous twit - GC