non-e-moose

11 ms·

1.
by non-e-moose 2y ago
Former AMD employee here (2007-2012) AMD 'dropped the ball' BADLY when (2012) then-VP Ben Bar-Haim decided to do a software purge, and focused on retaining the over-bureaucratic folks of ATI/Markham. Net result: NVidia was (
2.
by non-e-moose 2y ago
Seems to me that the goal is to build a funding model. There CANNOT be such a thing as "Safe Superintelligence". A ML system can ALWAYS (by definition of ML) be exploited to do things which are detrimental to consumers.
3.
by non-e-moose 3y ago
Unaligned pointer accesses are for 80386 bozos. Period End of story. If you want to play in 64-bit land, live by the architectural rules. If you do not, your code will likely die. And you need to "Lurn" a lot
4.
by non-e-moose 3y ago
Silly Rabbit - absolutely accurate times are a security problem. CPU designers (even waay back in Alpha @ DEC) intentionally introduced clock jitter, just to prevent total predictability. For x86, I think if you performed 3-4 of them, and
5.
by non-e-moose 4y ago
Count the number of "authors". Anything above 100 is absolutely garbage More then 10 is probably irrelevant and unproveable.
6.
by non-e-moose 6y ago
Because EMACS is not an efficient programming languge
7.
by non-e-moose 6y ago
I'm not sure I see the benefits here unless you are buying completely in to: Emacs, and Java and ignoring performance/overhead. Closure is implemented in Java; and the only apparent way to write it is via Emacs. The zero-eth issu
8.
by non-e-moose 6y ago
Kenoph: is your company looking for people with experience in binary translation/compilers? My URL: http://gorton-machine.org/rick/index.html and resume hangs off of that. Regards, Richard
9.
by non-e-moose 6y ago
Out of curiosity, what is the use case? RISC-V is new enough that it is unlikely to be needed for 'dusty-deck' (source code long lost) that was needed for the VAX --> Alpha binary translators, or for Univac (ones complement!) t