HNHacker News
TopNewBestAskShowJobs

tliltocatl

1,072 karma · joined June 23, 2024

submissionscomments
tliltocatl··on XOR'ing a register with itself is the idiom for zeroing it out. Why not sub?
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 encryption) would have low static and high dynamic.

tliltocatl··on XOR'ing a register with itself is the idiom for zeroing it out. Why not sub?
What's SMT in this context?
tliltocatl··on XOR'ing a register with itself is the idiom for zeroing it out. Why not sub?
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.
tliltocatl··on Planar maps: an interaction paradigm for graphic design (1989) [pdf]
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.
tliltocatl··on Not all elementary functions can be expressed with exp-minus-log
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 author's definition I've never met before, it apparently includes some multi-valued functions, which are quite unusual.
tliltocatl··on Tofolli gates are all you need
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 state. An irreversible process (that is, one that would force to macroscopically distinguishable states into a single one) is only possible if we conduct the "unknowness" aka entropy away from our computer - i. e. generate heat. Toffoli gate are reversible, and therefore in theory you can implement it in a way that is not subject to the Landauer limit.

Obviously, implementing one as a CMOS gate wouldn't be enough. Reversible gates would be very different. AFAIR they need to have a fan-out of one - you can't just wire an output to two inputs without losing reversibility.

tliltocatl··on What is RISC-V and why it matters to Canonical
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 abstracted away a lot of BIOS routines, so it would be easy to port MS-DOS to a non-IBM x86). But after IBM revealed MCA to show just exactly how much do they care about compatibility and platform openness, Intel realized they are missing out and cleaned up the MCA/EISA/VLB mess with PCI. Then Microsoft and Intel jointly released APM 1992 (which was clearly not enough), and then ACPI in 1996 (which is a total dumpster fire, but a sufficiently functional dumpster fire). I. e. ACPI and UEFI are exactly the product of the monopoly. M$/Intel profited from the abundance of cheapo white boxes, so it was in their best interest to come up with a standard even DELL can implement. The fact that AMD is going to implement the ACPI too wasn't much bother for Intel - they were so dominant that they could afford not to care.

On the other hand, ARM sells the cores to SoC vendors (and doesn't care much what becomes of it), SoC vendors ducktape the ARM cores to a bunch of Synopsys peripherals and sell the resulting SoCs to smartphone and car makers (and doesn't care much for the product). System integrators throw Android on top and sell it to the customers. Then Google, who get all the cream via Play, hides all the mess behind a thousand layers of Java abstractions.

DeviceTree is an offshot of Sun's OpenFirmware (and it leaves out all the hard stuff - OpenFirmware had Forth, DeviceTree expects the kernel to support every single brand of fan switch). OpenSBI is a disaster. I'm sorry, but what kind of bright mind came up with the idea of hiding damn *timer* behind a privilege switch? Timers were enough of a pain point on x86 already, then it settled on userspace-accesable RDTSC. RISC-V SBI? Reproducing x86 one stupid decision at a time.

tliltocatl··on On Division by Three
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 still possible, to check in O(1) extra space.

* s/6/9/ Typo, thanks apothegm.

tliltocatl··on Helium is hard to replace
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. semiconductors and lasers) where it is much more irreplaceable.
tliltocatl··on What is RISC-V and why it matters to Canonical
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 interest was to stay as compatible as possible. Its unlikely that another platform would be able to reach this state, the PC architecturing was subsidized from the M$ software monopoly that nobody would have wanted to suffer thru again.
tliltocatl··on Sports bets on prediction markets ruled to be "swaps," exempt from state laws
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 recover the loss?

Market works well on non-correlated risky affairs with a positive expectation (i. e. Age of Discovery marine trade, where it all started). It can't do anything about a fundamentally negative-sum game.

tliltocatl··on Why are we still using Markdown?
Because Markdown is quite readable in plaintext form with no Markdown-specific rendering at all. HTML isn't.
tliltocatl··on The Evolution of x86 SIMD: From SSE to AVX-512
> 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 problem delivering software/API part, Intel could but has too low of a market share, the rest are mobile IP core vendors with zero interest to provide compatibility.

