3 ms·
I mean by that logic we should still be using FORTRAN for our research code and there’s no point developing new languages because the space is explored at this
by tnecniv 3y ago
I mean by that logic we should still be using FORTRAN for our research code and there’s no point developing new languages because the space is explored at this point.
Really I think the main thing holding it back are the lack of templates supported by journals and conferences and some known rendering bugs / limitations that are being worked on.
- pama 3y agoI think the main blocking point is that TeX algorithms are near optimal for a lot of the technical typesetting and everything else looks somewhat off to the astute readers, and those readers are repeat consumers of the technical texts.
- a2800276 3y agoIt's not as though the TeX algorithms are secret and can't possibly be recreated elsewhere.
- pama 3y agoAbsolutely. There simply hasn’t been a better/faster implementation outside the existing TeX ecosystem so far. Returning to the comment that I replied to: everybody could rewrite/extend Fortran; it will still be Fortran.
- slow_typist 3y agoJust for the record, FORTRAN is #12 on tiobe [1], leaving go and swift behind. [1] https://www.tiobe.com/tiobe-index/ https://www.tiobe.com/tiobe-index/
- kaba0 3y agoTIOBE is still behind useless. It once listed Visual Basic ahead of JS. It has as much relevance to sorting programming languages as alphabetical ordering.