(no title)
adg001 | 3 years ago
Okay with the postmodernism, but relying on a memory unsafe language to implement a server-side web framework in 1970, 1991, 1992, and 2017 is equally anachronistic. That being said much love to Forth! – Or, as the post-modern philosopher Slavoj Žižek is used to say: "and so on and so Forth".
tluyben2|3 years ago
> memory unsafe language
That's the implementation thing, not the language. You can implement an ANSI Forth standard like GForth in a memory safe way without a lot of issues. Even the memory allocation words[0] are easily implemented in a garbage collected language. Of course that makes it useless for embedded purposes which is where Forth usually works well, but that's not an issue as you are not doing that here.
[0] https://forth-standard.org/standard/memory
astrobe_|3 years ago
You can forbid yourself to do these things and implement a "safety layer" for string handling, array handling with bound checking etc. but at the end of the day, it's more a a cultural thing than a technical thing. IMO this era wants to build reliability from lots of unreliable parts, and that include developers; cowboy programmers who could make reliable things by themselves have been retired.
Well, you see the result: smartphones that can't make emergency calls when you need it etc. But hey, it's written in a memory safe language and our bus factor is 0.00004 !
adg001|3 years ago
I am reminded about a quote attributed to Keith Martin (mathematician): "Theory is important, at least in theory"