I shouldn't of made this. Another direnv alternative for no reason | Hacker News Reader

I shouldn't of made this. Another direnv alternative for no reason

willwa.de

10 pointswillwade12 comments

Open articleView on HN

I will jump on the obvious error too but will provide some more context:

You are typing what you hear in: "shouldn't've" which is a double contraction of "should not have"

"I should not of made this" vs "I should not have made this"

Shouldn't have*

That's one of my least favourite errors

Looks like the author noticed and changed the title to "Direnv - and reinventing the wheel with envloader". Going by the TLD I initially thought that he's from Germany, but no, "de" are just the last two letters of his surname...

I think that these types of errors are made mainly by native English speakers, as they learn and practice their language mostly 'by ear', without having to think much about the logic behind it. And this is as much a logical error as grammatical one.

As a (barely) recovery grammar festidian I highly recommend checking out this video by Dr Geoff Lindsey [1]

TLDW: some fascinating realignment of perspective from a linguist about such things [^2], and the - frankly moderately mind-blowing - revelation that despite caring about language I've been gleefully pronouncing "covert" 'wrong' my whole life (and will likely continue to do so)

[1]: https://youtu.be/I6duEGj04Mg

[^2]: edit for clarity: such things being the concept of "normal forms" or rules in language.

As an aside: despite caring about "correct" use of language I've always been willing to frivolously split infinitives - it's against the rules, but I think quite an effective evolution of language

Good to have linguists around reminding us to boldly go explore :)

So true.

Maybe of interest to someone out there. I'm waiting to get flamed as its totally useless for many many people (I could of solved it with a simple powershell script but in the process I learnt go.. ) - but it solved my problem on my ridiculous Windows machine. Maybe someone else out there..

could have*

Glad you made this - whether it needs to exist or not seems far from relevant as reworking and rethinking things is why we have most of the coolest tools we take for granted :)

Did you discover anything interesting in the process of building it?

I base64 decoded CONFIG_ENCRYPTION_KEY and it looks random vs some mock data. Wonder if it's the real key accidentally posted.

What’s the value prop here vs set -a/+a? That it’s more tolerant of weird variable values?

Reply on news.ycombinator.com