newpavlov

5 ms·

1.
by newpavlov 2mo ago
Open weight models challenge the "winner takes all" hypothesis, which motivates the astronomical valuations and acts as a justification for trains of cash dumped into AI development. In other words, if AI models become a commodity
2.
by newpavlov 2mo ago
I wonder if NNs could be trained well enough with 1 bit weights (i.e. 0 and 1) with some layers doing addition, while others substraction (i.e. weight sign would be "hardcoded" into the network architecture). Or with zero-less wei
3.
by newpavlov 2mo ago
Some people use cryptocurrency miners to heat their homes. It's certainly better than dumb resistive heating, but depending on various conditions it can cost more than installing a heat pump.
4.
by newpavlov 2mo ago
Because it's not economical, the required hardware is unlikely to pay for itself during its lifetime. The gradient is too small (~50C), which means low Carnot efficiency. Additionally, extraction of low-enthalpy energy involves obstruc
5.
by newpavlov 3mo ago
>There is no "objective" foundation to music. Well, there is a number of "objective" factors which play a significant role. For example, see: https://www.youtube.com/watch?v=tCsl6ZcY9ag
6.
by newpavlov 4mo ago
>Its capabilities all the way down. IIUC one problem with such layering of capability processing is that each passed layer results in a context switch (i.e. switch of memory mappings, thrashing of caches, etc.) and its on top of the cost
7.
by newpavlov 5mo ago
No, it's not. Launch windows [0] are about relative position of orbital bodies which enable use of more efficient transfer orbits. [0]: https://en.wikipedia.org/wiki/Launch_window
8.
by newpavlov 5mo ago
>Are we going to run out of space? In a certain sense, we do. Pumping thousands satellites to LEO increases probability of triggering the Kessler syndrome. Luckily, LEO orbits are also self-cleaning on reasonable time scales (decades), s
9.
by newpavlov 6mo ago
For Rust we have Loom [0], but do not expect for it to work on your whole application. [0]: https://github.com/tokio-rs/loom
10.
by newpavlov 6mo ago
Isn't it just a lawmakers' version of diff? :) You just can't conveniently apply it automatically to compile the resulting text. >Why the hell you not just rewrite the old law and bump the revision? Because it's aimed
11.
by newpavlov 6mo ago
>it requires creating logical qubits with error rates that we are only now seeing companies report And yet 21 was not factored on a real hardware. >There is linear engineering progress for getting from 32 bits to 256 bits being factor
12.
by newpavlov 6mo ago
>The underlying scaling needed to go to 32 bit requires only linear progress to get to 256 Nope. Firstly, for RSA you need to scale from 32 to 4096. Secondly, Shor requires N^2*log(N) quantum gates where N is number of bits in the intege
13.
by newpavlov 6mo ago
Dup? https://news.ycombinator.com/item?id=47582418
14.
by newpavlov 6mo ago
Have they factored 21 yet? [0] IMO most of us can ignore such pieces until a practical factorization of arbitrary 32 bit integers is demonstrated on a QC. And even after this "easy" milestone is achieved, I think it will be at lea
15.
by newpavlov 6mo ago
>1 might be ok but introduces a bunch of opcode space waste. I wouldn't call it "waste". Moreover, it's fine for misaligned instructions to use a wider encoding or be less rich than their aligned counterparts. For exa
16.
by newpavlov 6mo ago
I am not saying that RISC-V should mandate performance. If anything, we wouldn't had the problem with Zicclsm if they did not bother with the stupid performance note. I would be fine with any of the following 3 approaches: 1) Mandate t
17.
by newpavlov 6mo ago
>So just use misaligned loads if Zicclsm is supported. LLVM and GCC developers clearly disagree with you. In other words, re-iterating the previously raised point: Zicclsm is effectively useless and we have to wait decades for hypothetic
18.
by newpavlov 6mo ago
>Multiply and divide And where it actually mattered they did not introduce a separate extension. Integer division is significantly more complex than multiplication, so it may make sense for low-end microcontrollers to implement in hardwa
19.
by newpavlov 6mo ago
>As for `seed`, if you're running on a microcontroller you can just look up the data sheet to see if it's seed entropy is sufficient. It's a terrible attitude to have towards programmers, but looking at misaligned ops, I g
20.
by newpavlov 6mo ago
>Misaligned loads and stores are Zicclsm Nope. See https://github.com/llvm/llvm-project/issues/110454 which was linked in the first issue. The spec authors have managed to made a mess even here. Now they w
21.
by newpavlov 6mo ago
In some cases RISC-V ISA spec is definitely the one to blame: 1) https://github.com/llvm/llvm-project/issues/150263 2) https://github.com/llvm/llvm-project/issues/141488 Anothe
22.
Microscope super-resolution with an LED array and Fourier Ptychography [video](youtube.com)
2 points by newpavlov 7mo ago|0 comments
23.
by newpavlov 7mo ago
Compilers also like to unnecessarily copy data to stack: https://github.com/llvm/llvm-project/issues/53348 Which can be particularly annoying in cryptographic code where you want to minimize number of copies
24.
by newpavlov 8mo ago
>The obvious next step is to do all the math in client-side code and just have the user enter the secret https://en.wikipedia.org/wiki/Password-authenticated_key_agr...
25.
by newpavlov 9mo ago
IIRC at least one of the `restrict` bugs found by Rust was reproduced on both LLVM and GCC.
26.
by newpavlov 9mo ago
LOL, nope. Those annotations must be part of the type system (e.g. `&mut T` in Rust) and must be checked by the compiler (the borrow checker). The language can provide escape hatches like `unsafe`, but they should be rarely used. Withou
27.
by newpavlov 9mo ago
For a system programming language the right solution is to properly track aliasing information in the type system as done in Rust. Aliasing issues is just yet another instance of C/C++ inferiority holding the industry back. C could&#x2
28.
by newpavlov 9mo ago
I generally agree with this opinion and would love to see a proper well documented low-level API for working with GPU. But it would probably result in different "GPU ISAs" for different vendors and maybe even for different GPU gen
29.
by newpavlov 9mo ago
For all my skepticism towards using LLM in programming (I think that the current trajectory leads to slow degradation of the IT industry and massive loss of expertise in the following decades), LLM-based advanced proof assistants is the onl
30.
by newpavlov 10mo ago
>we had about an inch of separation between our laser diodes and our photodiodes Why can't you place them further away from each other using an additional optical system (i.e. a mirror) and adjusting for the additional distance in s

More ›