Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
p_l
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
211.
▲
by
p_l
6mo ago
Often the alternatives presented as cheaper to me in discussions are actually burning money. But given how I always see "you don't need k8s because you're not going to scale so fast" I am feel like even professional k8s
212.
▲
by
p_l
6mo ago
Still is, just details change. A lot of criticism of k8s is always centered about some imagined perfect PaaS, or related to being in very narrow goldilocks zone where the costs of "serverless" are easier to bear...
213.
▲
by
p_l
6mo ago
The thing is, JJ makes mega merges easy... Which opens paths to simple but powerful workflows that match reality better. Having multiple converging changes, or even separated bits of history for $reasons becomes ready without rebar and seri
214.
▲
by
p_l
6mo ago
Suppliers doing that kind of trick is what really killed GOSIP, and why the new v6 mandates in USGOV do not allow waivers for vendors, only for individual specific use cases
215.
▲
by
p_l
6mo ago
Ok, so a simplified summary of EU AI Act approach as of now: Model outputs are not copyrightable at all, only human work. That means the prompt, and whatever modifications done to output by human, are copyrighted, but nothing else. HOWEVER
216.
▲
by
p_l
6mo ago
UK plugs are always grounded because there is no ungrounded version. But elsewhere you only get grounded plug if you buy extra extension cord for the apple power brick, otherwise it's only ungrounded.
217.
▲
by
p_l
6mo ago
Apple avoids shipping grounded plugs as if it was personal affront to Ive. Also caused many many times for me to be shocked with electrostatic build-up.
218.
▲
by
p_l
6mo ago
Macs are actually part of pain point with ARM64 Linux, because the Linux arm set er tend to use 64 kB pages while Mac supports only 4 and 16, and it causes non trivial bugs at times (funnily enough, I first encountered that in a database co
219.
▲
by
p_l
6mo ago
Because if there's stock-based renumeration, it's 100% certain it applies and probably is considerable portion of renumeration of those deciding on layoffs. Honestly, I'd preferably make it so that stock movement is frozen fo
220.
▲
by
p_l
6mo ago
They should also trigger holds on bunch of other operations, like stock buyouts or sales by people with active or recent relationship to the company
221.
▲
by
p_l
6mo ago
If you want something extra spicy, there are devices out there that implement CORBA in silicon (or at least FPGA), exposing a remote object accessible using CORBA
222.
▲
by
p_l
6mo ago
It was because IA-64 was a completely different unrelated architecture that until AMD succeeded with K8 was "the plan" for both 64bit intel roadmap and the roadmap to kill off compatible vendors (AMD, VIA)
223.
▲
by
p_l
6mo ago
Outlook when connected with exchange (which is probably the case, with corporate network email accounts connected) does not use SMTP nor IMAP, but Exchange RPC protocol, with underlying data model based on X.400 not SMTP. Can actually work
224.
▲
by
p_l
6mo ago
I used to be on a project that, IMHO, had possibly considerable impact on capabilities and even some specific financials in a publicly traded corporation. After about third earnings call (which happened a tiny bit before the trading window
225.
▲
by
p_l
7mo ago
As some have noticed, US writing about games is very console-centric
226.
▲
by
p_l
7mo ago
Well, here I am following what people who worked on CPUs at the time wrote. And from the point of microcoded system like x86 and 680xx were (including 68060) it is important to how many microinstructions your instruction stream will decode
227.
▲
by
p_l
7mo ago
From the first time the story surfaced, for spurious reasons[1] she was booked as fugitive, and that made it so that there was "no need" for normal timeframe of hearing. [1] The reason being that she was found in Tennessee while b
228.
▲
by
p_l
7mo ago
> Those addressing modes became a problem later, in the CPUs with pipelined execution and hardwired control, because a single instruction with such addressing modes could generate multiple exceptions in the paged MMU and because any such
229.
▲
by
p_l
7mo ago
Just remembered that part of the story: Part of the effort to ditch x86 was to destroy competition that existed due to second sourcing agreements. After already trying and losing in court the case to prevent AMD and others from making compa
230.
▲
by
p_l
7mo ago
Analysis of issues in making more performant 68k and VAX are major part of what led to RISC development, with complex addressing (even in earliest 68000) being part of the problem. People think of x86 as CISC when reading about CISC vs RISC
231.
▲
by
p_l
7mo ago
Notice I didn't write harder to optimize for - I am not talking about optimizing code , but optimizing the actual internal microarchitecture. Turns out m68k orthogonality results in explosion of complexity of the physical implementa
232.
▲
by
p_l
7mo ago
Harder to optimize at microarchitectural level because each individual instruction represents way more complex execution model, including to even decode what the CPU is supposed to do. X86 is comparatively simple, with limited indirect addr
233.
▲
by
p_l
7mo ago
68k was much harder to optimize than x86, being way more CISC-y 68k like VAX was seen as dead avenue not only compared to RISC
234.
▲
by
p_l
7mo ago
The reason I'm seeing "boiling the frog" is that tories did bunch of reforms, and were literally caught red handed with stuff like ordering a software vendor ensure the software would mistakenly bar people from getting servic
235.
▲
by
p_l
7mo ago
It used to be the case with intel macs and their atrocious confluence of cooling system, thermals, and power supply system (the CPU actually was not really to blame). But when RAPL and similar tools to throttle CPU are used, the CPU time ge
236.
▲
by
p_l
7mo ago
The process described is literally an attempt at canceling benefits in "frog boiling" method. If Tories went straight to canceling benefits, they would end up in trouble, by making worst possible process they could put it in terms
237.
▲
by
p_l
7mo ago
Merced (first generation Itanium) had hilariously bad performance, and its built in "x86 support" was even slower. HP-designed later cores were much faster and omitted x86 hardware support replacing it with software emulation if n
238.
▲
by
p_l
7mo ago
The deep and close relationship of Compaq with Intel meant that it also killed off Alpha, which unlike MIPS and PA-RISC wasn't going out by itself (Itanium was explicitly to be PA-RISC replacement, in fact it started as one, while SGI
239.
▲
by
p_l
7mo ago
Yes, with branch prediction and speculative execution too
240.
▲
by
p_l
7mo ago
Honestly what broke Itanium the most was the extreme market segmentation that made Itanium very expensive with no path to mass use. Resulting in claim like "it's pretty good DSP, but hilariously overpriced".
More ›