Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
justaboutanyone
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
justaboutanyone
6mo ago
How does that work with multiple credit agencies?
2.
▲
by
justaboutanyone
6mo ago
While pinyin might be "better", there's still a lot of room for something better than it
3.
▲
by
justaboutanyone
6mo ago
At this point, it might be moot. Too many people are assuming it's still a closed-source thing and will dismiss it. Due to the closed source nature, every mojo announcement I see I think "whatever, next" If the actual intent
4.
▲
by
justaboutanyone
6mo ago
This failed when I put in an australian postal code.
5.
▲
by
justaboutanyone
7mo ago
Shell programming is high density inter-language glue. You simply have more options of implementations to call out to and so less to write. I can trivially combine a tool written in rust with one written in js/java/C/whatever
6.
▲
by
justaboutanyone
8mo ago
First thing a public spacex would want to do is sell off all the non-spacex crap
7.
▲
by
justaboutanyone
8mo ago
This sort of thing will be great for the SpaceX IPO :/
8.
▲
by
justaboutanyone
8mo ago
Running llama.cpp rather than vLLM, it's happy enough to run the FP8 variant with 200k+ context using about 90GB vram
9.
▲
by
justaboutanyone
8mo ago
For Qwen2.5-72B-Instruct-Q5_K_M at 32k context, I fed it a 26k token file (truncated fiction novel) asking it to summarize, and it input processed at 224 tok/s and output generated at 3 tok/s. Not really good enough for interactiv
10.
▲
by
justaboutanyone
8mo ago
You can run large-ish MoE model at good speeds, like gpt-oss-120b, it's snappy enough even with big context. But large and dense at the same time is a bit slow. Running a local LLM will be a load of money for something much slower th
11.
▲
by
justaboutanyone
8mo ago
We may as well have the LLMs use the hardest most provably-correct language possible
12.
▲
by
justaboutanyone
8mo ago
What is the article text for those stopped by the paywall
13.
▲
by
justaboutanyone
8mo ago
It really feels like more than 1 in 20 driving around the 101/280
14.
▲
Rust’s Standard Library on the GPU
(vectorware.com)
255 points
by
justaboutanyone
8mo ago
|
57 comments
15.
▲
by
justaboutanyone
8mo ago
Where are the RVA23 boards that have been hinted at for so long?
16.
▲
by
justaboutanyone
8mo ago
Perhaps people will move to stricter programming languages try to counter the slop issues
17.
▲
by
justaboutanyone
9mo ago
People are still going to read the PR regardless of how it was created.
18.
▲
by
justaboutanyone
9mo ago
Punching through just a firewall is much easier than punching through a typical NAT+firewall setup https://tailscale.com/blog/how-nat-traversal-works
19.
▲
by
justaboutanyone
9mo ago
There are some address source selection problems if you're still using any ipv4 for the local services https://blog.ipspace.net/2022/05/ipv6-ula-made-useless/
20.
▲
by
justaboutanyone
10mo ago
> Except silicon, power, and water Various chemicals too, https://haz-map.com/Processes/97
21.
▲
by
justaboutanyone
10mo ago
Has there ever been an effort to port PF over to linux, or to create an adaption layer that makes things compatible?