Can't we really keep the IT without breaking news/we are all gonna die/sensationalist way of passing news?
316 karma · joined February 13, 2016
From (yuck!) JVM/Spring/Kotlin, through Go/TS/C# to C/C++.
Can't we really keep the IT without breaking news/we are all gonna die/sensationalist way of passing news?
Thanks to The Lord everytime someone discovers the vulnerability he reports it right to the owners/maintainers and there are no bad actors out there keeping it as secret and using for years.
I hope someone at big corp will be so bored one day that he'll just start releasing Win 10 updates after reverse engineering the mechanisms and we will get Win 10 support again.
The rule still alive and stands strong - every second Windows is just a crap. ME, Vista, 8 and now 11.
And yes, I know that by default chats are not E2E, that phone number has way too many effects on accounts etc. Still, UX and agencies interested in important people are more welcome than data selling, ad-based companies.
As to Rust - we all, hopefully, agree that it’s great language, but not for some startup making websites or Mongo based, boring backends. It’s great for the stable, system level products.
[1] https://web.archive.org/web/20260728013424/https://overpaid....
Also Mongo is catching up in the use case we have and it’s even more scary. We are all the time at the exact edge of Mongo scalability and I’m talking about very good, few-years-invested-in setup on NMVe that is really delicate…
One added value I see in senior knowing how things work is simple - in case of outage or business incidents (caused by incorrect logic produced by LLMs from even worse prompts or incomplete spec) senior can act faster and answer difficult questions live. Now we are going to have bunch of kids looking at „Hallucinating…” and „Crashing the prod…” status bar in CC CLI.
Maybe this is what’s gonna be acceptable and it’s just new world.
The other thing that bothers me - why not real stable, but maybe „too old, medieval” solution with Redis as the main source of through - without any sync with SQL at all in terms of stock… it worked in my previous job with much higher traffic (1000s/s). Yup, we ended up with app-side sharding, but it was stupid-simple.
I wonder if no one really thought there about rewrite that will still connect with all old dependencies with old protocols, but also will expose new kind of API that can be used by next rewritten block.
We also had mainframe, we used Oracle. It turned out that casual server is also reliable in long term and we restarted them only for upgrades of OS. Of course moving to some distributed, fault tolerant option also feels like good direction, but instead not-doing the perfect rewrite at once you can do it two/three step migration. Costs nowadays? You already fixed that.
The real competition is Apple Watch and for sport-intensive application Garmin wins because of battery and simplicity of usage in harder conditions.