> Maybe for some internal usages. but imagine someone from a country using different language and characters gives me a card with their email. It's now far less portable for me to use it. Those days, I surely could picture it and find the email most likely getting it right.
It would be more portable for use with their peers who speak the same language, rather than requiring that everyone they want to communicate with in their own language and alphabet understands a second alphabet just for the addressing scheme.
> Well - the point of involving the AI is that very often it explains my intuitions way better than I can. It instantiates them and fills in all the details
> I like to think that I can recognise good arguments, but if I am wrong here - then why would you prefer my writing from an LLM generated one?
Because the AI will happily argue either side of a debate, in both cases the meaningful/useful/reliable information in the post is constrained by the limits of _your_ knowledge. The LLM-based one will merely be longer.
Can you think of a time when you asked AI to support your point, and upon reviewing its argument, decided it was unconvincing after all and changed your mind?
If 10 people on the internet tell you they want to kill you, how do you tell if 1 of them is serious and is actually going to show up physically?
The answer is that you can't, and there isn't a firm line where all trolling is on one side and harassing/violent behaviour is something different.
Many of us can heuristically decide that trollish behaviour aimed at us won't extend to our person/home/workplace, and doesn't need to be taken seriously. That doesn't mean it's a rule for everyone or an excuse for that behaviour.
I have some frustrations with browsh's docs too, but the readme in the github repo does link to a build guide[1], and the build steps are also reproduced in the Dockerfile.
There are "low profile mechanical" switches now that are more chiclet-like, but I'm not sure if they've been put into an ergo design yet: https://www.youtube.com/watch?v=4lAokeiYbzo
I personally like Matias Quiet Click switches for a good feeling, quiet switch. But the keys and keyboards from Matias have a deserved reputation for being finicky.
I have a Matias Ergo Pro - which I otherwise like - but once in a while keys on the left half will chatter until the board is unplugged. https://matias.ca/ergopro/pc/
I think this expression would be familiar to most native English speakers, but it is idiomatic.
It's using "near" as a synonym to "close" -- as in "a close shave" (actually close) rather than as a synonym for "close to" as it is in the expression "near death" (almost, but not quite dead).
The second sense is definitely more common.
This post suggests "near miss" became common as a military phrase to mean "missed, but still damaged the target" but changed as it entered the vernacular:
While fictional, the Canterbury Tales portrays pilgrimages as a kind of extended carnival, where some of society's normal rules are suspended. You can argue that tourism was born out of catering to pilgrims: http://blog.museumoflondon.org.uk/pilgrim-badges-birth-touri...
Of course there are more serious traditions of pilgrimage, but people are people, and for every one with a deep connection to their faith, there are others who will use the excuse of pilgrimage for a break from the routine.
However, this is really Matias's problem to resolve. Supposedly the switch or the assembly process has been redesigned to prevent this problem in the newest batch, but I don't know if it's a proven success.
We don't need to accept that roads are deadly places for non-drivers. We should strive to make our environment more liveable - by changing road design, vehicle safety features and driver attitudes - and this includes enforcement.
"dotnet publish" should have you covered for restoring from nuget, compiling and producing a deployable package. Is there something it's missing for your use case?
Noda Time might have what you need in a datetime library.
First, tweeting the anti-CoC article was only one of the issues listed, but some of them were on the private issue tracker so I can't speak to those.
The article was definitely what brought it to a head because it prompted some people to say publicly they had bad interactions with Rod Vagg.
There were also a number of thoughtful responses to Rod's tweet where people spelled out why they thought his attitude towards CoCs was unhelpful. As far as I know he didn't engage any of these authors, which makes me suspect he was not actually looking for "interesting discussion".
Overall it was inflammatory in the same way another article complaining about missing generics in golang would be inflammatory here. The article doesn't seem to respect existing work and doesn't bring a new or evidence based perspective.
I agree it would be nice if all the complaints, responses, etc were laid out plainly. But I can also understand why this is not the case, given tweets like https://twitter.com/ag_dubs/status/887785046320480256 and the understanding that there's little benefit for the women involved to gain by re-litigate these interactions in public.
It would be more portable for use with their peers who speak the same language, rather than requiring that everyone they want to communicate with in their own language and alphabet understands a second alphabet just for the addressing scheme.