If I recall, tom7 was at odds with chrome throwing up a warning at users trying to visit his website because he didn't support TLS on it. He wasn't against TLS. Calling them a TLS antivaxxer is not accurate.
I don't particularly like the terminology but, still, the attitude that TLS is just for "sensitive" websites, actions, or data is quite wrong. Even if you don't care about surveillance or ISP ad injection, you should care about infrastructure compromises and exploit injection. It sounds exotic and high effort but it's not. Unless you're personally auditing the coffee shop, airport, library, hotel, etc. Wi-Fi hardware and network before you connect, it could affect you easily. It's not even a choice that reasonably belongs in the hands of website owners, because they don't control all the paths from users back to them. And even residential and municipal ISP networks can get compromised, too, along with data centers and everything in between.
Yeah I kind of forgot exploit injection in the spur of the moment as of course I rushed to correct "someone on the internet".
ISP injecting ads is like annoying but if someone knows as much as Tom about TLS and totally skips rouge "airport wi-fi" can use his website to own someones else device that is the argument I should use for calling him or anyone else names on the internet.
I guess Kazakhstan example kind of covers it, because I do believe they would definetly deliver malicious payloads to dissidents.
There's a lot of lingering "SSL is just for your bank" sentiment out there. There are other ways to achieve integrity protection than using TLS, and there are even ways to use TLS without WebPKI, but nobody is putting any effort into any of them, and so TLS+WebPKI is the solution, and no website is exempt, because it is fundamentally an infrastructure problem.
While he does indeed have extensive knowledge of TLS/SSL. He still completely side steps points I wrote about and exaggerated many minor inconveniences. While PDF seems quite up to date it also picks on stuff that is not there anymore like green padlocks.
For some reason the article doesn't tell you the benchmark results, it just shows a screenshot.
It's 86 avg fps at 1920x800 (on medium?) but with upscaling on auto and frame generation. So who knows what the actual performance is like, since the render resolution even included in the results. And benchmarking with frame gen is a joke.
It kinda sucks though if you end up being a bad culture fit a couple times in a row. You end up being rejected on that basis alone. Forever. And there is nothing you can do about it, even of you are qualified for the jobs you apply for.
> I used to lose entire days trying to figure out some stupid error in a build chain or trying to upgrade through some library's breaking change.
Shouldn't the takeaway here be that depending on poorly maintained libraries is a risk? Code is a liability, not an asset. The habit that modern web developers inspired of depending on a new library for everything before ever thinkng about the problem first is bad actually. GenAI is a force multiplier for putting bandaids on bandaids and managing complexity, not extracting simplicity.
I don't use GenAI enough to lose entire days on it but when it "halucinates" fictional answers complete with broken citations and invented links that go nowhere, I am so glad I don't have to use this stuff for work.
Even well-supported, well-documented projects. I'm in the middle of a Spring Boot upgrade, which includes a collection of Hibernate updates. These are well-supported projects with -- theoretically -- fantastic documentation. But when something goes wrong, trawling them for what's happened is tedious and doesn't teach me much; you end up chasing down uncommon threads. The death of StackOverflow doesn't help much either. Previously, web searches might have found a commiserator, but that's all gone now.
A concrete example: during one of the updates, previously working code started throwing an OptimisticLockingException. Only in one place, annoyingly. My thought was that Hibernate was more strict about something it had previously been lenient about. I went down two or three false threads in the docs; I debugged the old version and the new version and read the guts of Hibernate but couldn't figure out why the persistence path had changed so significantly (or why it'd throw an OptimisticLock, it was saving a brand new row!). I was really struggling.
I set Opus on it, and it found the relevant section of the docs and zeroed in on the issue in the code: we were generating and setting an ID on a class that had an annotated @GeneratedValue. Old Hibernate said "whatever"; new Hibernate changed the persistence code so in this situation it calls `merge` instead of `save` (update rather than create AFAICT); there was no existing entity with the generated ID (of course, it's a new entity!); it fails.
While my hypothesis was broadly right, that _particular_ issue would've taken me days to chase down -- but the LLM correctly diagnosed in minutes with links to relevant documentation.
I vaguely hate LLMs, but this one saved me from a days long side quest that would've held up delivering the actual value of the project. I hope this doesn't sound like my brain is no longer functioning.
(edit -- reading it back I'm starting to write like one of the fucking things, which is probably the part of them I hate the absolute most)
My challenge for anyone who still thinks like this is pay for Claude or Chatgpt and use the thinking version of the latest model for every web search you would do. See how long it takes for it to make a mistake. I can't remember the last time and I use chatgpt quite a bit every day.
The model reads the webpage before it gives it to you so the odds of a stale link are effectively nil these days. And the odds of it being exactly what you were looking for are quite high.
The models are so much better than they were even a year ago, and it seems many people have an outdated view of their capabilities.
Your idea about web devs picking a package before thinking about the problem is legitimate. What would be cool is if you could have something help you break down both the problem and the packages to choose from (or if it's worth rolling your own). AI is fantastic at this.
As said banging your head against arcane documentation or the infuriating Internet [1] isn't using your brain. And skipping the mundane parts let's you use your higher functioning brain so much it's exhausting. Thinking on the harder problems all day is exactly where I want to be.
What an absolutely unnecessary analogy. The question is obviously more asking what is preferable about putting data centres in places where there is high competition with the population for power.
