2 ms·
Calling it a 'phase' doesn't seem that weird to me? For each file, they go through a number of steps to translate it, and one of those steps is to run the J2K t
by LegionMammal978 2y ago
Calling it a 'phase' doesn't seem that weird to me? For each file, they go through a number of steps to translate it, and one of those steps is to run the J2K tool on it. The next section is just describing how they implemented that step: the J2K tool is normally enmeshed into the rest of the IDE, but they managed to jerry-rig a solution to run the relevant code by itself, without running the rest of the IDE with it every time.
- zahlman 2y agoIt could possibly make sense if the phases were described as e.g. "performing a deep build, preprocessing, running J2K, postprocessing, linting and applying error-based fixes" (i.e., all participles). But then the descriptions should be about how those phases are implemented (i.e., this is the place to mention the work of setting up a headless version of J2K so that it could be run in an automated pipeline) and how they contribute to getting the desired result. The description "The J2K we know and love, but server-friendly!" is utterly useless here, and also practically the archetype of what ChatGPT writes in "promotional material" mode.