Why do we insist on building cars to be safe in a collision when it would be so much nicer to not have accidents? Why do we build cancer treatment when not getting cancer is a much better option?
The article for example mentions MRI macines, aerospace engineering, fiber optics and semiconductors, so I guess it depends on if you want those things to still be available in a crisis
That does sound kinda minor? A worst-case scenario of a month or two without MRI machines or "aerospace engineering", whatever that means doesn't sound particularly scary. And that is making some pretty unrealistic assumptions like there is literally no helium, hospitals don't have private reserves that can last a few months and there are no replacement gasses or alternative options of any sort. And people can make do with limited fibre-optic or semiconductor manufacturing. We have crisises in various computer components every few years (I can think of HDD, RAM & GPU supply shocks over the last few years). Doesn't seem to be a major problem. A couple of months of disruption isn't a strategically interesting event.
If you're worried you can keep your own helium reserve? Then if there is an emergency and it turns out that you don't need an MRI you can sell the helium to whoever does and feel really good about your foresight.
I'm not seeing any need for a strategic reserve here. There aren't any strategic issues. It is a bit far-fetched that a helium shock will even lead to the end of MRIs.
Everyone also could keep their own supply of gas and their own batteries for electricity but it turns out that is not expensive and foolish compared to centralizing such backups.
A lot of people die every month. We're talking about a probability near-0 event where I imagine it'd be difficult to pick that deaths out from general background mortality - admittedly just based on the fact I don't recall anyone I know who needed a life-saving MRI but I know a few who died. That isn't much of a justification for a strategic helium reserve. Some level of risk just has to be tolerated, we can't afford to have a contingency for every possible hypothetical.
It's pretty easy to make up a reasonable sounding excuse for something you do for your own profit as a company. If they don't even provide any statistic on how frequent these scams are, it can be just words
Also, if your bank 2fa code is in your notifications, you should switch 2fa methods to something other than sms, or switch banks.
> So we should just accept that all apps must treat android notifications as a compromised communication channel?
Look, that's an OS issue, not an app distribution issue. If I could use the trusted, vetted software from F-Droid I wouldn't need to worry about this sort of attack.
yes - monorepo. Git (and associated service providers) have a lot of work to do to scale out to large organizations working in a single code base.
"Better Merge Conflicts" is not on this list.
Although I'm sympathetic to the problem, and I've personally worked on "Merge Conflicts at Scale". Some of what's being suggested here is interesting. I question if it makes a material difference in the "age of ai", where an AI can probably go figure out enough context to "figure things out".
Merge conflict avoidance is not a monorepo issue. In fact, the whole purpose of a monorepo is to avoid these sorts of issues, so it's not surprising.
Merge conflict hell shows up when, for example, you maintain a long-lived feature branch periodically rebased against an indifferent upstream that has its own development priorities.
I've maintained a project for years that was in this sort of situation. About ~100 commits on top of upstream, but invasive ones that touched nearly every file. Every six months upstream did a new tagged release. It would take me literally weeks of effort to rebase our patches on top, as nearly every commit triggered its own merge conflict hell.
You don't encounter these sorts of issues in a monorepo.
The most frustrating thing with the "Atomic architecture" bit with tiny packages is how obviously stupid it is. Any borderline sane person should look at isOdd/isEven and see that it's an awful idea
Instead they've elevated it to a cultural pillar and think they've come up with a great innovation. It's like talking to antivaxers
It's because it has a smart-sounding name. Some people are shallow and performative; some nice-looking blog post says they can have "atomic architecture", then the trend starts and everybody wants to show how enlightened they are.
Atomic packages brings more money to the creators.
If you have two useful packages it's hard to ask for money, even if they're used by Babel or some popular React dependency.
If you have 900 packages that are transitive dependencies the same couple deps above, it's way easier to get sponsorship. This is a way to advertise themselves: "I maintain 1000 packages".
The first guy that did this in a not-nice way was a marketing/salesperson and has mentioned that they did on purpose to launch their dev career.
TLDR: This is just some weird ass pyramid thing to get Github sponsors or clout.
A third argument is that it was because of aliens from the planet Blotrox Prime. But I suppose without evidence we'll just have to accept that all three theories are equally probable.
Interesting how you decided to switch to hyperbole instead of providing evidence for your claim. Backing up your viewpoint would have easily shut me down, putting the ball in my court to do the same. Instead you gave a knee-jerk childish response.
Nope. Just a reductio as absurdum that you decided to counter by asking that I maintain higher standards of debate than you.
The notion that atomic architecture came about because people are stupid and performative is not really useful. Its fairly misanthropic and begs the question why it became so prevalent in JS specifically.
The philosophy was kinda refreshing in the early days. There was a really low barrier to publishing and people were encouraged to build and share tools rather than hoard things. It was probably somewhat responsible for the success of npm and the node ecosystem, especially given the paltry standard lib.
Of course, like most things, when taken to an extreme it becomes absurd and you end up with isOdd.
I think the issue is that the JavaScript ecosystem is so large that even the strangest extremes manage to survive. Even if they resonate with just 0.1% of developers, that’s still a lot of developers.
The added problem with the atomic approach is that it makes it very easy for these fringes to spread throughout the ecosystem. Mostly through carelessness, and transitive dependencies.
I've seen some juniors writing risoni code like that. They've heard that you shouldn't write big functions, so obviously they forcefully split things until they can't be split anymore.
Bose QuietComfort Ultra 2 at least just allows varying levels of passthrough. You can have noise cancelling or noise cancelling + sound from the outside mike. You cannot have noise-cancelling off for better battery life or to cope with windy conditions
They're awful in several other ways too, which is sad for what should be their flagship model
reply