Love that page styling.

I'm building a simple model inference platform: https://marigold.run

Seems everyone is building an inference platform lately, but this one is mine! And I'm enjoying it...!

With new tools (i.e., LLMs) it feels like software engineering is moving to an assembly process.

The best engineers will have an awareness of overall problem, architecture, how pieces should fit together and what changes when the fits are made.

The top-tier will be able to adjust components, and identify gaps which can be filled by newly created, but properly shaped components to create new emergent properties from the combinations.

This has always been a requirement, but intertwined with the expression of the vision by coding. Are those two things really separate? I don't think people can be architects without coding, but I'm an old man with old ideas!

A ban on desktop PC components over a certain power threshold (300W) or PSUs would definitely affect local AI, and Europe is not a big enough market, nor has it's own internal supply chains to offer alternatives.

This has been done in the EU/UK in the past (hoovers/vacuum cleaners) so the mechanism exists.

I'm in the UK and support your direction.

> would definitely affect local AI

And not only. Given your example with 300W, it will affect even things like (somewhat advanced) home servers, (mostly) personal self-hosting machines and even just gaming PCs. That would affect way too much, if I understood your thought correctly.

yes, that's what I thought.

"You got a loicense for that PSU?" is my biggest fear!

And it is focussed on social networks, which require an email address, which usually implies a device.

But instead of inserting controls around email addresses (as with paid services) or devices (as with contraband), the requirement is pushed to the application layer. It really makes no sense from a technical POV.

The US "product machine" is so strong. They really know how to do frictionless signup and vendor lock-in on the corporate side.

Can anyone explain how this ultrasound can see through the skull?

I've worked on ultrasound devices and data, the shadows from bone, and distortions caused by tissue types were very difficult. If this device can deal with those distortions it would already be useful for lung imaging.

lungs are much harder than brain and bones (the acoustic impedances of solids and liquids is more similar than solids/liquids vs air: air is very thin)

Yes, thank you. That's exactly where I am, and trying to gather some knowledge.

The power draw from the wall is especially important, because a spike across multiple devices at the same time can cause issues which are really difficult to debug.

Open weight and local hosting is far, far cheaper. In every respect. Even support is cheaper, over time.

However, it's difficult to sell this to businesses who want contracts and KPIs, not staff and commitments.

Regulated industries will favour the closed sources, either by choice or mandate. The interesting question is whether they will have better models, or worse models. History says they will receive a worse service, but continue anyway.

Cheaper until you factor in security and liability, which are going to get increasingly salient over time.

> Regulated industries will favour the closed sources, either by choice or mandate

Until your country will appear on naughty list of US administration because your local politician did something what mildly inconvenienced US oligarch

I've just made a milestone on my project, moving away from AWS (budget) to self-hosted and the local models are so much faster than in the past. Beyond LLMs, having embeddings, image, video, audio gen available is crazy.

Running locally is the bar; it's hard to make these things a service which scales.