![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/a64z2tlDDD.png)
Fork. Setting up a whole new project infrastructure, getting fellow developers on board with your putsch and everything can be a PITA but all those are natural hurdles, due to how the licensing works the BDFL has no way to stop you.
As such, as a BDFL you rule by the grace of authority of the bootmaker. If you don’t make sense, if you aren’t respected, sooner than later the community is going to leave you behind.
There’s plenty of schemes that aren’t fully standards-compliant but I don’t think leaving out eval is common – it’s easy to implement and nothing about the standard says that it needs to run code fast.
Just wanted to point out that eval is the real static vs dynamic boundary. As to evil, sure, you shouldn’t run just any code you find without having a sandbox in place, C’s way to do the same thing is to call
cc
followed bydlopen
, that’s way scarier, which is why people just link in lua or something instead. I guess in <currentyear> you should probably include a wasm runtime instead of usingdlopen
.