> in my 8 years working in this field my biggest take-away, as of recent days, is that you make so much trouble adding features
You're right.
My big thing is unless you require the user to add another system like dotenv it's not simple to store state unless you write a script that exports variables.
My other point, I remembered was, I don't like env variables for system configuration, tuning maybe. I use them like many other libraries do, for adjusting startup library behavior. For instance, enabling debugging, tracing, specifying the heap binary to map into the process, things that are meant to be transparent to the application developer at startup. If the library is used widley, it needs global state, the best way to ensure that variable is set when the process starts is with an env.
Other than that, strict typing and language enforcement that I don't have to write parsing code is good. Errors in configuration data is easier to validate and give clear feedback is also a big deal.
I was going to get into secrets, but its kind of pedantic, I don't like secrets in environment variables.
ChipTuner
npub1qd…3fqm7
2024-09-23 17:57:58
in reply to nevent1q…mq0g
Author Public Key
npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7Published at
2024-09-23 17:57:58Event JSON
{
"id": "0003b3b34d2c9dacebdfb78babfef1e227037399278dc6b821e807ce27b0bea2",
"pubkey": "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
"created_at": 1727114278,
"kind": 1,
"tags": [
[
"e",
"a0f7ea6f92fb790e6c6dc4d0b0cc3b6be8a13f7c395253cb1dccf6307320b14a",
"",
"root"
],
[
"e",
"ac790b661b2513bf665024a8a26f49a5a61531900d42de341f8a78aafa22b6dd",
"",
"reply"
],
[
"p",
"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"",
"mention"
],
[
"p",
"16f1a0100d4cfffbcc4230e8e0e4290cc5849c1adc64d6653fda07c031b1074b",
"",
"mention"
]
],
"content": "\u003e in my 8 years working in this field my biggest take-away, as of recent days, is that you make so much trouble adding features\nYou're right.\n\nMy big thing is unless you require the user to add another system like dotenv it's not simple to store state unless you write a script that exports variables. \n\nMy other point, I remembered was, I don't like env variables for system configuration, tuning maybe. I use them like many other libraries do, for adjusting startup library behavior. For instance, enabling debugging, tracing, specifying the heap binary to map into the process, things that are meant to be transparent to the application developer at startup. If the library is used widley, it needs global state, the best way to ensure that variable is set when the process starts is with an env. \n\nOther than that, strict typing and language enforcement that I don't have to write parsing code is good. Errors in configuration data is easier to validate and give clear feedback is also a big deal. \n\nI was going to get into secrets, but its kind of pedantic, I don't like secrets in environment variables. ",
"sig": "b8da36b94487e06070de7fd4780d0971e15303f31e5eb820e840a556097f88a85d85f609db8a780f8865cea29ed3a8d6539bdc5c0989944be5f58be917dd1e2b"
}