591–600 of 605 posts
There is one hard wall that stops very old clients from connecting: Not supporting a new enough version of TLS. TLS 1.2 is from 2008, and TLS 1.3 is from 2018. Web browsers older than 2008 can't connect to modern websites since TLS 1.0 and 1.1 were deprecated from web servers in 2021.
TLS 1.2, the standard, may be from 2008 but support for it in browsers did not start to appear until around 2013.
Sadly, this is the story of nearly every React project I've reluctantly inherited. In my experience, it's because React is not opinionated like its peers Vue and Svelte. So, a bunch of devs will use something for state management and and another team will use something else completely. Eventually both teams leave after making a mess. But, if you look at the graphs and numbers that MBAs chase, they will all look like…
If there is one thing developers hate its admitting that something is too complex. They feel it makes them look dumb, and for some it is perhaps some form of job security. You don't have to have a technical discussion whether or not React is too complex, you just have to look at the average website created with it.
Bingo. And that's one of the reasons you will face a lot of friction whenever any discussion surrounding this comes up.
Earlier quoted context omitted.
Yes, there 'should' be a trail. And there's someone and a process to check that trail. And a process to find the issues, correctly so, and fix, and do all that on a timely basis, and reimburse the person for damages, ... PS: I have actually suffered through some of this, badly so, though in an unrelated setting. It comes back to which system is more robust/mistake-proof and more practically recoverable.
Sure, but that's how Governments worked for decades before widespread access to laptops / mobile phones...
However, I thought more about this and I now agree to your position. Till there is still a significant enough percentage population that is not setup to use the new approaches (digitization/Internet in the example at hand), the older methods need to stick. Meanwhile, assuming the new approaches actually offer more value, there should be an appropriate push for moving the remaining population towards it.
Two failed React attempts before this. Shows how chasing fancy frameworks over solid basics can cost millions. Simple HTML wins for public services every time.
but it's not simple html, it's a npm-package
Earlier quoted context omitted.
Oh, I know it's not the point but I find it a bit disingenuous going from iPhone base model to the Pro in the last 3 years and still comparing to the base model Samsung S series. Though maybe I'm missing something non obvious. But yeah, generally I've seen a better experience buying used phones (in good condition) instead of budget/cheap new ones.
The data is from my blog series, the latest installment of which is here: https://infrequently.org/2025/11/performance-inequality-gap-... The top two lines are the fastest devices available in the iOS and Android ecosystems each year, and when using Samsung S-series devices, I have made sure to pick the faster of the Qualcomm vs. Samsung Semi parts (both are used historically, but Qualcomm is most prevalent in the US…
I also saw you addressed in your blog post the growing market for refurbished phones and in the last year or so I've noticed a similar thing in Romania where a e-commerce giant is involved with a company that refurbishes and resells old user devices to try and corner a big piece of the pre-owned (second-hand) market where previously you'd be stuck hunting for good deals on the national Craigslist equivalent or searching for small-ish repair shops that sold refurbished devices.
Earlier quoted context omitted.
I just had one of these people, a contractor working for a state government, argue vocally with me in a meeting stating that "500 JavaScript requests is not a problem" for a single page. Un-cached, of course, despite there being a CDN in front of the site. You can't win against cargo-cult coders because they just assume you're from a different, competing cult. They have no concept of engineering or science, they have…
> argue vocally with me in a meeting stating that "500 JavaScript requests is not a problem" for a single page Where's the benchmark or at least the numbers? If not, that's not proof of anything. Nothing to argue about. I'd just laugh. > You can't win against cargo-cult coders You don't need to. Unless you're not in control or don't have influence then whatever. It shouldn't be about "winning". It's either some vote…
I like to fight this kind of asinine "push back" by simply reversing the time order:
Here's an app that does 5 CDN-cached requests of its JavaScript. Demonstrate why disabling the CDN cache and splitting that into 500 individual requests is better.
Earlier quoted context omitted.
Chase works with ad blockers, though. It doesn't work if you disable JavaScript...but it wasn't always this way! They had a mobile version of their online banking service at https://m.chase.com that was EXTREMELY FAST and did 85% of what you need to do in an online banking portal (check balances, transfer funds). They scrapped it when they moved to their current bloated monstrosity of the portal that they have today.…
i am unclear on if it's because of the adblocker (specifically i use ad nauseam which does block some JS. some.) or because of firefox. I can load it on edge every time it fails on firefox. last week, chase.com worked fine on firefox. the previous 15 months where i needed to log in, it did not. Someone at chase isn't checking their work on firefox.
It's just how i roll. it seems to bug a lot of people that i don't want to be bleeding edge. i don't particularly mind that.
Earlier quoted context omitted.
1. Presumably the team that made the previous app also thought they knew what they were doing. Presumably they were not hired on the assumption that they couldn't make a good app. 2. The design constraints had always existed, the previous app just failed to meet them.
1a. They may have thought they knew what they were doing, but their work product shows otherwise. 1b. They may have thought they knew what they were doing and spoke confidently enough to convince whoever was doing the acquisition, likely non-technical, of the same, but the bad hire and the bad hire’s work product shows that neither was the case. 2. Ideas merely exist. To be constraints, they must be enforced.
2. It was enforced, just at a higher level (expensive fines triggered by customer complaints). A good engineer broke down and actually applied the constraints in a preventative way.