[Info-vax] Programming languages, was: Re: DECUServe is a Hobbyist Chapter
Simon Clubley
clubley at remove_me.eisner.decus.org-Earth.UFP
Tue Jul 7 08:25:59 EDT 2020
On 2020-07-06, Arne Vajhøj <arne at vajhoej.dk> wrote:
> On 7/6/2020 1:46 PM, Simon Clubley wrote:
>>
>> Python's high level constructs make it really good for scripting
>> type operations and is far superior to anything that DCL has to
>> offer in terms of control structures and data types.
>>
>> For traditional application programs, I prefer a more traditional
>> programming language which has all the compiler-time checks and type
>> checking built in.
>>
>> You wouldn't use C++ or another similar language to write a shell
>> script and you wouldn't use Python to write a full blown accounting
>> package (for example).
>
> There are accounting packages in Python.
>
>:-)
>
So I now see. That's an, erm, "interesting" choice of implementation
language.
> And if I were to create an accounting package from scratch, then
> I would seriously consider a model with some foundation in a
> static typed compiled language, but all the code that may
> require changes due to management decisions and changes in
> regulations in a dynamic language (like Python).
>
Have you worked on an accounting system ?
There might be an argument for supporting the easy customising of
front-end reporting tools, but implementing the backend in the way
you describe is unlikely to provide real benefits.
It is really hard to predict what might need changing as the result
of future management decisions and future regulations.
The best way to design the back end architecture is to make it as table
driven as possible with as little business logic embedded in the
actual code as possible. That can be done independently of backend
programming language.
Simon.
--
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.
More information about the Info-vax
mailing list