ninjalj

general recent conversations

Discussion on question by Noob_Guy: W…

Imported from a comment discussion on retrocomputing.stackexch...

ninjalj

Jun 17, 2023 08:28

Apparently, DEC also thought of this, and some years later, when memory and other components were cheaper, created the DEC Rainbow, which was both a terminal, and a computer.

Discussion on question by Evan Carrol…

Imported from a comment discussion on retrocomputing.stackexch...

ninjalj

Jan 17, 2021 13:44

@EvanCarroll: bash doesn't descend from the Almquist shell. In fact, according to Wikipedia, the Almquist shell was only released a week before bash.

Discussion on question by user20534: …

Imported from a comment discussion on retrocomputing.stackexch...

ninjalj

Jan 16, 2021 19:08

Linux can run on processors without MMUs (see uClinux for historical details)

Discussion on answer by Chromatix: Wh…

Imported from a comment discussion on retrocomputing.stackexch...

ninjalj

Sep 14, 2020 15:27

@CarsonGraham: you are adding s.b twice, and not adding s.d, which may be what makes the compiler output harder to understand. Also, the struct is not passed on the stack, but on registers rdi and rsi, needing shifts to extract the integers from the upper part of registers. Knowing that, the code at -O3 is quite straightforward.

Discussion on question by JoelFan: Co…

Imported from a comment discussion on retrocomputing.stackexch...

ninjalj

Mar 20, 2020 19:36

@lvd: IDK about complex, but it is more error prone. When support for UTF-8 is broken, it's obvious with the first character outside of ASCII. When support for UTF-16 is broken, ...

ninjalj

Mar 20, 2020 14:06

Re: Much later, UTF-8 was invented [...] UTF-8 was invented quite early, during 1992, and presented in 1993 according to Wikipedia. UTF-16 came later, again according to Wikipedia, for Unicode 2.0 in 1996. UTF-8 is the best solution for pretty much all applications, since there is no special treatment of higher-valued characters and no byte-order-mark needed. As a bounus, it's backward-compatible with 7-bit ASCII.: of course there is special treatment of higher-valued bytes, it's just used much more often than surrogates, and more immediately obvious when it' broken...

ninjalj

Mar 20, 2020 14:06

...being backwards compatible with ASCII is not a bonus, it is the essential feature of UTF-8, which started its life as UTF-FSS, filesystem-safe, with path separators and string terminators being the same in ASCII and UTF-FSS.

Discussion on question by jwzumwalt: …

Imported from a comment discussion on retrocomputing.stackexch...

ninjalj

Mar 3, 2018 13:34

@IlmariKaronen: I remember a PC joke program that displayed a message "your PC is now turned into a washing machine", and used the floppy drive to make spin cycle like sounds.

Discussion on answer by jlliagre: Why…

Imported from a comment discussion on unix.stackexchange.com/q...

ninjalj

Dec 24, 2017 12:22

@matt: the point being that you could insert blank lines easily by pushing the lever repeteadly, without moving the carriage.

Discussion on answer by Amadeus: Kill…

Imported from a comment discussion on worldbuilding.stackexcha...

ninjalj

Dec 15, 2017 21:37

@gerrit: IIUC, fertility rate decline tends to follow mortality rate decline, not wealth. Apparently, people don't need that many children if they know the ones they have will survive into adulthood.

Discussion between wizzwizz4 and Denk…

Imported from a comment discussion on codegolf.stackexchange.c...

ninjalj

Mar 15, 2016 23:24

"clamping" en.wikipedia.org/wiki/Saturation_arithmetic

Stack Overflow en español

Chat de la comunidad de Stackoverflow en español. A veces char...

ninjalj

Feb 29, 2016 20:03

@jasilva neocomputer.org/projects/et

ninjalj

Dec 12, 2015 23:05

A eso (~) por aquí se le suele llamar virgulilla, tilde se suele usar para el acento agudo (´).

ninjalj

Dec 7, 2015 19:17

@tchrist ¿ dols → duelo | dolors → dolor?

Discussion on answer by Thomas Pornin…

Imported from a comment discussion on security.stackexchange.c...

ninjalj

Feb 27, 2016 15:11

Judging by the amount of ArrayIndexOutOfBoundExceptions that I've seen, the offender that should be shot is not the offending code, but the offending programmer, possibly with a nerf gun.