Hacker Newsnew | past | comments | ask | show | jobs | submit | flykespice's commentslogin

Really, I don't get why would anyone buy these priced RISC-V development boards over much cheaper ARM-based variants that are faster.

What is the target audience for these development boards anyway?


People who think "it's open source bro! Boo ARM!" without understanding how peripheral IP works.

I'm not obliged to mourn someone that spread hatred against the group of people I belonged to, even moreso when they didn't show any regret about their words at the end of their lifetimes

Same thing with Taito, founded by ukranian jew Michael Kogan. The company that created the phenomenal Space Invaders and spark the japanese video game industry from a niche hobby to mainstream.


The behemoth that is autotools mostly helped to conceal the backdoor (and contributed to the payload)

It's an old legacy technology that needs to die out from all forms of distributions (looking at you GNU)


Recently, RealLifeLore has been my to go channel to watch the current state of geopolitics thorough the world, I discovered them through the video of "How Rwanda is Conquering Their 100x Larger Neighbor" (https://www.youtube.com/watch?v=0N34UFbWpFk)


Chip8 is the rite of passage for many emulator devs due to its simplicity, it can be implemented on virtually every 1 cent microcontroller out there.

It should've had a more dedicated vibrant community if it weren't the many incompabilities among the different emulators implementations out there, all due to people using cowgod's chip-8 tecnical reference as the single source of truth[0], which itself is based on David Winter's original implementation which contained a few inaccuracies on some instructions behavior from the original COSMAC VIP interpreter.

[0]: http://devernay.free.fr/hacks/chip8/C8TECH10.HTM


It's rather disheartening to see new chip8-related projects which reference Octo, modern test ROMs written with Octo, and still see a citation for cowgod's egregiously incomplete and misleading documentation.


Damn Small Linux was one of the first distros I tried out as teenager with a LiveCD. It's sad it fell out due to his lead being rather an asshole with his contributors and overall incompetent.

BTW, one of former core contributors went to make their own distro called TinyCoreLinux.


It doesn't makes him less a hero rescuer if many others were still involved, in fact, every diver who volunteered on the rescue effort is a hero on my book.

> There were teams from 11 countries, Musk included.

What did Musk help exactly, other than coming up with an impractical solution, then calling the hero rescuer a "pedo guy" after getting his big ego bruised?


What did remaining 10k people help exactly?

Ego's has been bruised for sure. Fact is pedo guy started this first, got called out, tried to sue and lost.


I'm curious, why is that?

I know x86-64 zeroes the upper part of the register for backwards compability and improve instruction cache (no need for REX prefix), but AArch64 is unclear for me.


It's to break dependencies for register renaming. If you have an instruction like

  mov w5, w6 // move low 32 bits of register 6 into low 32 bits of register 5
This instruction only depends on the value of register 6. If instead it of zeroing the upper half it left it unchanged, then it would depend on w6 and also the previous value of register 5. That would constrain the renamer and consequently out-of-order execution.


I don't know either, but why wouldn't backwards compatibility apply to aarch64? It too is based on a pre-existing 32-bit architecture.


I don't think it's backwards compatible the same way x86-64 is.


You really want to avoid a dependency on prior content of the destination register, to allow renaming and maximize out of order scheduling.


He has a pattern of taking any bit of criticism of his language on bad faith, and immediately goes all defensive accusing the criticizer of being a psyop working with a rival language.

This is all childish and unacceptable behavior.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: