I have the same feeling as 2010-2015 with the js ecosystem craziness. These half baked ideas. Please we need to stop, we don’t need extra layers of abstraction and tooling that is not really solving any problem, it’s just ego tripping to create something and to get GitHub stars.

▲

IanCal 5 days ago | parent | next [-]

I disagree. I think it’s worthwhile trying these things out to see what’s working and what isn’t. We can sit and think and discuss all we want but sometimes you need to build something and try.

▲

thrown-0825 5 days ago | parent | next [-]

none of it is working, MIT just released a paper showing that the overwhelming majority of orgs adopting llm workflows have seen no benefit

	▲	__MatrixMan__ 4 days ago \| parent [-]
		I think that the overwhelming majority of orgs are too inflexible to just insert LLM access, step back, and ask of it was an improvement. I think you're more likely to see an effect if you can somehow capture how far a solo founder gets before they need to bring on the second employee. Because LLMs aren't better than me at my job, but they are better than me at many jobs which I can tolerate being done poorly. If there is a significant technological shift, it'll be when those startups start outperforming the ones for which LLMs weren't available at the start.

▲

donperignon 4 days ago | parent | prev [-]

nah, i am too old, i already know that this is not useful and it will generate security issues in the short term.

▲

phist_mcgee 4 days ago | parent [-]

Wow, must be amazing to be the first omniscient human being!

	▲	donperignon 4 days ago \| parent [-]
		It’s called experience. Never say i know everything. I know this is hype nonsense that’s all. Thank me later.

▲

razvi0211 4 days ago | parent | prev | next [-]

Right now theres is only one option available for people creating agents, that lets the users of those agents add capabilities for the agents through tools. Its MCP. And to be honest, its not great, because its very opinionated, and requires an internet-wide infrastructure rebuild. UTCP is the only other alternative. And it takes a light-weight approach, that instead of forcing extra abstraction layers, uses existing protocols

▲

falcor84 4 days ago | parent | prev | next [-]

What's your issue with "half baked ideas"? Would you prefer that we go back to the 80s when everyone baked in a garage and only released fully-baked code? I don't remember things being better then.

And as for the js ecosystem craziness; while I agree that we went through a lot of craziness, I think it was necessary to arrive at the current relative stability around React and a handful of other frameworks in conversation with it. React in particular was originally released in 2013 and definitely benefitted from baking outside in the sun since then.

▲

5 days ago | parent | prev | next [-]

[deleted]

▲

TZubiri 5 days ago | parent | prev [-]

Maybe we can release a buzzword thing called Tool Calling Protocol. And it's just TCP.

Or Contextual Shared Variables

Or eXecution Model Language

or..

	▲	franky47 5 days ago \| parent \| next [-]
		Context Sharing System and Heuristic Transformers Machine Learning are also promising.
	▲	taneq 5 days ago \| parent \| prev \| next [-]
		Damn these Tool-related Language Additions.
	▲	Razengan 5 days ago \| parent \| prev [-]
		Please fund my Extensible eXpertise Enhancements