top | item 46975112

MDST Engine: run GGUF models in the browser with WebGPU/WASM

33 points| vmirnv | 18 days ago |mdst.app

12 comments

order

vmirnv|18 days ago

Hi Hacker News!

Just in case (a common question): we are planning to open-source the MDST WebGPU engine, but please give us some time to polish it and get it ready for a harsh oss community.

Meanwhile, you can skip the waiting list with this invite: hackernews_Eq1RDox

WebGPU technology gives us a way to provide truly free and accessible user tiers for everyone without burning investor capital or doing rug pulls.

If you have any questions, I’d love to answer them.

evanjrowley|14 days ago

Is there a way to read more blog posts? I couldn't find a "Blog" area from your site's navigation menu.

MDST is exciting and so was this blog post. I'd like to read more.

vmirnv|14 days ago

it was our first post, sorry, we are a small team of ds and developers, and this is our first step outside of closed beta. you can follow us on twitter and telegram for more often updates (links are in the blog).

Ms-J|15 days ago

While it is nice that you say you will eventually open source it, I'm concerned that there is a need for an account to use the free options. Most software could be used great without an account and collecting all of our private data.

Also, since we are forced to sign in, there is no option to use the website for auth and only Google or Github, both not the best choices.

vmirnv|15 days ago

You're absolutely right (lol, I'm talking like gpt4o now), after initial feedback we found that there is a better way to present webgpu gguf engine without registration — some kinda webgpu gguf playground and we are currently building it!

(if you have any neat ideas — I would love to hear it)

b00twhy|14 days ago

But why?

In this synthesized machine states era do I want to still run a bloated, buggy web browser?

I think I will keep working on synthesizing a replacement for the desktop metaphor of a blank viewport/canvas and sampling from a model of vision data, tweaking at the edge when labels are missing or wrong, edges don't align, saving it back to model

Think "boot to Blender" or Unreal Engine, synthesizing desktop and text files and such inside that environment

There is increasingly little reason to import all the state of legacy software beyond a minimal Linux distribution

Prompt to binary is on the way, skipping the generation of the intermediary code layer altogether

Code is legacy technology from the 1950s era of using machines; arbitrary syntax for labeling with human context the use case of a memory address

No reason the labeling has to be at the machine level. That can be vectors and labels of human value applied right to what's shown onscreen

What tech people should be focused on is political action that keeps hardware open and models open and not locked behind data center.

Software dev as we knew it is already over technology wise, social acceptance has yet to propagate, but social acceptance is an eventually consistent system. It’ll happen

bigbadfeline|14 days ago

> In this synthesized machine states era do I want to still run a bloated, buggy web browser?

I do. The browser is indispensable, at least for now, and it's much better to keep improving it for the age of AI than to jump to fairy tails and unproven replacement technologies.

> What tech people should be focused on is political action that keeps hardware open and models open and not locked behind data center.

And while they're working on this, you're going to do what exactly? You made a lot of forward looking claims that have nothing to do with the present reality, you just forgot to present any realistic vision about how to get there.

If you can't imagine procuring any those pink unicorns yourself why do you plead with others to deliver them to you? It just doesn't add up.