Live data from Hacker News

Hot Dog Linux – Horrible Obsolete Typeface and Dreadful Onscreen Graphics

hotdoglinux.com

91–100 of 167 posts

Re: Hot Dog Linux – Horrible Obsolete Typeface and Dreadful Onscreen Graphics

#92
post #88
post #78

Earlier quoted context omitted.

I use jsonlines on those occasions https://jsonlines.org/examples/

This is nice. But less space-efficient than CSV when its strictly tabular, since CSV has columns legend on first row allowing 'pure' rows, whereas JSON will have to key every field, on every row.

Your use case is literally the first item in the link I shared (and the reason I shared that link too):

  ["Name", "Session", "Score", "Completed"]
  ["Gilbert", "2013", 24, true]
  ["Alexa", "2013", 29, true]
  ["May", "2012B", 14, false]
  ["Deloise", "2012A", 19, true]

Re: Hot Dog Linux – Horrible Obsolete Typeface and Dreadful Onscreen Graphics

#93
As I’m growing older, I appreciate those typefaces for the sheer fucking contrast and readability they have. On low DPI screens, I seek bitmap fonts for the UI (and it disappoints me that the support for them in toolkits seems to be getting shoddier, to the point that it’s easier to use TrueType fonts that mimic bitmaps); on high DPI screens, I’m using serif fonts.

I’m toying with the idea of purely black and white themes so I can use them on my eInk screens, too, pity there’s so little time.

Re: Hot Dog Linux – Horrible Obsolete Typeface and Dreadful Onscreen Graphics

#94
post #21

Earlier quoted context omitted.

"badly-written Perl scripts" They do appear to be badly written on purpose, like this "hotdog-aboutDrives.pl" one: https://github.com/arthurchoung/HOTDOG/blob/master/hotdog-ab... The entire script is this: #!/usr/bin/perl $str = `df`; print $str;

The rationale: https://hotdoglinux.com/PerlAndUseStrict/index.html " Most tutorials about Perl will tell you to always 'use strict' or something to that effect. However, the general rule for HOT DOG Linux is to not 'use strict'. The reasoning behind this is that each Perl script should be as simple as possible. It should be simple enough to not need 'use strict'. If it gets to the point where the script would be easi…

If a brick could fall on you and kill you, just use smaller bricks.

Re: Hot Dog Linux – Horrible Obsolete Typeface and Dreadful Onscreen Graphics

#96

As I’m growing older, I appreciate those typefaces for the sheer fucking contrast and readability they have. On low DPI screens, I seek bitmap fonts for the UI (and it disappoints me that the support for them in toolkits seems to be getting shoddier, to the point that it’s easier to use TrueType fonts that mimic bitmaps); on high DPI screens, I’m using serif fonts. I’m toying with the idea of purely black and white t…

I'm using a nice bitmapped font called knxt by Constantine Bytensky.

Re: Hot Dog Linux – Horrible Obsolete Typeface and Dreadful Onscreen Graphics

#97
post #21

Earlier quoted context omitted.

"badly-written Perl scripts" They do appear to be badly written on purpose, like this "hotdog-aboutDrives.pl" one: https://github.com/arthurchoung/HOTDOG/blob/master/hotdog-ab... The entire script is this: #!/usr/bin/perl $str = `df`; print $str;

The rationale: https://hotdoglinux.com/PerlAndUseStrict/index.html " Most tutorials about Perl will tell you to always 'use strict' or something to that effect. However, the general rule for HOT DOG Linux is to not 'use strict'. The reasoning behind this is that each Perl script should be as simple as possible. It should be simple enough to not need 'use strict'. If it gets to the point where the script would be easi…

Since the smaller scripts run in separate processes, there is in fact a safety benefit to the break-up, which compensates in some way for the lack of strict. Processes are isolated; you know that a function call in one script will not misuse a function in another. Or that a global variable defined in one script can't be modified or accessed in the other. The scripts can only communicate via external mechanisms: command line arguments, environment variables, files/pipes/sockets, more rarely shared memory.

Unix was built using an extremely unsafe language. Yet it reached a decent level of reliability in just a few years, a lot of which was owed to the system applications being small programs isolated into separate processes.

Re: Hot Dog Linux – Horrible Obsolete Typeface and Dreadful Onscreen Graphics

#99

Earlier quoted context omitted.

Its an absolutely bonkers aspect of US society. Its not that one needs to be blind to "race", and who could be blind to differences in skin colour? Its that Americans seem to be taught that it is so very important, and that instead of applying situational relevancy, they default to cultural relevancy. So race and skin colour gets mentioned all the time, even by people who aren't bigoted. This can be seen in their new…

Not only that, Americans view everyone else and their cultural problems as being similar to theirs. Eg: Journalists who equate India's caste system and racism and writing opinion pieces. (both are terrible, but american journalists understand shit about caste).

Yes, another example is the minor kerfuffle the Game "kingdom come deliverance" had about it not having any darker skin toned NPCs in it. It is made by a Czech developer and set in a semi-historical 12th century setting. From an American perspective that looked wrong enough to be called racist.

Re: Hot Dog Linux – Horrible Obsolete Typeface and Dreadful Onscreen Graphics

#100
post #78
post #43

Earlier quoted context omitted.

> CSV files.... that encode JSON?! We need a new schema language with the ability to specify such cross-format …formats.

I use jsonlines on those occasions https://jsonlines.org/examples/

That's like a file with S-expressions, only worse (because those already existed, whereas this had to be made up as a new thing, without offering any improvement).
Post reply on HN