Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dakom
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
Show HN: AwsmAudio – a WebAudio editor with native MCP
(audio.awsm.fun)
7 points
by
dakom
3mo ago
|
0 comments
2.
▲
Show HN
2 points
by
dakom
3mo ago
|
1 comments
3.
▲
by
dakom
8mo ago
How does it deal with latency? Afaict remote LLMs need seconds to process, but Tetris can move much faster..
4.
▲
by
dakom
8mo ago
I agree wholeheartedly. It's like the energy and motivation has to go somewhere, and talking too much is a vacuum.
5.
▲
by
dakom
8mo ago
I love this, simple, fun, and easy-to-read source :) FYI - there's a security problem with the leaderboard, I added the Testy McTester score of 42 to see if it would go through, feel free to delete it
6.
▲
by
dakom
8mo ago
Yeah, I split the crates so `renderer-core` deals with the web-sys part, `renderer` is pretty much plain Rust (and wgsl with Askama templates) I prefer this for 100% browser-only, but that's a niche. I do think wgpu makes more sense wh
7.
▲
by
dakom
8mo ago
Mostly because I want insight and control at a lower level, which breaks down into two different use-cases: 1. Debugging. The nature of bugs in this space is a lot more of "it doesn't look right on the screen" as opposed to &
8.
▲
by
dakom
8mo ago
This is the culmination of a long journey — it started in TypeScript, moved through WebGL1 with Rust bindings, then WebGL2, and now finally WebGPU. Woohoo :D AwsmRenderer is a browser-native WebGPU renderer written in Rust, using web-sys di
9.
▲
Show HN: AwsmRenderer, a browser-native WebGPU renderer in Rust
(dakom.github.io)
3 points
by
dakom
8mo ago
|
5 comments
10.
▲
by
dakom
11mo ago
fwiw I'm happy to see this - been trying to tackle a hairy problem (rendering bugs) and both models fail, but: 1. Codex takes longer to fail and with less helpful feedback, but tends to at least not produce as many compiler errors 2. C
11.
▲
by
dakom
1y ago
I wouldn't dismiss personal anecdotes any more than I'd dismiss someone claiming they saw something in a reputable journal but can't remember the citation. In other words, yeah, don't just believe it at face value- but i
12.
▲
by
dakom
1y ago
Funny coincidence, I use this often and just opened an issue earlier today: https://github.com/go-task/task/issues/2303 :)
13.
▲
by
dakom
1y ago
Taskfile and Justfile are pretty solid.
14.
▲
by
dakom
1y ago
I've never delivered a game anyone's really paid for, so take with a grain of salt, but imho the big win when you are writing your own stuff is you get to decide what not to include. That sounds obvious but it really isn't. O
15.
▲
by
dakom
1y ago
There's also some cool stuff brewing in the AVS space to allow nondeterminism, GPU, storage, and more.. for example, WAVS executes stuff off-chain in WASI components, and brings the result on-chain (secured by re-staking via Eigenlayer
16.
▲
by
dakom
1y ago
Cool. Trying to understand the value-add here, how does this differ from executing via wasmtime?
17.
▲
by
dakom
2y ago
bevy_math also uses glam, re-exported in the prelude: https://github.com/bevyengine/bevy/blob/cc69fdd0c63ea79fda4f...
18.
▲
by
dakom
2y ago
Do you remember Angry Birds? https://villekoskela.org/2012/02/15/angry-birds-facebook-rel...
19.
▲
by
dakom
2y ago
Eh.. lots of projects targeted mobile app stores by authoring in Flash and using the GPU accelerated stuff. Starling was a semi-blessed framework. Worked perfectly well, no battery drain. Lots of "native" apps were authored that w
20.
▲
by
dakom
2y ago
While some of this is true, some of it is not (deep links worked fine, there was a brief time where hidden html was encouraged and worked just as well for search engines to pick up, etc.) More to the point though- Flash didn't shine as
21.
▲
by
dakom
2y ago
I'd agree it's largely the human factor, but maybe from a different angle. Rust has got the "there's a crate for that" factor, like JavaScript, which helps onboard people who are afraid of getting stuck writing ever
22.
▲
by
dakom
2y ago
> overhead of each API call Yeah, that's an issue, esp with WebGL.. but you can get pretty far by reducing calls with a cache, things like "don't set the uniform / attribute if you don't need to".. but I hea
23.
▲
by
dakom
2y ago
I've been using Figment [0] Needs a little bit of hand-holding when you have structs with different field names, but otherwise does everything I need for that particular part of the problem. [0] https://github.com/Sergi
24.
▲
by
dakom
2y ago
Love this :) Small, related anecdote: back in the year 2001 or so, this is in the same family of how I built websites... The difference is I wrote in in C as Apache Modules. So, like, most people were using other people's C modules (li
25.
▲
by
dakom
2y ago
Yeah, the game I linked to is in Rust/wasm, running solely in browsers :) The interesting part of the collision detection code is here: https://github.com/dakom/not-a-game/blob/main/src/collisio
26.
▲
by
dakom
2y ago
FYI, I recently posted about a 2d game I made, here: https://news.ycombinator.com/item?id=41761517 Putting aside the politics and all, focusing on the tech- one thing I came across when trying to do my own collision detecti
27.
▲
by
dakom
2y ago
Love that book, great resource for lookup up all kinds of programming topics, whether game related or not
28.
▲
by
dakom
2y ago
I don't think you get how powerful Rust's pattern matching is, or how to think of it in terms of a router. From my example above, check out https://github.com/dakom/dominator-workers-fluent-auth/blob/
29.
▲
by
dakom
2y ago
> URL redirection Erm, just return a new url after the match? Get fancy with state machine like enums? Rust has everything you need here, not getting why you think this requires a framework. > Specific management of [...] again, match
30.
▲
by
dakom
2y ago
This article makes several different points that would ideally each be tackled on their own. You don't need a router when you have pattern matching (just split the url and match on static and dynamic vars however you need) Auth is typi
More ›