rfoo

6 ms·

31.
by rfoo 1y ago
If you compare "schema validation error count" plus "Count of Finish Reason others" then SiliconFlow and Infinigence is in the same bucket too. Maybe their API layer detected incorrect tool call and set finish reason to
32.
by rfoo 1y ago
Graphene just made VoLTE / NR / VoNR toggle feature built-in to their OS.
33.
by rfoo 1y ago
China knew that chips were security and strategic issues maybe 20 years ago if not more, I wonder why they haven't done building equally capable factories on-shore.
34.
by rfoo 1y ago
That's cool. For those who happened to be in China right now, there's the same listing on a Chinese marketplace (idlefish) for only 480 CNY (~68 USD). That's... better than too good to be true. I'm going to have a try.
35.
by rfoo 1y ago
> and that's ironically the one feature they bought out and integrated (Supermaven) instead of developing themselves What? Cursor bought Supermaven last November and I have been using their much superior (compared to GH Copilot) com
36.
by rfoo 1y ago
It could be a better draft model than separately trained EAGLE etc for speculative decoding.
37.
by rfoo 1y ago
> It still seems strange. A big part of GrapheneOS is to provide a safeguard from Googles data hoarding, yet it works primarily on Google phones. That's the most confusing part. IMO GrapheneOS is not mainly about "provide a saf
38.
by rfoo 1y ago
Well, anyone with actual root on a secure (locked, verified boot on) Android phone can hard brick it with a single command. Yes, you can yell at the user telling them it's their fault. Still something you usually do not want to support
39.
by rfoo 1y ago
Then refresh rate is a problem.
40.
by rfoo 1y ago
Spoiler: they went to Thailand.
41.
by rfoo 1y ago
You are absolutely right! But China bad Dario good Anthropic the only firm caring about AI safety /s
42.
by rfoo 1y ago
How what? The fp64 GFLOPS per watt metric in the post is almost entirely meaningless to compare between these accelerators and NVIDIA GPUs, for example it says > Hopper H200 is 47.9 gigaflops per watt at FP64 (33.5 teraflops divided by 7
43.
by rfoo 1y ago
<rant>The official Arrow C++ implementation is just ergonomic warts, full of `const std::shared_ptr<T>&` bs. Trying to use it to manipulate data always give me headache telling apart WTH is an Array, ArrayData, Buffer, and t
44.
by rfoo 1y ago
This is the extracted Arrow C data interfaces as documented in https://arrow.apache.org/docs/format/CDataInterface.html It's not how you interact with the data in your own C++ code, it's for passing this
45.
by rfoo 1y ago
It's more of a culture thing. People just hate the concept of "idk how much I'm going to pay let's just try this and find out later". Also people would be confused as they expect things to be prepaid, so if you let
46.
by rfoo 1y ago
You can try your solutions here: https://wf25open.kattis.com/contests/wf25open I believe it runs with the same test data as in the actual contest.
47.
by rfoo 1y ago
meret is really good tho.
48.
by rfoo 1y ago
For a whim I read this as "us regular boeing engineers" and it was really funny.
49.
by rfoo 1y ago
IMO the correct thing to do to make these people happy, while being sane, is - do not build llama.cpp on their system. Instead, bundle a portable llama.cpp binary along with unsloth, so that when they install unsloth with `pip` (or `uv`) th
50.
by rfoo 1y ago
Slapping Rc<T> over something that could be clearly uniquely owned is a sign of very poorly designed lifetime rules / system. And yes, for now async Rust is full of unnecessary Arc<T> and is very poorly made.
51.
by rfoo 1y ago
> and frankly, it likely will only need to work until the bubble bursts, making "the long run" irrelevant Now I get why people are so weirdly being dismissive about the whole thing. Good luck, it's not going to "burst
52.
by rfoo 1y ago
Scrapers do not care about having a 20% slowdown. All they care is being able to scale up. This does not block any scale up attempt.
53.
by rfoo 1y ago
... except when you do not crawl with a browser at all. It's so trivial to solve just like the taviso post demostrated. This makes zero sense, this is simply the wrong approach. Already tired of saying so and been attacked. So I&#x27
54.
by rfoo 1y ago
Pretty sure it's an incident.
55.
by rfoo 1y ago
For me it's my most used super long command line flag. For a brief moment `--break-system-packages` surpassed it, then I discovered `pip` accepts abbrev flags so `--br` is enough, and sounds like bruh.
56.
by rfoo 1y ago
> There are a lot of countries still where you're limited to feature phones I thought China fixed this for most of the world, at least for Africa it's fixed. It's the Internet access being the bottleneck now.
57.
by rfoo 1y ago
Or, you can say, OpenAI has some real technical advancements on stuff besides attn architecture. GQA8, alternating SWA 128 / full attn do all seem conventional. Basically they are showing us that "no secret sauce in model arch y
58.
by rfoo 1y ago
> The only thing that I can say definitively is that there is overhead to doing the literal stack switch. There's a reason async I/O got us past the C10k problem so handily. You can also say that not having to constantly alloca
59.
by rfoo 1y ago
Good points. Personally I'm more annoyed of async-Rust itself than not having a blessed async solution in-tree. Having to just Arc<T> away things here and there because you can't do thread::scope(f) honestly just demonstrate
60.
by rfoo 1y ago
Is there really something to lose? How often do we see "stackless coroutine" listed as advantage in Rust vs Go for network programming flamewars?

More ›