I see. But excuse my ignorance - could you please explain to me what "Framebuffer-SDL" means in this regard?
Yes, it's the frontend. NetSurf is split into the "core" - which is the bit which does all the layouting, fetching, etc - and the frontends - which are the OS-specific bits, so the GUI, rendering, input handling etc.
Framebuffer is a non-GUI interface, it basically just writes the browser direct to the screen. All the fonts and graphical elements are built internally and the OS has little involvement. Framebuffer has some other outputs built on top of it, so there's Linux Framebuffer (I assume this will run from a command-line without X, never tried it) and SDL (which uses the SDL libraries to create the display and handle input).
As you can see, the Framebuffer frontend isn't really designed for running on a multitasking windowed operating system.
Arrgh - to top it all both versions (Arthur's and yours) have the same version number! The SDL version I tried to run is also 3.6 dev...
Yes, it's NetSurf internal numbering
Anything between releases gets the next version+"Dev".
Release versions don't have the "Dev".
My versions also have a standard version string, so you can run "version" on them and see the build date (the version number there wil be 3.60006 I think)
Most people run the CI builds, which have the next version number plus their own numbering...
What does "CI build 3602" mean?
It's literally a sequential build number. The auto-builder builds NetSurf after every commit, build number 3602 occured at around the time I manually built the current "3.6dev".
The version command there will show 3.3602 (which is why release versions are +.60000)