Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
hajile
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
by
hajile
5d ago
This isn’t the human body or some other thing with billions of unknown parameters. It’s a single (relatively simple) math equation that you are ascribing tons of non-existent complexity to. Left to its own devices, that system will result i
2.
▲
by
hajile
6d ago
When you’re required to approve thousands of lines a day (code you can’t possible understand), it certainly IS causing issues that didn’t exist before. Every study I’ve seen correlates the use of AI with large increases in the number of bug
3.
▲
by
hajile
10d ago
Loads of those result in crashes with some involving hundreds of cars. Just one collision in space carries an ever-increasing risk of cascading into a major event with long-term effects (there's no a good way to call in a space wrecker
4.
▲
by
hajile
11d ago
It’s little to do with misinformation and much to do with trying to keep their model from collapsing from ingesting too much slop.
5.
▲
by
hajile
11d ago
SpaceX satellites are doing about 1000 collision avoidance maneuvers every single day. The addition of new networks is going to congest things even more and the risk of unavoidable cascading failure keeps increasing at a massive rate.
6.
▲
by
hajile
25d ago
Water usage may be a drop in the bucket nationally, but they tend to put datacenters in areas without much water (often because evaporative cooling is less expensive in arid regions) and the effects to those local water supplies can be extr
7.
▲
by
hajile
25d ago
The markets may not be claiming a recession, but the real world certainly is.
8.
▲
by
hajile
27d ago
Vectors are pretty big for speeding up stuff like string comparisons. Bit manipulation offers up to almost 10% advantage. Zicond allows branchless code which represents significant speedups. There’s also serious gains to be had from crypto
9.
▲
by
hajile
1mo ago
Rewriting critical stuff like hand-written SIMD takes a long time (though not as long as it took ARM because ARM had to overcome everything being written in just one ISA). Even a decade in, there are still lots of low-hanging fruit in RISC-
10.
▲
by
hajile
1mo ago
If such an instruction is so obviously important, we'll see it start popping up as a custom instruction in some cores then it will get adopted as an official extension by other companies trying to stay competitive.
11.
▲
by
hajile
1mo ago
> The problem is that RISC-V is never going to win at the high end. RISC-V will never have as much money driving it forward as x86 and ARM. As such, the blocks and integration will always lag. Qualcomm recently bought Ventana and are loo
12.
▲
by
hajile
1mo ago
Here's a good one. Qualcomm beat ARM in court and reportedly pays 2-3% royalties where ARM was demanding 5-10% royalties. Qualcomm's ARM license expires around 2028 with an option to extend to 2033 (for some amount of money). If Q
13.
▲
by
hajile
1mo ago
> I will make one ISA propsal: x86_64 should have had 32 instead of 16 registers APX proposes exactly this along with 3-register syntax and some other things. There are two big issues IMO. 1. It will take at least 15 years before most so
14.
▲
by
hajile
1mo ago
Not too long ago, the claim was that having multiple Phds worth of knowledge was the real value of AI, but now that's gone and it's suddenly a good thing. That's a sales tactic -- not a logical position.
15.
▲
by
hajile
1mo ago
I think this has to do with parallel decoding. How do you tell that the immediate is an immediate instead of an instruction? You have to carve out a very large part of the encoding space and you still can't fit a full immediate (eg, if
16.
▲
by
hajile
1mo ago
Not traditional VLIW per-se as packets wouldn't imply parallelism (though that's theoretically possible) and instruction count would vary. 2-register to 3-register also just involves different wiring and costs nothing. I think you
17.
▲
by
hajile
1mo ago
How about EPIC-esque packet-based instructions? 64-bit instructions with 4 bits indicating instruction formats (60-bit, two 40+20-bit variants, 30+30-bit, 20+20+20-bit, three 30+15+15-bit variants, and 15+15+15+15-bit). Have each larger ins
18.
▲
by
hajile
1mo ago
How can you use consistency and SSE/AVX in the same sentence? SSE has inconsistencies like SSE4.x vs SSE4a. AVX is an even more mixed bag. There are some 19 AVX-512 extensions and ZERO chips support all of them. The situation is so bad
19.
▲
by
hajile
2mo ago
Neither AlphaGo nor AlphaZero were transformers. Why would you expect the same results? Going further, current LLMs have at least an order of magnitude more computing resources, but completely suck at go. Why would this suddenly change unle
20.
▲
by
hajile
2mo ago
Scheme SRFIs make Scheme a much bigger language while also making it painful to use because you have to research which SRFI are implemented in your scheme variant then map those SRFI numbers to what they actually do then you usually need re
21.
▲
by
hajile
2mo ago
JS converts most number into 31-bit ints internally (which is why it’s so fast). GUI work often prefers int or f32. You have a point about games, but the CPU is seldom the limiting factor. Very few people are handling raw audio. For the res
22.
▲
by
hajile
2mo ago
> Itanium would still have sucked I'm not completely convinced of this. If you ignore VLIW, you just have a very unexciting RISC ISA, but because of the VLIW, you get extra scheduling info that most RISC designs don't provide w
23.
▲
by
hajile
2mo ago
How will costs come down? Each generation of model is more expensive to train and run than the last. More efficient hardware? That means throwing out billions of dollars worth of existing hardware and buying billions more in hardware. The c
24.
▲
by
hajile
2mo ago
As it stands, the leaked financials prove him correct. Given their losses (not counting restructuring) they are going to need enough funding to buy any of the bottom 300-400 of the F500 companies outright just to keep the lights on for the
25.
▲
by
hajile
2mo ago
The real answer is to stop trying to have AI reviewing AI code because it's just the blind leading the blind.
26.
▲
by
hajile
2mo ago
Nvidia already seems to be pivoting to "Local inferencing" with stuff like RTX Spark laptops. The problem is that local inference machines won't allow anywhere close to their current margins or gross sales figures. At the sam
27.
▲
by
hajile
2mo ago
On a $100B AI datacenter, some 60-70% of the center needs to be replaced every 2-6 years. These companies claim the hardware lasts 6 years while simultaneously claiming they are relying on new hardware to lower inference costs (implying muc
28.
▲
by
hajile
2mo ago
All "interim" AI contributions to OpenJDK can and will be sued to make big money off of Oracle if those court cases don't go a certain way. This is ironic given how Oracle has bet almost everything on AI succeeding.
29.
▲
by
hajile
2mo ago
The distillation commentary is really crazy coming from a company that stole all it's training material.
30.
▲
by
hajile
2mo ago
You formally verify that your incorrect solution executes without a hitch, but you might just be formally verifying that any user can hit your API and download all your plaintext passwords. Lots of security bugs are caused by incorrect spec
More ›