Types of Solar Eclipse
⌘ Read more

@lyse@lyse.isobeef.org @movq@www.uninformativ.de I’ve always liked the sound of crows, and I really really hate the sound of motorized vehicles, so I also find it absurd. I’ve come to think that some people are at some level afraid of nature, and nature sounds remind them of it.

@prologic@twtxt.net

Taking Jordan Peterson asn an example, the only thing he “preaches” (if you want to call it that) is to be honest with yourself and to take responsibility.

This is simply untrue. Read the articles I posted, seriously.

In a tweet in one of the articles I posted, Peterson states there is no white supremacy in Canada. This is blatantly false. It is disinformation. Peterson has made statements that rape is OK (he uses “fancy” language like “women should be naturally converted into mothers” but unpack that a bit–what he means is legalized rape followed by forced conception). He is openly anti-LGBTQ and refuses to use peoples’ preferred pronouns. He seems to believe that women who wear makeup at work are asking to be sexually harassed.

He’s using his platform in academia to pretend that straight, white men are somehow the most aggrieved group in the world and everyone else is just whining and can get fucked. The patron saint of Men’s Rights Activists and incels. I find him odious.

being immersed in gorgeous #nature makes me want to write elegant programs, I’m amazed by the underlying systems #coding #phylosophy

Estuve revisando una entrada del blog (Sembrando Juegos) y un caso de rol para un conocido (100 páginas), y aunque encontré decenas de errores de ortografía y gramática, muchos pasaban desapercibidos, aún con muchas leídas.

Es impresionante cómo las herramientas automatizadas facilitan la revisión de ortografía y gramática. Como se ha mencionado, es la creatividad asistida por tecnología que se está haciendo más “natural”, o simplemente la normalizamos con el tiempo.

@prologic@twtxt.net Error handling especially in Go is very tricky I think. Even though the idea is simple, it’s fairly hard to actually implement and use in a meaningful way in my opinion. All this error wrapping or the lack of it and checking whether some specific error occurred is a mess. errors.As(…) just doesn’t feel natural. errors.Is(…) only just. I mainly avoided it. Yesterday evening I actually researched a bit about that and found this article on errors with Go 1.13. It shed a little bit of light, but I still have a long way to go, I reckon.

We tried several things but haven’t found the holy grail. Currently, we have a mix of different styles, but nothing feels really right. And having plenty of different approaches also doesn’t help, that’s right. I agree, error messages often end up getting wrapped way too much with useless information. We haven’t found a solution yet. We just noticed that it kind of depends on the exact circumstances, sometimes the caller should add more information, sometimes it’s better if the callee already includes what it was supposed to do.

To experiment and get a feel for yesterday’s research results I tried myself on the combined log parser and how to signal three different errors. I’m not happy with it. Any feedback is highly appreciated. The idea is to let the caller check (not implemented yet) whether a specific error occurred. That means I have to define some dedicated errors upfront (ErrInvalidFormat, ErrInvalidStatusCode, ErrInvalidSentBytes) that can be used in the err == ErrInvalidFormat or probably more correct errors.Is(err, ErrInvalidFormat) check at the caller.

All three errors define separate error categories and are created using errors.New(…). But for the invalid status code and invalid sent bytes cases I want to include more detail, the actual invalid number that is. Since these errors are already predefined, I cannot add this dynamic information to them. So I would need to wrap them à la fmt.Errorf("invalid sent bytes '%s': %w", sentBytes, ErrInvalidSentBytes"). Yet, the ErrInvalidSentBytes is wrapped and can be asserted later on using errors.Is(err, ErrInvalidSentBytes), but the big problem is that the message is repeated. I don’t want that!

Having a Python and Java background, exception hierarchies are a well understood concept I’m trying to use here. While typing this long message it occurs to me that this is probably the issue here. Anyways, I thought, I just create a ParseError type, that can hold a custom message and some causing error (one of the three ErrInvalid* above). The custom message is then returned at Error() and the wrapped cause will be matched in Is(…). I then just return a ParseError{fmt.Sprintf("invalid sent bytes '%s'", sentBytes), ErrInvalidSentBytes}, but that looks super weird.

I probably need to scrap the “parent error” ParseError and make all three “suberrors” three dedicated error types implementing Error() string methods where I create a useful error messages. Then the caller probably could just errors.Is(err, InvalidSentBytesError{}). But creating an instance of the InvalidSentBytesError type only to check for such an error category just does feel wrong to me. However, it might be the way to do this. I don’t know. To be tried. Opinions, anyone? Implementing a whole new type is some effort, that I want to avoid.

Alternatively just one ParseError containing an error kind enumeration for InvalidFormat and friends could be used. Also seen that pattern before. But that would then require the much more verbose var parseError ParseError; if errors.As(err, &parseError) && parseError.Kind == InvalidSentBytes { … } or something like that. Far from elegant in my eyes.

Motion Blur
⌘ Read more

@movq@www.uninformativ.de
Yes, I did ask whether or not it was possible to move twts to an “archive” folder, but it will be the same at @stackeffect@twtxt.stackeffect.de experienced (which I have, too), that is, twts will “come back”.

There is no clear solution, I am afraid, right? It is the nature of the beast.

“The target of the Jihad was a machine-attitude as much as the machines,” Leto said. “Humans had set those machines to usurp our sense of beauty, our necessary selfdom out of which we make living judgments. Naturally, the machines were destroyed.”

Imagine a computer harnessing the natural behavior of natural systems and utilizing their behaviors to solve equations. via @devine@wiki.xxiivv.com https://wiki.xxiivv.com/site/computation.html

If [you take] a look at how APLers communicate when they have ideas, you see code all the time, all day long. The APL community is the only one I’ve seen that regularly can write complete code and talk about it fluently on a whiteboard between humans without hand waving. Even my beloved Scheme programming language cannot boast this. When working with humans on a programming task, almost no one uses their programming languages that primary communication method between themselves and other humans outside of the presence of a computer. That signals to me that they are not, in fact, natural, expedient tools for communicating ideas to other humans. The best practices utilized in most programming languages are, instead, attempts to ameliorate the situation to make the code as tractable and as manageable as possible, but they do not, primarily, represent a demonstration of the naturalness of those languages to human communication. — aaron hsu

Natural magical patterns of percussion Is the discussion, so listen up close

creating an off-grid culture that can live in harmony with nature, as a bit