Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
tliltocatl
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
91.
▲
by
tliltocatl
6mo ago
It is as cool as the fact that it is relevant is sad and scary.
92.
▲
by
tliltocatl
6mo ago
Before IBM PC computer's weren't particularly commonplace outside of ivory towers either.
93.
▲
by
tliltocatl
6mo ago
- Even each instruction does a lot of work, it is supposed to do it in parallel, so time available to fetch the next instruction is (supposed to be) the same. - Not everything is parallelisable so most of instructions words end up full of N
94.
▲
by
tliltocatl
6mo ago
At that point, just go Braille! Amazing work anyway.
95.
▲
by
tliltocatl
6mo ago
Not really. Itanium was a result of some people at Intel being obsessed by LINPACK benchmarks and forgetting everything else. It sucked for random memory access, and hence everything that's not floating-point number-crunching. Compiler
96.
▲
by
tliltocatl
6mo ago
On superscalars running xor trick as is would be significantly slower because it implies a data dependency where there isn't one. But all OOO x86's optimize it away internally.
97.
▲
by
tliltocatl
6mo ago
I don't think that's how it works. - Normally ALU implements all "light" operations (i. e. add/sub/and/or/xor) in a single block, separating them would result in far more interconnect overhead. Often,
98.
▲
by
tliltocatl
6mo ago
Static count - how many times an instruction appears in a binary (or assembly source). Dynamic count - how many times an opcode gets executed. I. e. an instruction that doesn't appear often in code, but comes up in some hot loops (like
99.
▲
by
tliltocatl
6mo ago
What's SMT in this context?
100.
▲
by
tliltocatl
6mo ago
It might be because XOR is rarely (in terms of static count, dynamically it surely appears a lot in some hot loops) used for anything else, so it is easier to spot and identify as "special" if you are writing manual assembly.
101.
▲
Planar maps: an interaction paradigm for graphic design (1989) [pdf]
(lri.fr)
2 points
by
tliltocatl
6mo ago
|
1 comments
102.
▲
by
tliltocatl
6mo ago
A few weeks ago a there were discussion here on HN on why SVG doesn't match Flash's capabilities as an artistic medium. Looks like that's why.
103.
▲
by
tliltocatl
6mo ago
Author and EML are using different definitions of elementary functions, EML's definition being the school textbooks' one (polynomials, sin, exp, log, arcsin, arctan, closed under multiplication, division and composition). The auth
104.
▲
by
tliltocatl
6mo ago
IANAP, but my understanding is that the Landauer limit defines the minimum energy of forcing a unknown bit into a known state. Physics as we know it is fully reversible at the microscale - every possible state have exactly one ancestor st
105.
▲
by
tliltocatl
6mo ago
The early PC era was a mess, and that's not the period I'm talking about. IBM was clearly not up to the task and Intel didn't care much yet, but Microsoft certainty did a lot for compatibility from the start (i. e. DOS abstra
106.
▲
by
tliltocatl
6mo ago
Surprising that the author finds it surprising. In base-10 it's as easy as "a number is divisible by 3 or 9* iff sum of its digits is divisible", which is trivially independent of endiannes and slightly less trivial, but stil
107.
▲
by
tliltocatl
6mo ago
MRI could switch to LH2. Yes, it's explosive and higher boiling temperature so would not support as high field and incompatible with currently used semiconductors. But it's doable. Plenty of other important uses (i. e. semiconduct
108.
▲
by
tliltocatl
6mo ago
PC/x86 was an extreme outlier, sadly, and it was because of Microsoft/Intel business model. The architecture details was historically mostly decided on by Wintel, yet the system integration was done by many vendors, whose best i
109.
▲
by
tliltocatl
7mo ago
But how do these hedges map to actual wealth? By the power of your stocks, you were entitled If a certain share of steel, gasoline and human labor. Now if a part of this share is burned with no gain, how can playing with casino chips recove
110.
▲
by
tliltocatl
7mo ago
Because Markdown is quite readable in plaintext form with no Markdown-specific rendering at all. HTML isn't.
111.
▲
by
tliltocatl
7mo ago
> standardized across GPU Nothing is getting standardized across GPU vendors never ever again (pretty much every GPU uses some form of SIMD internally). Nvidia's CUDA is too specific to Nvidia's hardware, AMD have some serious
112.
▲
by
tliltocatl
7mo ago
Those are called suicide cords for a reason. Exposed prongs is only one problem: another is that these can end up feeding current into a line that was supposed to be de-energized, potentially killing a lineman (I also wanted to add that the
113.
▲
by
tliltocatl
7mo ago
Damn, here goes another distro.
114.
▲
by
tliltocatl
7mo ago
> more intellectual property rights is the last thing we need. Granted, picking a famous name you don't have any association with is an a-hole move. Not all a-hole moves should be illegal.
115.
▲
by
tliltocatl
7mo ago
I agree that dependencies are a liability, but, sadly, "batteries included" didn't work out for Python in practice (i. e. how do I even live without numpy? No, array aren't enough).
116.
▲
by
tliltocatl
7mo ago
Because lead turns a single high-energy particle (that would disturb a single bit and punch through) into a shower of many low-energy particles (that would disturb many bits AND induce lattice damage over a wide area).
117.
▲
by
tliltocatl
7mo ago
> Main point of real threads is that the are executed simultaneously on different cores Sorry, that's about as far from truth as you can get. Threads were a thing way before multicore was available. Windows got them since Win95/
118.
▲
by
tliltocatl
7mo ago
If you are being paid for making people's lives miserable, expect some misery in return. That's how it is.
119.
▲
by
tliltocatl
7mo ago
Stackless coroutines in C when? As an embedded dev, I miss them deeply. Certainly not enough RAM to give a separate stack for everything and rewriting every async call as a callback sequence sucks.
120.
▲
by
tliltocatl
7mo ago
Besides context switching, another issue with OS threads is that you need to carefully use synchronization primitives and watch for missing barriers. Green threads are a bit more forgiving.
More ›