All the reasons posted for not running interpreted are valid and well taken.
On the other hand I see only 2 reasons that would compel one to run compiled…
security and speed
If you are concerned about someone stealing your code or perhaps messing with
it, then security would be the driving force.
For the first 10 or so years of my close to 30 years with 4D I religiously
deployed compiled. For me speed was the compelling factor. With each new
version of 4D, however, 4D got faster and faster until one day I saw very
little difference between the two. So given how much easier it was to support a
deployed database if it was interpreted, I decided to try deploying interpreted
for a while. I never looked back.
Being able to fix a bug or add a minor feature without little or no down time
makes me a hero with my clients.
Yes I know it’s sacrilege to even contemplate changing or adding to a deployed
server while it is running, but I do it all the time for isolated features or a
simple bug fix. Sometimes it is worth putting a bandaid on a problem until you
have a more permanent fix and can take the server down without affecting the
client’s work flow. I rarely change existing code but instead copy the
offending process or method to a button or menu item, put the fixed code there
and tell the user to use the new button or menu item.
I always compile my databases before deploying. I won’t deploy a database that
will not compile, but I no longer deploy them compiled.
John
> On Aug 1, 2018, at 4:34 AM, Noah via 4D_Tech <[email protected]> wrote:
>
> Is is really 'that bad' to run in interpreted mode?
John Baughman
1331 Auwaiku Street
Kailua, Hawaii 96734
(808) 262-0328
[email protected]
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
