There is
though currently much worse
1,253 karma · joined May 9, 2014
There is
though currently much worse
The era of ridiculous sounding last words came to an end
> The new biomaterial comprises two components: a bioactive peptide that binds to transforming growth factor beta-1 (TGFb-1) — an essential protein for cartilage growth and maintenance — and modified hyaluronic acid, a natural polysaccharide present in cartilage and the lubricating synovial fluid in joints.
and application:
> the new material could be applied to joints during open-joint or arthroscopic surgeries. The current standard of care is microfracture surgery, during which surgeons create tiny fractures in the underlying bone to induce new cartilage growth.
How, "Dynamic Tool Discovery"? Has this been codified anywhere? I've only see somewhat hacky implementations of this idea
https://github.com/modelcontextprotocol/modelcontextprotocol...
Or are you talking about the pressure being on the client/harnesses as in,
https://platform.claude.com/docs/en/agents-and-tools/tool-us...
Nuclear bomb?
I assumed this was going to be a functional evolutionary algorithm to make an efficient shape, it's just an image generator and an artist in the loop
The 11labs agent product is promising but very buggy, I was glad to see some of those issues in your implementation as well. The agent often drops out and comes back randomly after long stretches of silence. They also seem to be running some kind of half-functional censor on the llm output when used with Gemini 1.5. It also bills 500 credits for any time < 1 minute, not the aggregate use.
My wish is for one UI that specializes in one database like Postgres. These database engines are so powerful now, but generalist UIs can never take advantage of the specializations. Directus et al have the same problem.
You want metadata on posts, you install ACF. You want to filter on that metadata, good luck if it's over a couple filters simultaneously, the SQL queries will time out. Take a look at WP's insane schema to figure that one out.
Gutenberg promises to have WYSIWYG editable React components, which is a big deal, but they made insane decisions like storing the attributes in HTML, rendering HTML in the database, and requiring component developers to keep an array of deprecated changes when they want to modify anything on the component.
There are some people trying to untangle Wordpress by refactoring and bolting Laravel onto it[1], but every layer is just a nightmare; the authors of different parts can barely assess why things randomly break.
You might find WP appealing for the plugin ecosystem, but the plugins are completely random in implementation, so you're likely to get a bloated scramble of CSS and JS pushed to your users.
I moved to Directus and Astro, but I would probably use a Laravel-based CMS like October or Statamic for more generalized PHP deployment.
[1]: https://roots.io/