> I made a chatbot that rolled dice, and it was constantly criticized for being "broken" because four 3's would come up in a row.
> These accusations would come up even though they (all being computer science majors) know it's possible (although unlikely) for these events to happen. They just don't trust the black box.
This reminds me of a talk [1] given at Game Developer's Conference (GDC) about the game Civilization, in which the Sid Meyer -- creator of said game -- spent a bit of the time talking about the difference between fairness and perceived fairness. The talk is only an hour long and worth watching.
> There's another one (maybe the same guy?) who moderates with a vengeful bias on Reddit. That kind of shit-throwing is anathema to a large company.
Also due to some being unhappy with the moderation of /r/bitcoin there's a separate community called /r/btc. Then again, there are many communities on Reddit that have split up due to disagreements about moderation, such as for example /r/meirl vs the previously vastly more popular /r/me_irl [1]. (The latter of these still has about 3x the amount of subscribers though, but /r/me_irl has grown to become large indeed.)
When I first switched from the terminal emulator that came with the first DE I was using (gnome 2?) to urxvt, it seemed very fast. When I later switched to Terminology, it seemed even faster. I've stayed with Terminology. I agree it'd be very interesting to see a proper comparison between Terminology, urxvt and others.
> Also with a few web sites I might upvote it first and then read it :-|
I can neither confirm nor deny that I do this too but I can say that I think it makes sense to do this, and I would go as far as to say that I think it's healthy for the HN community that stories get upvoted by people who have not yet read the story in full, as long as it doesn't happen too much -- while a story might turn out to be lacking or even factually incorrect in some way I think there is opportunity for interesting discussion to be had as long as the topic at hand is interesting.
Filling the indent area with dots is not a sensible default IMO. Often when I work on a query I am going to reuse it in an application. If PgAdmin III or psql filled the indent area with dots then they would be included when I copied the query I'd written.
Even though I always reformat the query, and even though the text editor I use -- vim / neo-vim -- supports rectangular text selection, I would be annoyed at such dots.
Don't fill it with dots, use it. This is my shell prompt. I break after
the '%', so that long commands use as much of a line as possible, and I
break before the prompt, because I like to visibly separate operations.
If you copy the entire line, stuff is arguments to the ‘:’ command, which does nothing. (This does mean stuff can't contain unmatched shell special characters.)
I think this was invented in the Blit era by someone I've forgotten.
The Python REPL notoriously uses >>>/... like in the screenshot, ẃith the effect that e.g. IPython has a special paste-from-repl magic just to remove these.
Or alternatively the prompt character could start on a new line. That way you can have smaller windows fit more query per line with less space wasted on white-space.
With the "newline after prompt" scheme, you only get one extra line per query.
Which, if the query is long (e.g. longer than 20+ lines) it's not gonna make any difference anyway -- it's not like it matters if you can fit e.g. 24 or 23 lines of a 30 line query (besides, the result rows are gonna take much more vertical space, further making the measly 1 extra line issue moot).
As for for multiple small queries (and one extra line after each of those prompts), you can always scroll. And, again, the results are gonna take far more vertical space than the single extra line per prompt.
And, of course, with the full horizontal space available (and not half wasted by dots) you get to fit more characters in each line, and thus your queries will probably end up using FEWER lines.
So, not only the extra line from the "newline after prompt" is no big deal vertical-space wise, but the dot scheme wastes MORE vertical space AND renders queries unpastable.
While you are data gathering, I will half-vote the other way.
In VIM I make my whitespace visible, and just live with the consequences when I cut an paste. That said, I most of my empty spaces are still invisible, I only show tabs and trailing spaces.
You can change this to an empty space via the config file right now. In ~/.config/pgcli/config look for continuation prompt and set it to empty string.
Also some of us don't even like to have the software localized. English is not my mother tongue and it's not an official language where I live either but I always set the system language to American English on my computers and devices.
You are right. Internationalization might be the word for what I'm talking about, though some might argue that that's not correct either because they might say that l10n is a subset of i18n. Not quite sure. But anyways, yes, l10n in the sense that it works in my part of the world is desirable. I18n if only taken to mean translation (and things like right-to-left and such which arise from supporting certain languages) is what doesn't matter to me.
> These accusations would come up even though they (all being computer science majors) know it's possible (although unlikely) for these events to happen. They just don't trust the black box.
This reminds me of a talk [1] given at Game Developer's Conference (GDC) about the game Civilization, in which the Sid Meyer -- creator of said game -- spent a bit of the time talking about the difference between fairness and perceived fairness. The talk is only an hour long and worth watching.
[1]: https://www.youtube.com/watch?v=AJ-auWfJTts