I think you'll be very surprised at how successful this is.
Do you remember the Microsoft prototype for a folding tablet? It would have two different apps running, and you could use the spine to pull data between them, a kind of visual clipboard.
I don't think that workflow is as important now, but having two apps open (one on each side of a device) is going to be killer, and it's something they're clearly hinting at with some of their asks for developers (and with their iPad OS).
I finally pulled the trigger after being in tech for 21 years. 10 years at a FAANG.
I simply can’t handle the performative Machiavellian culture anymore.
I could play that game for longer, but I don’t want to. All I want is to build cool and ambitious things without any of the theatrics.
I don’t want to go offline. I just want to live a normal, modern, and peaceful life. I would go nuts without all of the comfort of modern tech, especially the high speed broadband.
I think the billionaire class will expand BNPL type products so everyone will stay in-debt forever. And expand gig economy so everyone can stay "employed" forever.
Employed doing what? At some point, we'll have autonomous tractors, autonomous techs to fix those tractors, autonomous cars and delivery vehicles, robot plumbers, AI doing information work.
If we reach a point where all labor is automated, then realistically we should have achieved post scarcity utopia at that point. If not, the only realistic options are some form of UBI, or state sponsored make-work. Grow the bureaucracy, the state employs people to do BS fake jobs. Audits, compliance, oversight. Middle-management type work just to continue the illusion of a work for income social contract.
I never quite understand why /mcp endpoint is needed.
You can still keep using Rest API with swagger docs and tell the AI to read the swagger docs. It's the same thing. The entire Rest API specification is a lot more flexible than the JSON RPC format /mcp uses.
rest api with swagger docs requires one extra hop to pull the details necessary to interact with the api, and it pollutes context in a similar way as mcp.
ideally what you would have is skills + scripts that the agent can load progressively to interact with the api
or even better: a single cli tool the agent is aware of, and which combines `--help` output with `tldr` tips, when the command is incomplete, and prints out helpful error messages when the incantation is wrong
It looks great. If the price is good, I think it will sell well. The only thing holding it back is Google’s own reputation of canceling things so rapidly.
> People used to proudly use Vi to write code. But now IDE is commonplace.
this is funny because I met many software developers who did not have a, let's call it "Unix hacker background", who only ever used Git through an IDE. Now sometimes when they need to log into some system and use the commandline they are lost because they are neither familiar with a shell environment (readline and stuff) nor the Git commands.
I guess you can work that way but that's not for me, because I want to understand stuff. Of course I also use an IDE but I don't rely on it.
I usually am a pro Apple consumer but how many high end users actually want this form factor?
reply