Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
14113
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
14113
1mo ago
Yes, I was being a bit concise: Individual optimisations should be turned on as determined by profiling, application semantics, etc. My point was more that if you want to get as close as possible between integer and floating-point, then the
2.
▲
by
14113
1mo ago
> Floating point math is often slower than integer math because the compiler is being conservative about how it optimizes your code. It's not strictly true to say that it's "being conservative". What is more correct i
3.
▲
by
14113
1mo ago
Seconding this - having worked on LLVM and Firefox, the performance tuning of each application was very different. Even measuring the performance of an application like Firefox (in a meaningful way) is non-trivial, wheras compilers are much
4.
▲
by
14113
1mo ago
I mildly disagree - depending on your definition of "typical app". Most applications have much greater use of multi-processing and concurrent cross-thread (or cross-process) communication. Compilers, aside from high-level parallel
5.
▲
by
14113
2mo ago
> I feel like this is with 2026 view where browsers are so mutually compatible. I wish this was the case. Unfortunately, companies that work on non-Chromium browsers need to employ dedicated web compatibility teams to either a) help webs
6.
▲
by
14113
2mo ago
There are two types of people. Those who can extrapolate from incomplete data, and
7.
▲
by
14113
2mo ago
To me, the parentheses make it significantly easier to read. They make it clear which operator directly acts on the variable, and create a mental meta-object to which the next operator acts. I accept that if you're extremely used to wr
8.
▲
by
14113
2mo ago
As I experienced while trying to write out an AST for this pattern, the operator precedence makes it harder to read. I would at least prefer that it's written as *(foo++).
9.
▲
by
14113
2mo ago
Oops, you're right - I got the operators the wrong way around! I forget the precise precedence of * and ++ in C sometimes. Assuming that it would be bracketed as *(lwr++), it should actually be: block statement (assignment)
10.
▲
by
14113
2mo ago
Representing code in a compiler is not precisely trivial, and the two statements are actually quite different from a compiler or AST perspective. Just looking at the first branch: *lwr = x; lwr++; This could be be represented with so
11.
▲
by
14113
2mo ago
Passing by pointer (in C) reduced the difference a lot, but swapping the order of Add and Int in the Rust enum was enough to reduce the different to: cmp ecx, 1 je .LBB0_3 vs cmp ecx, 2 jne .LBB0_2 LBB0_3 and LBBO_2 were t
12.
▲
by
14113
2mo ago
It required a little bit of messing with optimisation settings and library generation in Rust, but they emit very very similar x86-64 assembly: https://godbolt.org/z/89W4srz4d
13.
▲
by
14113
3mo ago
My understanding is that churches were built next to yew trees, not yew trees planted next to churches. Pre-Christian religions had many associations with yew trees (they live for a long time, give off mildly hallucinogenic gasses on hot da
14.
▲
by
14113
3mo ago
The fundamental issue with this is that many problems have a time/energy/financial threshold for success. Trying to tackle such a problem with incremental iterative solutions will consistently fail, as each individual iteration wi
15.
▲
by
14113
3mo ago
Because, in the latter case, you have to declare a function argument for /every possible option/ that you want your graphics API to expose, and you need to do this every time you add a new option. On the other hand, declaring the
16.
▲
by
14113
4mo ago
Incorrect: Star Labs have been shipping laptops since 2018, before Framework was even a company.
17.
▲
by
14113
4mo ago
Star Labs have delivered a number of other high quality linux laptops - I even used one as my daily work driver for a few years at a previous job. They're not a startup.
18.
▲
by
14113
6mo ago
> companies are supposed to lose money while they grow At what point do we declare that a company has "grown" and now must make money? OpenAI is a multi-billion dollar company right now, surely that's a point at which they
19.
▲
by
14113
6mo ago
This post is actually a joke, but it does bring about an important point: For an interpreter, having more information results in faster execution. WASM is much closer to Java bytecode than you might think, and SpiderMonkey/V8 are bas
20.
▲
by
14113
9mo ago
There was a company that did compute-in-dram, which was recently acquired by Qualcomm: https://www.emergentmind.com/topics/upmem-pim-system
21.
▲
by
14113
9mo ago
That's not quite correct. Snapdragon chips that are advertised as being good for "AI" also come with the Hexagon DSP, which is now used for (or targeted at) AI applications. It's essentially a separate vector processor w
22.
▲
Say Hi to Kit
(firefox.com)
52 points
by
14113
11mo ago
|
61 comments
23.
▲
by
14113
2y ago
> More streamlined menus For everyone here complaining about this, have you ever looked at how many ways there are to access your history on Firefox? At my last count, there were 4 different ways to do it, depending on which menu you pic
24.
▲
by
14113
2y ago
No, Firefox never targeted geeks. It's just that, when it came out, the only people who used a browser other than Internet Explorer happened to be geeks. The audience came to them, rather than them going to the audience.
25.
▲
by
14113
4y ago
From the article: "[...] as developers get more and more senior, they tend to ignore more and more problems, because they've gotten so used to it. That's the way it's always been done, and they've learned to live wi
26.
▲
by
14113
6y ago
This is wrong - triSYCL is roughly the same age as ComputeCpp, and hipSYCL is only slightly younger. There has been a lot of academic interest in SYCL, but as with any new technology (especially niche technologies) it's always going to
27.
▲
by
14113
6y ago
DPC++ is basically "just" SYCL, so no MPI.
28.
▲
by
14113
7y ago
Well maybe the other carriers have less awful legacy tech - I can't speak for what they have. All I know is what I saw while working at BA.
29.
▲
by
14113
7y ago
That's a much more reasonable explanation - thanks, I appreciate it! The way I'd had it explained to me was more along the lines of "greedy pilots want to be able to fax because they can't be bothered to learn how to use
30.
▲
by
14113
7y ago
Speaking as someone who (for a time) worked in the IT department of British Airways, the culprit is really just ancient systems that aren't well maintained, along with institutional and industrial pressure not to improve them or upgrad
More ›