Repeat after me:

process.env is not standardized. Keep it out of the browser.
process.env is not standardized. Keep it out of the browser.
process.env is not standardized. Keep it out of the browser.
process.env is not standardized. Keep it out of the browser.

Fucking hate the web community. It's just a large trash barge at this point.

I'll show my ignorance here and say that ... didn't even know that could be 'in the browser'...

@N00bPancakes There are people that favor "convention" (if you can call it that) over standards. Those people make me angry.

@junon

Can't say I understand it well but I get it in node land ... not sure I want some parameters like that changing or held in a processenv while I'm trying to debug client code in the browser though....

@N00bPancakes Precisely. Also, `process` doesn't exist in the browser so you have to have a build step just to get the code to work.

@junon To be fair though, if you have a build step and process.env is automatically replaced at build time then it's not a convention, it's an intended feature. Kinda like ldflags in go

@ScriptCoded They are not stripping them at build time, hence the issue.

@junon Then the only problem I'd see is it being global

@ScriptCoded I see web dev and see an entire field of issues growing upon their forgotten and buried parent issues, who in turn grew upon their forgotten and buried parent issues, and so on back to the dawn of the web. And, honestly, before.

JS tooling and NPM are respectively the advent of farming equipment and automated farming that both (and especially together) greatly accelerated this ever-growing atrocity.

@Root I don't disagree with you. The JS ecosystem is utter shit. But that doesn't mean that defining a variable is idiocy.

Do you know webpack

@nitwhiz Of course. Webpack created this fucking mess.

@junon and what did browserify do on this path?

@nitwhiz Exist. That was a huge fuckup, too.

@junon i guess the problem is accessibility. Making stuff for browsers is easy and you can show it to everyone easily.

Same with unity. It made making games for multiple platforms easy and videogames become more trashy with every fucking day.

@nitwhiz I agree. The easier you make something, the shittier the overall ecosystem becomes because less and less skilled people (see: fucking idiots) use the technology the wrong way and we ALL suffer for it.

I completely agree.

@molaram what

@molaram Apparently we can’t say anything anymore. 🤷🏻‍♀️

Everything is trash. Fight me.

@molaram Sounds like my weekend