898 karma · joined May 26, 2016
I am not sure what is meant by "board popular", did you mean to say "broadly popular". At any rate, you have not answered my question. You have simply rephrased what the poster that I responded to above already said.
What is this supposed to mean? Why are you suggesting that the average "software developer" would view the subject's expressed point of view as "woke" as opposed to a person from any other occupation? Why the hostility towards software developers?
I guess my big problem with the concluding statement is that it places the responsibility of resolving the impasse on the demographic that is apparently incapable of imagining the world from the others perspective. That seems futile in the absence of empathy. Whose responsibility is it then, to establish a sense of empathy amongst the majority of the orthodox privileged group (empathy would be needed in the other group as well of course)?
Consider also that an obligation to be polite and silence ones voice from engaging in meaningful discourse, may very well be what ultimately leads to an orthodox privileged group in the first place, making the proposed solution a paradox.
> Similarly, if someone says they can think of things that are true but that cannot be said, it's only polite to take them at their word, even if you can't think of any yourself.
That statement suggests to me that the responsibility of being polite should fall on those in the orthodox privileged demographic when challenged by those claiming that there are truths that cannot be safely spoken. It seems flipped around from the rolls expressed in the body of the essay, and that has me confused. How would they know to be polite? How is this actually a solution?
Email is just used to receive the patch, you should use a tool meant for the job to actually do the merge. I realize that is probably not what you meant though. Besides, when email patching first began, the tooling was in its infancy.
However; today tools like the git cli itself, or magit + smerge-mode (my personal preference) are as good as GitHub, if not better. I never actually use GitHub for merging, even when working on projects hosted in GitHub.
I feel that Canada has a similar problem.
> Using the tooling in this repo, I am able to boot from linux to sinit as PID1, and from there to Emacs acting as PID2 using --script mode, performing all typical rc.boot system initialization using Emacs lisp until we hit the getty.
I have run into issues with the odd package, but nothing that has ruined my day.
Funny, the years spent onboarding Emacs, and GNU/Linux for that matter, was the experience I was looking for.I never wanted to be just another cog in a well lubed task grinding machine.
>they shouldn't have to entirely relearn how to write code
If you are referring to elisp, it really isn't a mountain to climb or anything like that. Besides, only very basic lisp knowledge is required to customize Emacs, after that you can code your day away in a lisp of your choosing.
If you are looking for a more modern experience with emacs try elgot + tree-sitter [1]
That is really interesting. The potential side effects from toxicity listed on wikipedia [1] are ominous. I wish there was consumer technology to effectively monitor ones own blood work.