I started reading this out of curiosity, thinking: that's such a far fetched thought, I'm curious about what the author wants to say.
I think he makes a good point about execution vs. readability, and the actual need for the latter, drawing analogies to earlier abstractions.
I'm still skeptical about low level language generation (tbh, letting an LLM handle memory at this point of maturity feels scary to me.. leaks etc)... But overall very interesting writeup and many points that I agree with.
I believe they are arguing against vibe-coding categorically by pointing out that high-level programming languages are for human expression. It's a reductio ad absurdum against the logical conclusion that follows from vibe coding as a premise. If vibe coding is like a using a compiler, why not just translate English directly to machine code or lower level languages?
I haven't been actively monitoring for security vulnerabilities ever since I switched from system administration to software development a few decades back. These days, I just read news that talks about high profile vulnerabilities - I do see CVE a lot more than cert.
I switched from Samsung Galaxy (first S, then S3) to OnePlus years back, and I've been a happy camper.
I currently have an OnePlus 9, I've heard no so good (compared to previous) reviews of their newer models, but I'll cross that bridge when I get there. My current phone has been running great for multiple years, minimal bloatware, would recommend.
I have the 10 pro and although the camera is definitely an improvement over the 5 I used to own, the overall performance is about the same. I still have my 5, and use it a lot for POS stuff and it's great still. I even have a OnePlus 1 around and it still works decently although it struggles a little with some apps. That's a TEN year old phone.
I have a recent OnePlus and it's been excellent. I like it even more than the older ones I had, which is directionally quite different than my experience with Apple and Samsung.
I bought a Motorola G73 5G a few months ago, paid $160 for the 256GB variant including 25% VAT.
Compared to my primary phone, Samsung S21, it's a ridiculous amount of phone for the money.
But I find the default Google apps to be quite limited compared to Samsungs offerings. Google's calculator app has no unit conversion and a very bare-bones "scientific" mode. Google's file app has no way to search for files containing special characters, while Samsung's can do that just fine by using \ to escape the character.
I don't have a SIM in the Motorola as I just use it around the house, other is "work phone", so haven't tested the phone and messaging parts yet, but I recall Samsung were better there too several years ago when my SO had a Sony or something phone.
But yeah, seriously considering getting something else next time around.
Yeah, I'm honestly afraid to buy a new phone with all the horror stories. I still have my OnePlus 6T, Oxygen is fine but it seems like the ROM scene isn't what it use to be.
