First was just a test to see if I could. Then became a pretty fun test on iteration loops. How little I could be involved and what kind of instruction works best.

It's a language server for WAT, the webassembly text format. There are not many of these that exist in general, so it's very easy for this to claim the #1 spot.

It's a problem that has some clear correctness criteria so putting it in a loop with Claude Code on Opus 4.5 kept producing really nice results.

The repo includes a playground so you can see how it feels without needing to download anything. Check it out at https://wat-lsp.emnudge.dev/

Comments URL: https://news.ycombinator.com/item?id=46632943

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46447789

Points: 4

# Comments: 1

Stackblitz did this with Node (aka their Web Containers).

You could make a new project very quickly and prototype an idea. When finished, download it off the browser and deploy it.

There’s no free WiFi without requiring a phone number. It allows the government to connect internet users to real identities.

The way I’ve explained it is “unserious surprise” which also fits with this.

https://emnudge.dev/blog/a-grand-theory-of-humor/

And then software that does exist will often have bugs for Linux that are overlooked due to how small the market is.

I get onboarded to new projects sometimes with a bunch of local unstructured logs already set up. They come from different parts of the application at different layers - many without syntax highlighting. It's hard to make sense of things.

In contrast, something like your browser's dev console allows filtering, highlighting, and inspection of "unstructured" logs. I wanted something like that for any kind of terminal output.

There are some tools with a similar goal. I hope to make considerable UX improvements over those. I have a custom query language, a command palette, automatic syntax highlighting over unstructured code, and some basic chunking heuristics to combine certain logs if they're close together. It's the combination of the view and the search features that I think really makes it a helpful tool.

Comments URL: https://news.ycombinator.com/item?id=40031756

Points: 2

# Comments: 0

Whenever I'm onboarded onto new codebases, I have a tough time finding my own debug logs when there are hundreds of logs from different systems all cluttering the terminal. It's hard to know where one log ends and another begins. It's just white text on a black background.

I started this a couple days ago, but it's already been useful for my work. After building it, I found out projects like this had already existed. There's a section on bottom of the readme comparing them.

Comments URL: https://news.ycombinator.com/item?id=39982667

Points: 3

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=39939094

Points: 4

# Comments: 0

i.e. texting or calling a number in a specific way based on some standard tons of fast food places provide to make fast food orders without human interaction.

Upon review, it does not look like this is the case. I have several very low traffic projects on which would have never been anywhere close to the free limit. However, if I get involved in a random spam attack, it seems I could be on the hook for several thousand dollars.

This is incredibly dangerous. Netlify is often used as a beginner friendly free tier for static hosting. Not as something that is cheap, but as something that is free. This is just an overall dangerous position to put people in.

https://github.com/EmNudge/watlings

Comments URL: https://news.ycombinator.com/item?id=39263877

Points: 2

# Comments: 0

From my understanding, there are 3 answers here.

1. Most spaces do not need WASM. You don't necessarily see speed improvements since usually your JS and WASM (in the browser) are compiled into the same thing.

2. WASM is very good at bringing tools to new spaces. The biggest limitation here is in both tooling and education. It is not trivial to compile something like FFMPEG for the browser. Improvements to the WASI standard are helping here.

3. WASM is starting to see use in different spaces. For example, as a containerization format for efficient sandboxing.

I don't know that their Wasm module is necessarily "broken", so I'm unsure whether my contributions would be welcome.

My initial motivation to learn WASM (as someone from a primarily web background) was that I had a pretty poor understanding of WASM in general and so I had a lot of difficulty working with WASM builds in just about any capacity other than a heavy JS wrapper.

There are aspects to how WASM works that are quite different from other kinds of assembly formats that make learning the basics pretty important. e.g. how memory is requested, provided, grown. How functions are received and exported. Capabilities of tables.

A lot of this might be abstracted by massive wrappers, but you're losing a lot in perf and debugability when using them.