Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
yaantc
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
91.
▲
by
yaantc
4y ago
AMD fabs at TSMC (and GloFo for the I/O die before, but this has moved to TSMC too recently) and has been using chiplets. TSMC does have 2.5 and 3D packaging for this. But it's still up to the fabless client of TSMC to design the
92.
▲
by
yaantc
4y ago
Memories have their specialized processes indeed, but there are other reasons to specialize. New nodes are fine for logic, but it takes time for analog IPs to move to new nodes (and some may not). So what AMD did, using an advanced node for
93.
▲
by
yaantc
4y ago
It shows that the difference in efficiency of doing a custom ASIC at Youtube scale saves more money that what's required to design and manufacture their custom chip. But this is different from the trend cost per transistor (particularl
94.
▲
by
yaantc
4y ago
This is the number of transistors per device only. There is no notion of "minimum cost point" as in Moore's 1965 paper, where the "law" comes from. See my other post in this thread on this and why the economic part
95.
▲
by
yaantc
4y ago
Moore's 1965 paper was literally about "the complexity for minimum component costs" [1]. So you're right that transistors on a chip is more applicable then just die density. But as too often nowadays you left out the &qu
96.
▲
by
yaantc
4y ago
The article [1] is a bit old (2010) but still relevant to answer your question. It compares the efficiency of a HD.264 implemented first on a general purpose CPU, then on a SIMD+VLIW DSP, then on the same DSP with additional optimized instr
97.
▲
by
yaantc
4y ago
Yes indeed, LTE max cell size is 100 km. There's a system using LTE to backhaul Internet traffic from planes (WiFi in cabin, with a LTE to the ground), working with larger cells of up to ~900 km from memory, but it doesn't use sta
98.
▲
by
yaantc
4y ago
Arizona and Ohio are silicon chip fabs, in Italy it would be a packaging fab taking silicon dies from other Intel fabs to produced packaged chips. Packaging can be pretty high tech and challenging nowadays, but it's not the same cost a
99.
▲
by
yaantc
4y ago
Seconding `rr` as suggested by @tux3, it's great for debugging. Also, the sanitizers for GCC and Clang ( https://github.com/google/sanitizers ), and the Clang static analyzer (and tidy too) through CodeChecker ( htt
100.
▲
by
yaantc
4y ago
FIDO allows to authenticate to an identity, which ideally is securely stored in a token and cannot be cloned or stolen. This identity is only an large, arbitrary number and that's all. This is not enough here. The example provided (b
101.
▲
by
yaantc
4y ago
A static analyzer does what is called "abstract interpretation". A good introduction on the principles is [1], from pioneers in the field. Very briefly, the analysis tries to approximate the "states space" for the progra
102.
▲
by
yaantc
4y ago
I'm very happy with the Clang static analyzer used with Z3 in the recommended way (for verification, not as the main constraint handler) through CodeChecker [1]. We use it with "cross translation unit" (CTU) support, to analy
103.
▲
by
yaantc
4y ago
Possibly, but I won't argue about hypothetical kinds of bad when a runtime issue happen ;) The point I tried to make was that you want neither for such use cases. Hence compile time verification (type base, static analysis, proofs for
104.
▲
by
yaantc
4y ago
You need to consider not just the memory access itself, but the consequences of preventing it. With a compile time check, there's a development cost but absolutely no runtime consequence. With a dynamic check, sure the memory access is
105.
▲
by
yaantc
4y ago
> It does not matter at which point the unsafe action is stopped. It does in practice. With a compile time check the issue simply cannot happen, and there is no need to deal with it in the code or at system level. With a runtime check th
106.
▲
by
yaantc
4y ago
From Emacs 28 onward, set 'dired-kill-when-opening-new-dired-buffer' to 't'. It will kill the previous buffer when opening a new directory.
107.
▲
by
yaantc
4y ago
I used to use jed instead of nano for quick edits, but same idea really. Then one day I realized that "emacs -nw -Q" starts subjectively instantly, and is also immune to a borked configuration ("-Q" skips it). So I just
108.
▲
by
yaantc
4y ago
The company is Amarisoft: https://www.amarisoft.com/ It's not SaaS, it's a software solution running on Intel PC/servers. You plug a (high end) SDR or remote radio head system to feed the PC with the samples,
109.
▲
by
yaantc
4y ago
No the same, lsp-mode is part of the MELPA archive not GNU ELPA. So it's easy to install too but MELPA has no package signature verification. For commonly used packages I don't think it's a big problem, any funny business wou
110.
▲
by
yaantc
4y ago
It's moving fast, and the experience will depend a lot on the LSP server itself now. As for me, I've recently switched to LSP with eglot for C, C++ (clangd) and Python (pyls). The experience is good, in that it's easy to forg
111.
▲
by
yaantc
4y ago
eglot is part of the GNU ELPA packages archive, managed by the people doing Emacs. It's possible to install it from the Emacs package manager, and the package will be signed and verified. So although it's not part of the official
112.
▲
by
yaantc
4y ago
Another open source alternative is CodeChecker [1] with the Clang static analyzer [2]. Make sure the Clang toolchain has been compiled with Z3 [3] support for better results (it's the case in Debian stable), particularly for code doing
113.
▲
by
yaantc
5y ago
Both core and RAN have user and control planes: the control plane is for configuration and management, and the user plane for carrying user data. This user data must go through the radio access network (RAN) and the core too. The split betw
114.
▲
by
yaantc
5y ago
Yes, it's changed recently as Alt was interfering with too many applications (e.g.: Inkscape use it). Using the Super (Windows) key is less problematic. So it depends on your KDE version. Or you own settings: I have an "old"
115.
▲
by
yaantc
5y ago
I don't remember seeing a criticism of OOP that is a criticism of encapsulation. Everybody tends to agree that encapsulation is desirable. It seems to me criticisms of OOP are that it rolls too many things into one construct, the class
116.
▲
by
yaantc
5y ago
On this topic the following paper is interesting: https://www.researchgate.net/publication/220770895_Understan... They work on an H264 encoder, starting from a software implementation and adding hardware support progre
117.
▲
by
yaantc
5y ago
To me, it seems like an "analog" cargo cult thing. A lot of audiophiles simply don't get the digital transition. In the old times, the musical signal was analog and any impairment was a degradation. Audiophiles went to great
118.
▲
by
yaantc
5y ago
In many places yes, but still with a much reduced bandwidth allocations. Newer generations increase the spectral efficiency, so more throughput can be supported on the same spectrum. So the operators tend to move spectrum from old to new ge
119.
▲
by
yaantc
5y ago
Thanks for your work. And I have to say that for internal development, when there is no need for the latest features, it's much easier to develop based on a Debian release as much as possible. A stable distribution provides an easy to
120.
▲
by
yaantc
5y ago
I used to use a light editor for quick edits, jed, but now I use Emacs too. It turns out that Emacs in text mode without a full configuration (so: "emacs -Q -nw") starts nearly instantly on a few years old laptop, so I just aliase
More ›