I don't see how. Anyone can buy electricity without any intervention from the government. An intervention is an action that changes what would happen by default.
16,431 karma · joined April 14, 2007
I don't see how. Anyone can buy electricity without any intervention from the government. An intervention is an action that changes what would happen by default.
Not arbitrarily banning companies from buying a product from a supplier doesn't meet my definition of the term "subsidy".
I think the way this could work is by linking certain capabilities to MDM or a developer program membership. Organisations and people who really need it would still be able to get it but regular users would not.
E.g., the iPhone 15, released 3 years ago, doesn't get Apple Intelligence because it has just 6GB of RAM.
I wouldn't buy a device that is already at the very lowest end of supported hardware the day it's released. It could cut the years of meaningful OS upgrades by half or perhaps even by two thirds.
It's uneconomical.
The problem is that neither you nor the computer knows what 80% is without occasionally charging to 100%.
They may well decide not to chase customers for small unpaid amounts. But that's not something you should rely on as the issue is with large amounts.
None of this has anything to do with invoicing, but I would be surprised if they didn't issue invoices to all US customers.
That's not a solution because not paying your debts doesn't make your debts go away.
I get that this is not 10 years support for ChromeOS. But it is 10 years of supported software upgrades for these devices.
Perhaps the real issue is not the OS that runs on the devices themselves but support for the existing device management approach.
But that's not the real issue with CAPTCHAs or with a lot of other checks that companies do.
E.g., Apple does ID checks when you create a developer account. I would love to see the statistics, but anecdotally the overwhelming share of failed checks followed by "piss off we're not talking to you any longer" occurs with non-US IDs or types of IDs that are less common in the US.
Access to global infrastructures is very biased, I believe, and getting more biased. It's not always the US's fault though. The world is fracturing.
If companies avoid using software governed by such licenses then the overall impact is negative in my opinion, because it will lead to competing and diverging clean room clones that just split the community and the ecosystem.
I don't really understand why a well designed sandbox and permissions system doesn't solve the problem.
Only a handful of companies can make high end memory, semiconductors and semiconductor equipment. And some of them are wary of creating overcapacity down the line. Creating new capacity takes years and creating a competitor to any of these companies takes even longer, even when the incentives (high prices) exist.
So it's absolutely possible that consumers change behaviour before a sufficient supply side response arrives.
Demand destruction is a market response as well.
AI has greatly increased the number of security bugs found on a weekly basis (which is great) and we're getting one of those one-shotted and then immediately abandoned open source "projects" every day (which is useless).
And yet there is no indication that any of this new software development capacity is going into improving the quality and efficiency of the software we use on a daily basis.
Why is widely used professional software not getting better and more efficient if bug fixing is supposedly so much cheaper now? Is it not worth putting any effort into optimisation at all?
I think the reason could be that AI can only do more of what we have done manually before, i.e. more lowest common denominator code.
Or am I just too impatient and this is all coming?
Absolutely, but the context was small online forums. I don't disagree with the gist of your general criticism.
It's bad enough but not quite as bad as you claim. Article 19 of the DSA exempts small websites from the most onerous and expensive rules that big platforms have to comply with.
A one-off retroactive wealth tax is a rather questionable form of taxation even if (like myself) you are in favour of looking for ways to tax the super rich more effectively.
When I read about these one-off wealth taxes I find one thing really astonishing. The argument against wealth taxes in general is that people would change their behaviour, which would reduce the tax take over time. That's certainly true.
But then left wing economists believe that imposing it retroactively and calling it a "one-off" does not change people's behaviour. Technically, it cannot change their behaviour with respect to this specific taxation event.
But I find it utterly naive to believe that this sort of hit and run taxation will not change people's behaviour in other ways that would reduce tax revenues.
No one in their right mind would ever believe that a tax that brings in $100bn over 5 years will not have to be replaced by some other tax paid by the same group or by the somewhat less well off who decided to stay.
Not just in child mode, because child mode would only exist in compliant operating systems. It would not exist in all Linux or Android distributions for instance.
So governments would have collude with or regulate hardware vendors to control and certify what can run on the hardware available in the country.
This would be a highly centralised system with the potential the become tyrannical.
Would this not immediately lead to demands for hardware makers to prevent the installation of non-compliant operating systems?
I'm a bit surprised about the scalability case against a simpler solution. This is not about Shopify's scale. We're talking about contention for a specific SKU of a specific seller at a specific warehouse location.
How many shopping carts are competing for a single SKU at the payment stage at peak hours? Can this really be too much lock contention for a single database row?
I realise Shopify engineers are neither stupid nor inexperienced. Hence my surprise. I would have liked to hear more about that specific problem.
The author uses "server" as a role. So "my server is a phone now" translates to "the server role in my setup is now played by a phone".
Maybe this is just a rewording of what you said. You clearly know a lot more than me about linguistics.
In my view, the MCP should be part of the specification. It should expresses intended actions and/or restrictions while the code generated and executed by the LLM is an implementation detail.
This distinction is completely obvious in some cases such as using an external payment gateway. But let's consider a more borderline case.
Say your database is multi-tenant and every query absolutely must include a tenant_id. Now that doesn't necessarily mean you have to use MCP. It could be some command line tool that requires a tenant_id parameter.
But what you can't do is ask the LLM politely to please include a where clause for the tenant_id in any and all SQL statements it decides to generate. You have to impose some things deterministically and MCP is one way to do that.