, 6 tweets, 1 min read Read on Twitter
Maybe I'm a minority opinion the way things are going, but I absolutely hate environmental variables for configuration. They're brittle, they're ambient, they can be changed and FUBAR any known state underneath you, they're an attack vector, just...ugh. I do not care for them.
The most common answer I get on "why?" is "that's the cross-platform way, everyone supports it".

Okay, yeah sure...I agree that we're at the least common denominator. My issue is settling for that. I don't think most things should. We can do far better. Options already exist.
I love the way .NET Core does this - IOptions is very pluggable and one of my favorite API designs because it fits so many scenarios, including complex deployment and multi-tenant things we have here.

It's defaulting straight to "make it an environmental variable" that gets me.
I've seen so bugs where a thing works forever but stops because some sysadmin somewhere deployed a GPO that sets an environmental variable deployed to many machines that silently changed behavior of apps that haven't been deployed in years, just happens on restart and...ugh.
That's just one example, there are many.

"It works on my machine" is a problem. Environmental variables magnify that problem immensely. They're a maybe permanent, maybe ephemeral, maybe local, maybe global external state that adds more to control, break, reason about, and debug.
"Why does this app work, but this one doesn't?"

"After 2 days of debugging we found out this one runs as account X with variables Y and it has the SDK path correctly set, the other one didn't have that variable"

"...I quit."
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Nick Craver
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!