1,498 karma · joined September 21, 2019
I was not able to use comma 、 and the period 。 because I think FastMail disables searches on common punctuations, so those matched nothing.
(In case people are wondering, I sometimes scan through my Spam folder to check for false positives, i.e. things which were incorrectly marked as spam. It's difficult to do that when it is flooded with Japanese spam.)
The second one 'す' matched only 10 Japanese spam messages.
UPS has dropped the last 3 of my packages to my neighbor's house. They try to be helpful though. They took pictures of the packages, sitting against various walls and doors that I didn't recognize at all. I had to guess which of my neighbors.
I had never seen 'pc' used as a short hand for percent (%) until recently in an article (can't remember where), where they used 'pc' repeatedly. Unfortunately the article was also talking about the 'pence' of money, so I found it impossible to figure out from context whether they were talking about a 'pence' or a 'percent'.
In the US, I have seen 'pct' used instead of '%', but not too frequently. I had never seen 'pc' used until recently.
In practice, it may not work properly even on their "supported" models. For example, sound does not work on my Dell E7270. Secondly, you must be willing use the Chrome browser. I will not because Chrome no longer has the option to always show the scrollbars. I am convinced that modern UX/UI designers hate their users.
Case in point: I tried to install ChromeOS Flex on one of my laptops. After booting from the USB drive, the installer went through a series of screens. On the 3rd or 4th screen, it would hang and make no progress. I rebooted and re-installed. Same thing. Tried a third time. Same thing.
On the 4th try, I accidentally discovered that the dialog box had an invisible scrollbar. WTF. If I two-finger scrolled on the dialog box after moving the mouse pointer into it, it would reveal some additional text on the bottom which indicated that it was not hanging but doing some work.
After I had finished installing ChromeOS, I discovered ChromeOS has a Settings option to "always display scrollbar", but the Chrome browser completely ignores that flag. Awesome. I blew away ChromeOS Flex on my laptop.
The bus-factor of one was probably the main reason I did not choose them when I de-googled myself during Google's fiasco with their "free forever" Legacy GSuite termination. I found out a year or two later that they had rescinded their termination, but it was too late. I had migrated out of Google, to my relief.
1) Small projects, owned and maintained by a single person, with maybe a few random contributors.
2) Medium-sized projects maintained by handful of developers, without much organizational structure.
3) Large, almost enterprise-scale, projects used by thousands or millions of downstream users, maintained by dozens or hundreds of developers, requiring fairly complex organizational structure.
The article says that "instant you get that first contribution to your code, it becomes an open source project with an open source community of two", and the purpose of the project changes to "collaborating on the maintenance of the project".
For me, absolutely not. For most of my personal projects that I have open-sourced, I have no desire to migrate from a Type 1 (small, personal) project to a Type 2 (medium-sized, multiple-maintainers) project.
I accept PRs on a case-by-case basis, but I usually reject a vast majority of them: they are often buggy and incorrect, or they don't match the purpose and design of the project, or they are correct but severely incomplete (e.g. missing edge-cases, missing tests, missing documentation, etc). I have discovered that it usually takes me more time and effort to code-review the drive-by contributions into an acceptable state, than to just implement the feature myself.
On the other hand, for Type 3 (large, enterprise-scale) critical projects which affect numerous other parties, there is probably a higher level of implicit and social expectations that the project will handle bug reports and feature contributions from 3rd party contributors in a reasonable manner. The development process of a large project probably shouldn't rely on the whims and emotional state of a single maintainer on the project.
With regards to "kindness", which the article mentions a few times, I think for small projects, it might be reasonable to expect the kindness of the community. But for large projects, it is unrealistic that "kindness" will scale to thousands or millions of users. Too many people are too narcissistic, thoughtless, cruel, or all of the above.
In summary, it seems to me that the expectations and the dynamics of an open-source project varies quite a bit, possibly depending on the size and character of the project.
"A federal grand jury indicted him on charges of stealing secrets about the U.S. nuclear arsenal for the People's Republic of China (PRC) in December 1999.[1] After federal investigators were unable to prove these initial accusations, the government conducted a separate investigation. Ultimately it charged Lee only with improper handling of restricted data, one of the original 59 indictment counts, a felony count. He pleaded guilty as part of a plea settlement.
He filed a civil suit that was settled. In June 2006, Lee received $1.6 million from the federal government and five media organizations as part of a settlement leaking his name to the press before any charges had been filed against him.[2]
Federal judge James A. Parker eventually apologized to Lee for denying him bail and putting him in solitary confinement. He excoriated the government for misconduct and misrepresentations to the court.[3] "
The problem with Golang is that it has the same name as a common verb instead of a noun ("go" is used as a verb like 99.99% of the time).
I remember coming across a thread maybe 10-14 years ago where the Golang creators were asked to change the name of the language. They declined. If I recall, one of the arguments was that the name would naturally become associated with Golang. Here we are in 2024, and the confusion still happens.
The TFA blog was great, by the way, even though it was not about about Golang as I had expected.
Other than that, the blog post was very interesting, I learned a bit of history of QNX, and concluded that I should avoid it.
* Undefined behavior, there are apparently over 100 of them. I can probably name about 5, maybe 10. Will the compiler warn me if I accidentally trigger undefined behavior? Of course not, it assumes that I am super-human who never makes a mistake.
* Code sharing using '#include', god I hate 'em.
* No namespaces, which means a single global namespace for all functions.
* Strings: every time I have to manipulate strings in C, I want to shoot myself.
* Arrays decaying into pointers, very clever, causing so much misery.
* Array length decoupled from the array pointer. No way to pass around both of them together, and checked automatically by the compiler.
* The C preprocessor #define magic. Love 'em when they are mine, hate 'em when they are someone else's. Hate 'em even more when they are mine 6 months later.
* The #define/#ifdef spaghetti code. There ought to be better ways to support multiple architectures.
Those are just off the top of my head. I'm sure I could come up with a few more items.
Addendum: Every time I tried to understand Python packaging, I would come across the term "wheel" and my eyes would glaze over because I couldn't figure out what it was from context ("what the heck is a wheel?"). Maybe now I'll go back and finally understand Python packaging.