How many people here are programmers that actually need features added for custom software to be written? I am the maintainer of a fork of ECX, an Amiga E compiler that supports 68020 and PPC. Who among you are willing to help me add features to this Amiga/MorphOS compiler knowing that it will never work outside the Amiga community? Show of hands? Anyone? I thought not.
EEC could have a GCC code generator that would be portable to any supported architecture of GCC 10+ using the LibGCCJIT frontend. It could support multiple cores if the OS supported it. 64-bit tag-lists might get tricky but it might be possible if the data field was 64 bits and the code field was 32 bits. The point is that no volunteers will make it happen.
> So far our record waiting time (since 2.0) has been 615 days > (between MorphOS 2.7 and 3.0). It's been 584 days since 3.18 > as for today, so no new record... yet.
Apart from the massive 1010 days wait for 3.10 (already addressed by connor) and the even longer wait for 2.0 (1157 days), the wait for 3.0 was not 615 days but only 554 days, so the current 584 days wait for 3.19 is already longer by now, making it #3. Here is an ordered list of the waiting times in days just for the fun of it (feature releases in bold):
What's interesting to see (because it's counter-intuitive) is that the wait for the feature releases 2.2, 2.4 and 3.4 was on the shorter side, whereas the wait for the bug-fix releases 2.3 and 2.5 was on the longer side (as is the exceptional wait for bug-fix release 3.19).
Another fun list is that of added waiting times in days of feature release and following bug-fix release: