Mail Archives: djgpp/2011/02/08/12:00:18
"DJ Delorie" <dj AT delorie DOT com> wrote in message
news:xnfwrzpw1i DOT fsf AT delorie DOT com...
> "Rod Pemberton" <do_not_have AT notreplytome DOT cmm> writes:
>
> > If so, it's likely the DJGPP email to Usenet gateway rejected.
>
> It did. No foul language here, please, we have minors using DJGPP.
>
I'd respect that position, if I thought it were true. However, this is
Usenet. It's not for children. It never has been. Think of all the binary
alt.* groups. It wasn't 25 years ago. It still isn't today. I'm not aware
of ever seeing a post from a child.
The volume here is virtually non-existant. I'm surprised
comp.os.msdos.djgpp didn't get itself on the recent Big-8 deletion list. If
Andris Pavenis and Juan Manuel Guerrero hadn't been posting "ANNOUNCE"
messages, I think this group might've failed the Big-8 stage 1 requirements.
This group is not a DJGPP forum, or Listserv that you control DJ. You
could've made this group moderated, if you so wished. You didn't. That's
your failure. You still can, but AISI there is no point anymore. DJGPP's
time has past. Well, there might be one point to moderation: Big-8 doesn't
delete moderated groups. Or, two: you can block any words you don't like,
for any language.
DJGPP is not being used to code DOS, e.g., FreeDOS or DR-DOS. It was being
used to code FreeDOS-32, but that's been stalled for 6 years now. AFAIK,
it's not being used to code new OSes, or any major applications. DJGPP
hasn't progressed in the 6 or 7 years that I've been reading here. The
handful of serious users of DJGPP stopped posting 3 to 4 years ago. I'd
guess that most moved on. For all practical purposes, DJGPP is dead. It's
frozen in time. It tried to move to XP, sort of... It hasn't, yet...
That's still in Beta. 7 years of Beta... No demand? It has yet to find
another OS to give it purpose, or something to give it life, like a DOS
shell for Windows 7. I've repeatedly suggested two things that could
breathe some life into DJGPP: GNU GLIBC, and recompiled v2.03 with 64-bit
support enabled. GLIBC would allow GNU tools on DOS to just work. 64-bit
would allow current users to migrate from 32-bit. They'll have to do so at
some point. I.e., you'll lose them. So, the void is/was being filled by
other compilers: Cygwin, Pelles C, LCC-Win32, LLVM, MinGW, etc. All the
recent x86 OS developers seem to be using Linux w/GNU GCC, or MASM.
Rod Pemberton
- Raw text -