inkyoto

17 ms·

181.
by inkyoto 1y ago
> Are you well-read enough into the platform so that you can attest to it requiring no manual code optimisation for high-performance datapaths? Yes. > Have they really cracked it at homogenous computing […] Yes. > have it emit effi
182.
by inkyoto 1y ago
The cited article is pretty clear: the M1 Max maxes out at (approximately) 100 Gb/sec per a single CPU core , 243 Gb/sec per a CPU cluster , and 409 Gb/sec per the entire SOC . They did not (or, rather, could not) measure
183.
by inkyoto 1y ago
> […] but how much can your code actually use? All of it, and it is transparent to the code. The correct question is «how much data does the code transfer?» Whether you are scanning large string ropes for a lone character or multiplying
184.
by inkyoto 1y ago
Because until the C1, Apple did not have their own, and there were not that many viable options available with Qualcomm 5G modems being the «best» (however one defines it) and the fastest albeit power hungry and running very hot at high spe
185.
by inkyoto 1y ago
As a constrasting comparison data point, a Nokia 8800 cost around USD 900 in 2005 when it launched, which is approximately USD 1450 in the 2025 USD. The buyer would get a chromium-plated metal case within which a slightly fancier version of
186.
by inkyoto 1y ago
Today's sunscreens are complex cocktails of different molecules. The most advanced and efficient ones use both, inorganic and organic, chemicals, e.g.: Zinc oxide – for the broadest UV-A and UV-B absorption. Titanium dioxide – f
187.
by inkyoto 1y ago
For one, it is a US study. In Australia, anyone will get sunburnt , and moreso in summer. Going to an Australian beach at the height of the summer is akin to getting irradiated with a UV gun of epic proportions. The article also notes the
188.
by inkyoto 1y ago
I would say it is a niche solution that solves a specific problem. Modern data sources increasingly lean towards and produce nested and deeply nested semi-structured datasets (i.e. JSON) that are heavily denormalised and rely on organisatio
189.
by inkyoto 1y ago
That is not how a VMM subsystem works, irrespective of the operating system, be it Linux, or Windows, or a BSD, or z/OS. The list goes on. Access to a page that is not resident in memory results in a trap (an interrupt), which is handl
190.
by inkyoto 1y ago
It also supported overlays on the PDP-11, although not in the beginning. I do not think that anybody makes use of the overlays anymore.
191.
by inkyoto 1y ago
> The original design of UNIX ran on machines without an MMU, and they had fork(). The original UNIX also did not have the virtual memory as we know it today – page cache, dynamic I/O buffering, memory mapped files (mmap(2)), shared
192.
by inkyoto 1y ago
> It's also why I urge junior engineers to not rely on AI so much because even though it makes writing code so much faster […] I am afraid, the cat is out the bag, and there is no turning back with GenAI and coding – juniors have go
193.
by inkyoto 1y ago
> Our job in the very lucky liberal West is to keep what our forefathers won, and then push it further to show why our values are worth the sacrifice in copying It was the liberal West who helped China build the Great Firewall – Cisco, S
194.
by inkyoto 1y ago
z Series have used both, POWER and TELUM (I and II) processors. For many years, the 64-bit extension of the original S/360/370/390 architecture was emulated in the software layer via the static binary translation – just like
195.
by inkyoto 1y ago
This is where Oracle has a upper hand in the materialised view department: a materialised view can be refreshed either manually or automatically, with both, incremental and full, refresh options being available.
196.
by inkyoto 1y ago
Yes, that is the problem that is impossible to address with git due to its decentralised nature, which is a feature. A typical scenario that disqualifies git in certain scenarios is as simple as a master repository and a few local copies of
197.
by inkyoto 1y ago
> It’s just a social network for recruiters it’s not as complicated as they like to pretend. Dismissing this as «just a social network» understates the real constraints: enormous scale, global privacy rules, graph queries, near-real-time
198.
by inkyoto 1y ago
You have responded to the wrong comment. I have presented a case that concerns ledger databases, not the blockchains. If one doesn't understand the difference between the two, it is probably a good idea to refrain from chiming in.
199.
by inkyoto 1y ago
I respectfully disagree. Consider a leaf commit (or a leaf which is a subtree of commits). I am a person with nefarious intentions, and I delete the leaf commit, forcefully expire the reflogs, or force garbage collect them. At that point, t
200.
by inkyoto 1y ago
No. Official and legal records detest the in place changes, love a full history of changes, and also love to walk the entire history of changes back. You do not have to convince me, you can talk to the state auditors instead to get their pe
201.
by inkyoto 1y ago
Very much relevant. The definition of the ledger database includes immutability of datasets as a hard constraint[0][1]. The mere fact that the git commit history can be altered automatically disqualifies git from being an acceptable alterna
202.
by inkyoto 1y ago
There is no such a thing as «subsequent commits» in git. Commits in git are non-linear and form a tree [0][1]. A commit can be easily deleted without affecting the rest of the tree. If the git commit represent a subtree with branches dangl
203.
by inkyoto 1y ago
No snark required. Whatever the reason for discontinuing QLDB was, it has been replaced with the pgAudit[0] Postgres extension in AWS. I did look into using QLDB for a project involving the management of financial records about 4 years ago
204.
by inkyoto 1y ago
I have heard an argument for git before, and it is a viable fit for some use cases. The problem, however, stems from the fact that the git commit history can be modified, which automatically disqualifies git in many other use cases, e.g. of
205.
by inkyoto 1y ago
> No one knew what “blockchain” was, how it worked, or what could be used for. Not the blockchain itself, but the concept of an immutable, append only, tamper-proof ledger underpinning it is a very useful one in many contexts where the q
206.
by inkyoto 1y ago
OCaml was[0] very popular in the high-frequency trade programming, especially because of its high performance and predictable latency despite having a garbage collector, plus, of course, because of the correctness of the code written in it.
207.
by inkyoto 1y ago
> FreeBSD code is also in iOS and macOS via Darwin […] It is a common belief that Darwin has allegedly descended from FreeBSD, but there is not a lot in there: a pretty ancient snapshot of the FreeBSD userland, another snapshot of the TC
208.
by inkyoto 1y ago
Ah, the whisperings of silicon rebellion – RISC-V, that glorious open chalice of instruction set purity, now bearing the sigil of RVA23 and galloping toward the high-performance plateau. The prophecy smells of burnt wire and inevitability:
209.
by inkyoto 1y ago
> A. you're wrong, I've recently ran into Rosetta throttling […] Can you please define and explain the meaning «Rosetta throttling»? Rosetta 2 is static binary translation + JIT optimisations at the run time. Is Rosetta injecti
210.
by inkyoto 1y ago
> Main deal breaker for me when I tried it was I couldn't talk to multiple models at once […] … which seems particularly strange considering the size of the cloned GitHub repository to be 1.8GiB which swells up to 4.8GiB after runni

More ›