wishawa

7 ms·

1.
by wishawa 11mo ago
I see. That's slightly unfortunate. In principle, increasing temperature flattens out the distribution but the ordering between different tokens' probabilities remain the same, so setting a top-k shouldn't break my test. Can&
2.
by wishawa 11mo ago
This is with Together's API via OpenRouter, running DeepSeek V3 0324 and Kimi K2 0905. I didn't set a top-k. So it seems like Together must be doing something weird in their speculative decoding implementation.
3.
by wishawa 11mo ago
I didn't know this! I've always thought speculative decoding was "if p(draft_token) > threshold, use it". You made me go read how it actually works and it's pretty neat! That said, I still think some providers ar
4.
by wishawa 11mo ago
Fair point. If Moonshot is holding back the true weights or inference techniques that affect correctness, then providers including Together should call them out on that. I for one would stop using Kimi if that is the case. Anyway, Novita is
5.
by wishawa 11mo ago
Inference is impressively fast. But what about quality? In the Kimi vendor verifier ( https://github.com/MoonshotAI/K2-Vendor-Verifier/ ), Together has one of the highest tool call failure rates (>300 failures ov
6.
by wishawa 2y ago
Also check out [Eaglemode]( https://eaglemode.sourceforge.net/ )!
7.
NumPy 2.0.0(github.com)
8 points by wishawa 2y ago|0 comments
8.
Show HN: a Rust to JavaScript RMI, for your LiveView and Live Everything Else(github.com)
3 points by wishawa 2y ago|0 comments
9.
by wishawa 3y ago
Euclidea?
10.
by wishawa 3y ago
The instruct model is trained on the Baize dataset, which is generated from ChatGPT. So it is no surprise that Falcon censors the topics that ChatGPT censors. If you have an uncensored instruct dataset, you can use that to fine tune your ow
11.
by wishawa 4y ago
You're right. I got the two frameworks confused. Async UI is similar to Sycamore in term of not diffing VDOM. The API is different in that in Sycamore, you tell the framework what to render (by using sycamore::render) and the framework
12.
by wishawa 4y ago
Sycamore works pretty similarly to React. See https://www.reddit.com/r/rust/comments/xvv49w/comment/ir6pw0... for how Async UI is different from React-style frameworks.
13.
by wishawa 4y ago
I must admit I've never seen Concur before!.The idea of using generator/async is pretty similar. The difference, as I understand, is that in Concur, you yield the widget and let the framework mount it, while in Async UI, you await
14.
by wishawa 4y ago
The Todo example is 2.5 MB non -gzipped. About 600KB gzipped. Still large, but it's because we're shipping a lot of code that we don't need. Mostly the APIs exposed by web_sys. Proper dead code elimination would bring it dow
15.
by wishawa 4y ago
By lots of 'static and Rc.
16.
by wishawa 4y ago
That example is indeed pretty noisy, but partly due to my premature optimization. The operations of adding, editing, and toggling Todo items are all O(log N)[1]. Things could be simpler if I’d just take the O(N). [1] O(log N) for “our” code
17.
by wishawa 4y ago
RUI is really cool, but it is solving a different problem. It is immediate-mode, and it is focused on building a new toolkit. Async UI is more about re-exposing existing retained-mode toolkits in nice-to-use, Rust-friendly APIs. The cool th
18.
by wishawa 4y ago
This uses the executor used by async-std rather than the one used by Tokio. So if you're using something Tokio-specific, you would probably need async-compat[1]. But can you share more on what you need Tokio for? I'd completely un
19.
by wishawa 4y ago
The async control flow is not directly inspired by anything. It is a cool side effect of using async for everything that I myself only discovered once I started writing examples. Async UI as a whole is inspired by the simple fact that UI is
20.
by wishawa 4y ago
The full example code is here: https://github.com/wishawa/async_ui/blob/main/examples/gtk-l... . (except for that invalid_login_popup is not a real popup because I haven't implemented popups yet
21.
by wishawa 4y ago
You're right that components should intuitively pend forever. But with Async UI, the line between a component and a normal async function is blurry; our login_form eventually returns, so it is a normal async function, but it also rende
22.
by wishawa 4y ago
Hi HN! I've been working on Async UI for half a year now, and I think it is time I share it with everyone. The project is not even really usable yet (due to lack of implemented components and documentation), but I think the proof-of-co
23.
Show HN: Async UI: A Rust UI Library Where Everything is a Future(wishawa.github.io)
173 points by wishawa 4y ago|92 comments
24.
by wishawa 4y ago
Why not heat the inside of the house directly? Having the heat go through a pump just results in more loss.
25.
by wishawa 4y ago
> federal regulators consistently assured Americans that the risks of a massive accident were “vanishingly small”—even when they knew they had insufficient evidence to prove it Why is the burden of proof on them? Nuclear should be innoce
26.
by wishawa 4y ago
https://en.m.wikipedia.org/wiki/Moravec%27s_paradox
27.
by wishawa 4y ago
Perhaps this? https://github.com/denysdovhan/wtfjs
28.
by wishawa 4y ago
wouldn’t that be 23.15 UTC on the same day? edit: no it won’t. I was confused.
29.
by wishawa 4y ago
Pumps might only be able to suck water up 26 inches, but there is no such limit on how high they can push water.
30.
by wishawa 4y ago
For the open question on bounded number of choices, the idea is still "count the number of smaller combinations". Given a k-combination C, we first count the number of all possible combinations of less than k elements; this is bin

More ›