26,018 karma · joined February 18, 2008
pixels are pixels, and no browser implements them as a fractional-inch measurement. in every actual implementation i'm aware of, they're a hardware based unit.
if the user's operating system is configured to draw pixels at a 1:1 ratio, your pixels will be drawn at a 1:1 ratio. if the user's operating system is configured to draw pixels at a 2:1 or 3:1 ratio, you as a web developer don't get to override that, but you're still addressing pixels directly. if you want to write software that manages the user's hardware directly without giving them options to override it, the web is probably not the right platform for you.
that is basically what MCP is. except it answers all the questions that your version handwaves away - how often do you get a fresh copy, how do you describe the relevant tool calls, how are the tools organized, and how does auth work.
for agents, they're essentially the same thing - remote endpoints, and instructions on how to call those endpoints. what MCP brings is centralized updating and distribution of the instructions, and a promise that the skill and the REST api won't be out of sync with each other.
the one thing that skill.md+REST doesn't solve is how you get that skill.md to somebody else's computer, and how you ship an update to somebody else's computer once they've got a copy of the skill. if that's a problem you need to solve, you can either start inventing skill.md distribution protocols, or you can just use MCP.
Publishers would rather have the chance at $10 than give up the chance at $10 for 10c. And readers don’t want to be thinking about their credit balance every time they read an article.
use what you're familiar with, until it stops working. then use something else. postgres just goes a lot further than a lot of other tools before you get to the "use something else" phase. and postgres is the database a lot of people are familiar with.
this is framed as amazon doing something wrong, but it sounds like what's actually happening is that his marketer is wasting money. of course amazon is going to accept money if you give it to them for the things they're already doing for free. why shouldn't they?
They're only a better value if you're paying API rates
I just think the whole “moat” discourse is silly. OpenAI and Anthropic’s success depends on the same thing every business’s success depends on: their customer base, and their continued delivery of services their customers want to pay for. Not their tech or their compute or anything else. They have no moat because moats aren’t a thing.
If compute is the moat, that doesn’t really make their position any less precarious.
the biggest winner in that scenario would be ai providers, who suddenly have a capable model that they can serve much more efficiently. and the incumbents have a whole lot of compute. wouldn't anthropic and openAI just start offering that open weights model at prices that nobody else could compete with?
the value of openrouter is it offers centralized billing. you can route your calls to any provider you want, test a whole bunch of models against each other, and you just get one bill from openrouter. switching to a new model, or a new provider of the same model, doesn't mean setting up a new billing account with a new provider.
unlike everybody else in this comment section, i like the two-mode toggle. but that's just my opinion. without user testing numbers, an article saying "users like this better" is useless.
but openrouter says they don't expect the price to change other than through the deepseek api, other people hosting the same model will keep charging the same price.
and at the same time, it feels like all the AI companies - not just elon - are doing everything they can to burn trust.
geogrid is orders of magnitude easier and quicker to install.
this feels like "make no mistakes" level of prompting. reliable software isn't as simple as making it reliable, it's about choosing the trade-offs in the areas that don't matter as much as the areas that do. if you keep prompting the LLM to make your software more robust it will keep giving you things to do. they aren't all good things. eventually you'll end up needing kubernetes to run a calculator app.