Skip to content
FR EN

Handbook of Sustainable Design of Digital Services

MENU
← go back
Frontend    ODD#12     ODD#13    

Is a compiled language used for performance and / or security aspects ?

Advice 

development standards

B People

A Planet

A Prosperity

Difficulty

N/A

Priority

/

Récurrence

/

Tests

Is the code subject to optimization before compilation, or failing that before interpretation?

Precisions

The type of language used introduces either a proximity to processors (CPU), this is the case of compiled languages, or to humans, this is the case of interpreted languages ​​(PHP, JavaScript, ...). The proximity of machine orders increases technical performance but makes software production heavier (compilation phases, link editing). The "human" proximity facilitates development but also embezzlement (pirating) and requires systems to make an additional effort to translate program lines "on demand" into machine code, with the help of an interpreter.

Additional elements

Rule for assessing the level of compliance of the criterion

0 / 0

Life cycle

Réalisation

5 other criteria related to the recommendation: Implement and develop functionalities to limit impacts

Recommendation Essential

development standards

Don't the functionalities of the service go beyond user needs ?

Advice

development standards

Are the logs free of unprocessed errors ?

Advice

development standards

Are dead codes cleared ?

Recommendation

user Experience

Are the reference elements known, kept up to date, and made available to the entire project team ?

Recommendation

user Experience

Is the inventory of the input data made available for reuse in other projects ?