Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
fleventynine
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
1.
▲
by
fleventynine
10d ago
Having fewer resources such as security engineers will not lead to better outcomes. A skeleton team with gigawatts of compute in some middle east bunker is MORE likely to unleash something poorly aligned.
2.
▲
by
fleventynine
10d ago
I don't think society has enough power to control what billionaires spend their money on. The promise of AI is such an attractive nuisance for power seekers that trying to crack down on it will just force it underground, where it will
3.
▲
by
fleventynine
17d ago
Ugh, the accidental complexity of drop-frame encoding, BCD, etc... This mess will likely be with us for a long time.
4.
▲
by
fleventynine
1mo ago
The solution for this is to pay open source maintainers for their attention. If I want them to review and merge my bugfix I should attach $1000 to the PR.
5.
▲
by
fleventynine
2mo ago
Not an option for me until it supports submodules.
6.
▲
by
fleventynine
2mo ago
I typically work with commit chains of at least 5 commits in various states of code review, so I spend at least 60% of my development time editing an old commit in the middle of a rebase -i.
7.
▲
by
fleventynine
2mo ago
This machine needs better networking options to be useful, such as built-in 100Gbit QSFP28. There is not enough space between the x4 PCIe slot and the power supply for a NIC to fit, and even if there was, you'd have to cut a hole in th
8.
▲
by
fleventynine
2mo ago
It's pretty clear to me that coding agents are a significant cause of the current glut of comp-sci graduates unable to find their first job...
9.
▲
by
fleventynine
2mo ago
I think there's room for win-win solutions here; the cost of placating the locals is a rounding error compared to the cost of these data centers. 1. Local governments can require that if the data center peak load is 1.0GW, they must pr
10.
▲
by
fleventynine
2mo ago
I like Rust and use it full-time professionally. Unsafe is not the same as unsound. Unsound means that the unsafe code is not maintaining the aliasing invariants on references required by the language, and thus undefined behavior can leak i
11.
▲
by
fleventynine
2mo ago
I don't think this does enough to address to supply-chain security concerns. Before I use a crate, I want some assurance that the transitive deps have had a proper security audit, and that I'm not a single "cargo update"
12.
▲
by
fleventynine
2mo ago
I stopped using Facebook back in 2021 when the majority of my feed was reshared political content with 20+ comments from my friends fighting about divisive social/political issues. It wasn't fun, and it wasn't fostering commu
13.
▲
by
fleventynine
2mo ago
Is the RTL for the FPGA available to be tinkered with?
14.
▲
by
fleventynine
2mo ago
> Every corporate network to which I've connected worked just fine without it. Just because it appears to be working fine doesn't mean you are in control of it. Without hardware attestation, how do you know the machines are ru
15.
▲
by
fleventynine
4mo ago
If regular people can repurpose old hardware, so can shared providers, who can extract more value from the hardware and thus afford to pay more. In a constrained market, supply and demand favors folks who can most efficiently extract rent.
16.
▲
by
fleventynine
4mo ago
My point is that dram demand is mostly orthogonal to whether everyone is using open weight models or secret weight models. Heavy demand for local models (whether secret or open weight) will require even more aggregate DRAM than for shared.
17.
▲
by
fleventynine
4mo ago
If local models are good enough, doesn't that increase demand for DRAM as everyone buys DRAM for their poorly utilized local machines? Surely it is a more efficient use of DRAM to run inference on shared hardware with large batch sizes
18.
▲
by
fleventynine
4mo ago
I wonder how good LLM agents are at reverse engineering FPGA bitstreams... I want a robust open-source ecosystem where anyone can take my hardware projects and modify them without needing to deal with licensing friction.
19.
▲
by
fleventynine
4mo ago
There isn't enough hardware in the world for everyone to run their own SoTA model. The only hope we have is if we work together to host these on shared infrastructure, benefiting from >50x economies scale due to batching, etc. That
20.
▲
by
fleventynine
4mo ago
That DRAM would get even more use if it was removed from these machines and placed into a shared pool :) I joke, but thanks to the brutal DRAM market there has been some movement in this direction lately...
21.
▲
by
fleventynine
4mo ago
My point is that it is WAY more efficient if we put the world's DRAM supply into a shared inference pool instead of stranding it in local machines where it won't have as high of batch size or utilization. The cost of not being eff
22.
▲
by
fleventynine
4mo ago
I think folks in this thread are underestimating how expensive it is to serve a SoTA model at 100 tokens a second. In addition to the $500k in capital costs, you also have significant electricity costs. This stuff is expensive because suppl
23.
▲
by
fleventynine
4mo ago
Many small crates published by large, trustworthy projects are fine and preferable to one large crate that "does everything".
24.
▲
by
fleventynine
4mo ago
Good luck finding reasonably priced switches and low power PD ICs that support type 3 or type 4 PoE. Also, supporting those tiny pulses requires large capacitors to hold a charge in between pulses. That plus the required magnetics make PoE
25.
▲
by
fleventynine
4mo ago
PoE is lousy for sensors. The switch will cut the power if you draw less than 10mA (480 mW), so regardless of PHY efficiency (which is terrible compared to most RS-485, CAN, or even radio ICs), you are REQUIRED by the spec to generate heat
26.
▲
by
fleventynine
5mo ago
Even more interesting, the developer manual: https://discreetfx.com/documents/NewTekVideoToasterDeveloper... I remember using this thing when I was a kid, trying to figure out how all the switching effects worked, so s
27.
▲
by
fleventynine
5mo ago
I had the misfortune of writing a complicated WPF app from scratch circa 2010-2011. Performance using the WPF widgets was terrible compared to HTML/Javascript/Blink; we ended throwing away most of the WPF code other than the main
28.
▲
by
fleventynine
6mo ago
Most software uses 10x more memory than is necessary to solve the problem. In an ideal world, developers would stop building bloatware if their customers can't afford the DRAM.
29.
▲
by
fleventynine
6mo ago
You've got them mixed up with Blackstone.
30.
▲
by
fleventynine
6mo ago
Just donated $250; I'm trying to get in the habit of supporting the open source projects I use similarly to the cost of their proprietary competitors.
More ›