Which raises the following question: is it better to leave the potential source of problem around as long as it's not triggered, or is it better to temporarily activate it in order to remove it for good?
Sorry for the bluntness of my question: I only have little experience in using Python, which I acquired while trying out Django, and I remember using scripts to generate certain parts of the site (things might have…
You'd probably love COBOL too, it's closer to plain English than most other programming languages out there.
> 50K LOC python/django codebase. How much of it is generated?
> When was the last time you saw a systems language that scaled comfortably and gracefully from embedded systems to web services? Have a look at ATS[1], it supports many features that are available in Rust, and let you…
Which raises the following question: is it better to leave the potential source of problem around as long as it's not triggered, or is it better to temporarily activate it in order to remove it for good?
Sorry for the bluntness of my question: I only have little experience in using Python, which I acquired while trying out Django, and I remember using scripts to generate certain parts of the site (things might have…
You'd probably love COBOL too, it's closer to plain English than most other programming languages out there.
> 50K LOC python/django codebase. How much of it is generated?
> When was the last time you saw a systems language that scaled comfortably and gracefully from embedded systems to web services? Have a look at ATS[1], it supports many features that are available in Rust, and let you…