I think people are mainly confused because the AirPod Pros are quite competitively priced compared to other higher end offerings. The Max are so far off the market that it doesn't seem to make any sense and it seems unlikely that apple couldn't make up for lost margins with higher volume. Maybe they just literally can't/don't want to produce many of the Max and price them accordingly.
I'm delighted to see somebody else who refuses to use the pompous syntax Apple promote for these things. Entire thread full of people uncritically accepting that they should be referred to in actual conversation as AirPods Max as if it's a term that deserves more grammatical respect than most of them would give to attorneys general.
> This system was one of the oldest IT systems in NAV, and ran in production for 51 years, from when the National Insurance Scheme was introduced in 1967. In January 2018, Presys was put into production, which together with Pesys became the successor to DSF. At that point, DSF was also shut down.
The system is written in PL/I.
It's like the Apollo 11 code, but for social services.
We have an airtag in our cargo bike, connected to our ipad (neither my wife nor I have an Iphone). It never actually makes a sound and we can reliably track on the ipad. what gives? I never thought about this.
Except of course rollout will not be atomic anyway and making changes in a single commit might lead Devs to make changes without thinking about backwards compat
Even if the rollout was atomic to the servers, you will still have old clients with cached old front ends talking to updated front ends. Depending on the importance of the changes in question, you can sometimes accept breakage or force a full UI refresh. But that should be a conscious decision. It’s better to support old clients as the same time as new clients and deprecate the old behavior and remove it over time. Likewise, if there’s a critical change where you can’t risk new front ends breaking when talking to old front ends (what if you had to rollback), you can often deploy support for new changes, and activate the UI changes in a subsequent release or with a feature flag.
I think it’s better to always ask your devs to be concerned about backwards compatibility, and sometimes forwards compatibility, and to add test suites if possible to monitor for unexpected incompatible changes.
Rollout should be within a minute. Let's say you ship one thing a day and 1/3 things involve a backwards-incompatible api change. That's 1 minute of breakage per 3 days. Aka it's broken 0.02% of the time. Life is too short to worry about such things
You might have old clients for several hours, days or forever(mobile). This has to be taken into account, for example by aggressively forcing updates which can be annoying for users, especially if their hardware doesn't support updating.
Do you have a pixel? On Samsung you cannot share WiFi, Hotspot only works with mobile connections. I learners above that this is possible with pixel phones, makes me want to get one...
Yes, Pixels can definitely do that (I use Graphene). It’s incredible that iPhones are so expensive and yet so limited (can’t share WiFi, terrible file browser…)
Id argue that this isn't so much a fault of the MCP spec but how 95% of AI 'engineers' have no engineering background. MCP is just an OpenAPI spec. It's the same as any other API. If you are exposing sensitive data without any authz/n that's on the developer.
I mean given the computing devices most people use are you suggesting a large majority of the population switches to ethernet adapter's for their tablets and phones?
No, not remotely? I don’t know why folks jump to that (wrongest) conclusion whenever someone mentions ethernet being made a requirement in construction or use.
Can tablets and phones use ethernet? Yes! Should they? Perhaps for a fixed installation, but otherwise no, because that’s not their primary role? Same goes for laptops: if it’s stationary, plug it in; if not, WiFi is fine.
The goal is to shift traffic where reasonable and practical onto wired networks. Desktops, laptops, set top boxes, streaming rigs, control panels, SBCs, game consoles, the list goes on. The only “Wi-Fi required” devices are really just laptops, phones, tablets, watches, and similarly high-mobility devices.
Having to blast wifi through an entire building is part of the problem. If transceivers only need enough power to go a foot or three from an ethernet port with a wifi dongle on it, the problem is solved.
See also: cell phones having to boost power for more distant towers.
As things are, every device has to scream to be heard.
reply