1 player is enough to create tension on price when "don't buy it at all" is a comptetative option. By most accounts, Anthropic and OpenAI both lose to "just don't buy" when they try charging at cost.
Craftsmanship is not dead in other industries in the same way it is being talked about for software.
Sure, that cheap desk that arrived in a flat box and got assembled by me and a screwdriver was mass produced in a factory. But it's design had way more expert craftsmanship put into it than would ever be feasible for a bespoke product. High upfront design cost, then mass produced at a low marginal cost.
That had been the state of art for software from the beginning. When you download Firefox, there is no expert programmer carefully building you an artisinal web browser. There is a CDN server sitting in a data center somewhere copying bytes out of its cache for you.
One of the things AI us threatening to do is replace the CAPEX craftsmanship, which has not happened at scale in other industries.
What AI has had more success at it replacing low end "artisinal" software; which is a category that has thus far been so uneconomical is essentially doesn't exist.
In short, git has a 'create_ref_symlink' function that is replaced with a macro to '-1' on some build configurations. This means that any code which is conditioned on the success of create_ref_symlink would trigger a compiler warning when built with -Wunreachable-code. NOT_CONSTANT supresses this warning by preventing the compiler from realizing the code is unreachable. It also prevents the compiler from eliminating the dead code, but presumably that has only a negligable impact.
> For anyone seeking a legitimate source on the bluetooth device comments: you can listen to the KEWR Ramp/Company/Misc archive. Keep the date set to 2026-05-31 and the feed set to ramp/company/misc, but change the time to 0200-0230Z. Then, skip ahead to about 22:55
> Do you guys know what happened with that - uh what is that a - 7-6 on the left?
> There's a security detail out there. Someone had a bluetooth they named a certain four letter word; so they have to inspect the whole aircraft including the cargo area. The passengers have to evacuate.
Back when I was in middle school, we had "digital typewriters" that worked fine, and was brought out far more often than the laptop cart or computer lab.
One time pads are the only solution that is secure from an information theoretic perspective. In practice, however, that is not important. You would essentially be securing yourself against a weapon that no one has, and most experts think cannot actually exist.
I could imagine somewhere trying to make that the rule, but I have a hard time imagining that rule being enforceable.
At least for US federal taxes, losses do not need to be tied to revenue. As long as they occur in the same tax year, you can deduct. You can also carryover losses to future years, or pass them through to personal income deductions; but the rules there get more complicated.
At 8 layers of management (so 9 layers total, with the bottom rung being non-management), 3 reports per manager comes out to 6561 employers on the bottom rung. At 5 reports each, that 8 layers would give you over 300k at the bottom, an 10 each would give you 100m at the bottom.
Why does any of this imply they should become a regulated utility? This seems like a textbook case of the free market pushing prices down to cost. Having alternative revenue streams pushed that minimal price down; but even without that, there is no reason to think the market would have done anything other than push prices to the lowest level possible in that environment as well.
Bankcruptcy and corporate death in general are important. However, the details of how that is managed can vary wildly, and not all implementations are equal.
In this case, the bankcruptcy was handled by cancelling all flights with 1 day of notice. This level of ugliness is not necessary.
I think the death spiral breaks at step 3. Financially stable and literate people do not pay credit card interest. They pay off the full balance every month resulting in 0 interest payments. In cases where they need credit beyond the short term float the above gives you, they have access to lower interest loans.
These people also don't make the cards much money, so loosing them wouldn't have that much of an effect anyway.
People are used to living in highly regulated markets. When they go to a grocery store to buy lettuce, people don't stop to ask "what regulatory regime is this lettuce being sold under?". They just trust that food being sold in a food store will meet our societal standards for food. I can go to Amazon and order a raw steak for delivery, and still trust it will meet standards.
The situation with wellness apps is that they are a product that are designed specifically to exist outside of the regulatory regime that people associate with them.
That may be surprisingly difficult in Rust. We generally think of Option<T> using O to represent None. However, it can actually use any invalid value of T
Maybe I just haven't worked in enough start ups. But where I have worked, there are a lot of things stopping that. Most people don't have access to any production keys. For those that do, we have policies about how to manage them. Those policies go through audits. Our intranet goes through audits.
A production API key appearing on the wiki would be the second biggest security incident I have seen in almost a decade.
------
On the AI note, despite a massive investment in AI (including on-premesise models), we don't give the AI anything close to full access to the intranet because it is almost unimaginable how to square that with our data protection requirements. If the AI has access to something, you need to assume that all users of that AI have access to it. Even if the user themselves is allowed access with it, they will not be aware that the output is potentially tainted, and may share it with someone or thing that should not have access to it.
The closest I am aware of is clippy (`cargo clippy` in a standard Rust project will run it with default configurations).
Clippy is essentially a linter; and one of its checks catches cases where different enum variants have a significantly different size; with a suggestion to Box the larger variant.
Since this is just a linter, it doesn't actually have any knowledge of how frequently each variant is actually used. It also doesn't address the situation in the article at all.
Open source is driven by contributions. Most of the time, if someone wants a feature, implements the feature, and submits a reasonable PR to a project, that project will have the feature. In this case, the PR appears to have been written by someone who is not a regular SystemD contributor, and (through a bit of Googling) works for a FinTech company with no obvious interest. I can't comment on why that individual wanted to add support.
However, once someone added support, the question for SystemD is not if it is worth implementing, but if it is worth merging. At this point, it becomes a simple case of "the most intolerant wins". For people who care about complying with CA style laws, this feature is critical. For people who don't care, this feature is fine. I doubt it will even make it on mosts lists of SystemD feature bloat that most people don't care about.
This is the same reason a bunch of the food in your pantry is certified kosher. No one is going to not buy something because it is kosher. But if paying a thousand dollars a year to put a small circle-u symbol on the back of your box can increase sales by 1% among observant Jews, most companies are going to do it.