Fantastic work. I remember using Dillo in Puppy Linux from Live CDs back in the day.
What's the minimum compiler you target? Any big long term plans? Fuzzing? Moving to 'modern' build system like CMake?
What's the minimum compiler you target? Any big long term plans? Fuzzing? Moving to 'modern' build system like CMake?
> What's the minimum compiler you target?
I didn't defined any (yet), but shouldn't be too hard to add to the CI.
> Any big long term plans?
First preventing it from dying and getting removed from distros. Then it depends of how much free time I can dedicate to it, but at least maintaining it.
> Fuzzing?
I would say first adding some of the other browser tests suites. That should catch a lot of rendering issues. But yeah, fuzzing would be interesting, specially for the custom HTML and CSS parsers.
> Moving to 'modern' build system like CMake?
Yes, I had to modify the configure.ac and that was very painful, specially targeting a lot of platforms. It is also broken for cross compilation. I have to check also how is the support for cmake in other systems, so we can safely remove Automake and friends. But I didn't want to introduce any big changes before 3.1 is released.
Wouldn't a project such as this one be a perfect candidate for Cosmopolitan?
> Cosmopolitan Libc makes C a build-anywhere run-anywhere language, like Java, except it doesn't need an interpreter or virtual machine. Instead, it reconfigures stock GCC and Clang to output a POSIX-approved polyglot format that runs natively on Linux + Mac + Windows + FreeBSD + OpenBSD + NetBSD + BIOS on AMD64 and ARM64 with the best possible performance.