Sujet : Code-change-to-run times (was Re: Suggested method for returning a string from a C program?)
De : janis_papanagnou+ng (at) *nospam* hotmail.com (Janis Papanagnou)
Groupes : comp.lang.cDate : 24. Mar 2025, 18:44:28
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vrs5lu$1dj10$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
User-Agent : Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
On 24.03.2025 18:15, Kaz Kylheku wrote:
On 2025-03-24, bart <bc@freeuk.com> wrote:
>
When you have near-instant build times then it's completely different
way of working.
Obviously.
[...]
[ Dart / Flutter ]
Turns out what that refers to is that they want update times measured in
**milliseconds*; that is, from the time a developer makes a change, to
that change being compiled, loaded in the live application and running.
If that "subcultures in contemporary development" is (or becomes)
wide-spread or even standard... <shudder> - Software quality is
often already bad enough, no reason to foster that evolution.
Janis