tliltocatl··on CPSC Warns Consumers to Stop Using Male-to-Male Extension Cords
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 they can short-circuit between phases, but then released that's only a problem for Schuko, not NEMA). If you want to use a local generator, install a generator transfer switch.
tliltocatl··on Leaked Memo Suggests Red Hat's Chugging the AI Kool-Aid
Damn, here goes another distro.
tliltocatl··on We're pausing Asimov Press
> 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.

tliltocatl··on Axios compromised on NPM – Malicious versions drop remote access trojan
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).
tliltocatl··on LinkedIn uses 2.4 GB RAM across two tabs
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).
tliltocatl··on Looking at Unity made me understand the point of C++ coroutines
> 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/NT4.0, and these didn't support multicore, nor did most of OpenVMS machines where NT thread model originated run multicore (were there any multicore VAXen at all). The two main points for threads back then was to simplify concurrent IO and to be able to run a background computation without hanging the UI. Unix was different because it was initially oriented towards timesharing aka. running a single program for user, so threads were seen as redundant complexity (as were async IO - so even today "I want to run something yet be able get more user input at any time" can sometimes be a PITA).

And year, not everything needs scalability. Scalability is actually actively harmful for everything that's not a server. E. g. UI needs to be responsive - but that doesn't necessary mean "run on multiple cores", rather "being able to preempt low-priority stuff". And usually you don't want to deal with multicore synchronization.

MCUs rarely have multiple cores. Yet multi-threading is ubiquitous, and on most RTOSes threads are much closer to "green threads" than Windows ones. Through as I keep screaming in every coroutine thread, I really wish C stackless coroutines were a thing, you can't afford a stack for everything.

There are more to this world than the boring AWS crud.

tliltocatl··on The 'paperwork flood': How I drowned a bureaucrat before dinner
If you are being paid for making people's lives miserable, expect some misery in return. That's how it is.
tliltocatl··on Looking at Unity made me understand the point of C++ coroutines
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.
tliltocatl··on Looking at Unity made me understand the point of C++ coroutines
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.
tliltocatl··on Looking at Unity made me understand the point of C++ coroutines
Because they are unstructured and non-modular. And yes, graphical notation sucks.
tliltocatl··on Missile defense is NP-complete
Vastly cheaper and more powerful control and guidance systems (and cheaper, if only a bit cheaper, radars too).
tliltocatl··on Missile defense is NP-complete
You are confusing reason as in "why they did it" vs "why they ought to do it".
tliltocatl··on Wayland set the Linux Desktop back by 10 years?
I don't disagree in principle, my workflow is pretty similar, most of the integration part goes thru kitty for me too. But I also need need screenshot and screencast - which need special permission in Wayland because reasons. Fine for me, but I can imagine some having their workflow around specific tools, that might or might not work with Wayland - and apparently, Wayland team thinks it's not their problem.

And I personally need kicad - it doesn't support Wayland at all because of some mouse-related stuff. Again, Wayland team thinks it's not their problem.

Then I had a lots of issues with a graphics tablet. Yes, it's a cheap chinesium knock-off, but it does work on X11. Wayland - no chance and it's obviously not their problem.

So I dropped Wayland altogether and went to X11/herbstluftwm. Was a few years ago, but I didn't bother to go back since - why should I? These aren't their problem, but now I don't use Wayland anymore, so these aren't my problem either.

What I'm trying to say, "hundreds of thousands of gamers stress-testing" have very little to say about usability. Yes the graphics part is excellent, nobody is denying that. There is more to a WM then graphics.

tliltocatl··on Wayland set the Linux Desktop back by 10 years?
> Input is an afterthought

This. You need more than graphics to have a windowing system. Wayland team threw out X11, did graphics and left the rest for the others to figure out.

tliltocatl··on Wayland set the Linux Desktop back by 10 years?
We basically have it, it's called Blink (and it's a dumpster fire for unrelated reasons).
tliltocatl··on Wayland set the Linux Desktop back by 10 years?
Games isn't exactly the best stress test for a windowing system. Most (if not all) run in full-screen mode and don't really use it much after the launch. And that's not what desktop computing is about. You want to run multiple programs, you want them to integrate with each other. But games don't need any of this.
tliltocatl··on Pet dad turns to AI chatbot to cure sick pup using custom mRNA vaccine [video]
I don't see how LLMs are relevant to this. It will become an issue sooner or latter - bio isn't anything like metallurgy or semiconductors, it doesn't require huge factories so zero hope of non-proliferation.
← PreviousPage 5 of 16Next →