This looks a bit similar to the binrw crate in rust, which I'm a very big fan of. Here is a sample of it parsing a chunk in a WAV file.
Here's a WAV format chunk parser: github.com/EmNudge/insp...
Kind of insane: integrityindex.us does not show up on Google and Gemini refuses to acknowledge it is a working or legit or existing website.
ChatGPT and Bing get it immediately. I think Google is forcibly down ranking it?
It's vibe coded, but the code samples are tested in CI - most of this should be accurate.
I also made most of the code blocks editable and hooked up to my LSP, so you can see how changes affect things.
Added the playground to a subpage of the docs wat-docs.emnudge.dev/playground/ - felt fitting
Made wat-docs.emnudge.dev
I don't know of another WASM docs website, which is very strange.
You basically just have specifications, some written in LaTeX for some reason. MDN's guide is probably the closest you get developer.mozilla.org/en-US/docs/W...
Lesson here being that you can build rather complicated AND useful tools without writing a line of code yourself.
It does take someone who knows what they're doing, though. Which is fine, it means I'm not fully divorced from the code, just sitting at a higher abstraction layer more often.
This is the project that motivated building github.com/EmNudge/wat-... which is also vibecoded and itself best-in-class
This is kinda nuts
I vibecoded a thing I think is mildly impressive github.com/EmNudge/wat-...
Pure WAT implementation of FFT. Benchmarked against best-in-class alternatives which is either beats or is at parity with.
good read, echoes some of my thoughts.
Accidentally blogged about the same thing yesterday emnudge.dev/notes/the-mu...
Most programmers are terrible at writing, so surely you can do good work without this skill.
It's just such a benefit to evolving your capabilities and career that I think it's worth taking serious time to work on.
Most under-looked skill of great programmers: writing
Echoes some recent thoughts I hear from @oxide.computer - some of the best programmers I've worked with are excellent at communicating. Getting good at this is a great boon to your career.
Writing has helped me better express myself.
👀 what are you building there
Yes, every time. Something that allows relative selecting.
The ID model creates issues in the component model, forcing us to rely on some PRNG ID generator. With components, you cannot guarantee only one instance of the element.
Was very hard to read this as ironic at first because I've seen almost 1:1 this mentioned unironically.
serious question - what do you make of battery fires?
This is less about personal use of EVs and more about their existence in general. Am I overblowing the risks here? Are EV car fires not significantly worse than non-EV car fires?
Would like to be convinced otherwise.
You may be wondering what the difference is between this and voice-to-text + a regular LLM.
Those don't handle language switching well. I've tried.
It feels obvious since that's kind of why they exist, but LLMs are awesome for language learning.
A missing piece for me is getting ChatGPT or Gemini level voice chat offline.
There are dozens of ollama clients for the non-multi-modal LLMs. Would be awesome to get this for voice.
Solid uses this pretty heavily for props, right?
That's been one of the major footguns for me, but it at least is easy to learn and lint for.
You mentioned that they might have to sell Chrome to Perplexity. I don't think they can afford it and the judge wouldn't mandate a specific company.
They couldn't sell to another tech giant (I assume), so the next up seems to be a VC of some kind with lots of cash reserves.
Do you think Perplexity is a more likely sell than some VC? As rich as Perplexity is, I don't know that they have enough cash reserves to compete.
to clarify once more, you could recreate this API in JS. Nothing here seems language specific.
There are no new language constructs or token in this code snippet.
Or at least, that's what it seems.
If that is true, the `.async()` marker seems superfluous.
Sure, but this is done by the `await`, not the `async`. Defining something as `async` is akin to marking it as a generator function that pulls and pushes and yields control.
But the runtime is the `.await()`
I could imagine some reasons to have a `.async()` API, but none very convincing.
What is async doing? It seems like we can just call the function directly where we .await() it.
If the parallel here is a generator function, you can have the same kind of behavior. Is the benefit that you get to pass it with its params without calling it early?
Honestly I must be missing something because I'm not even sure why calling `.async()` is at all necessary here. I'll bet some long blog post will clear this up for me.
So this is basically a generator function with a slightly different API. The words async/await feel misplaced here.
Async in every implementation is basically a generator function as well, but with a more implicit API. Calling it async feels weird.
I would love recruiters and hiring managers to stop saying they were "impressed by my background" when they just mean I worked at a company they like. There is nothing impressive about this. You sound silly.
My work outside of my employment is publicly visible. Be impressed by my rants.