I am resurrecting this thread because after part of the "smoke and
mirrors propaganda" disappeared, it has become funny again.
A few posts above, alfie said:
Quote:
It seems like a university thesis about the power of suggestion and fanboysm. Teens College Rock and Roll Band.
One classic technique is to hide unpleasant facts. For instance, the
fact that with 256MB of RAM just the simpler sites were displayable,
and that when you runned out of mem (often, judging by the mem
requirements) it still tried to allocate some more memory and crashed,
became public only after a second release. That needs just 192MB as a
practical minimum and with 256MB can show moderately complex sites...
Other examples of such a phenomena can be found in this very thread.
For instance somebody questions if the MOS SDL implementation is
somewhat slower than other implementations. The answer is that
probably there's less fanboyism on MOS, and higher standards. Want
some numbers? Open Tyrian (SDL game) requires some 60% of CPU on A1,
and 20-25% on Peg. To those saying that OWB is fast even on classic:
try it, compare it with Sputnik...
Raffaele asks for technical discussions. I think he got plenty of tech
remarks, if he just read better Fab's, alfie's or my own posts. It's
not just about SDL or the inability of opening multiple tabs.
SDL is definitely a limit because it's an "alien" and selfcontained
framework, and a browser is a kind of app that has to be integrated in
the system. SDL means that important features like cut'n'paste are
difficult to implement, and impossible without hacks, not just that
you get an inconsistent GUI.
Anyway OWB isn't tied to SDL. But if you are going to use OWB just as
a rendering engine, you'll find yourself in the same conditions of
those working on Sputnik or Traveller. You have to write a whole
browser, and a Reaction or MUI GUI. Which is completely another
affair, and is not going to take 2 weeks (not 6 months as wrongly
reported by Raffaele... I'm pretty sure it would take Fab not much
more than a weekend for instance). However, if you take that route,
the fact that the OWB engine renders on bitmaps makes more complicate
to add the features mentioned above (cut, for instance). At that point
it would be wiser to start from WebKit itself, which is why those
working on an actual browser have taken that road.
Finally, I 101% agree with Fab about the "free" remark. Recompiling an
SDL app is absolutely different from writing a complex app like a
browser. But anyway, if you're going to take a cheap shot and use half
of your readme not for your program, but to lightly insult those
working for a bounty, then don't put the PayPal button. That's pretty
lame in my book, of course if he can still take a look in the mirror
at the evening and go to bed happy, that's not my problem.
But it has to be clear that recompiling stuff, and spending hundreds
of hours coding, sometimes leaving behind your studies, maybe
sometimes spending less time with friends or the likes, is different.
If marcik has a girlfriend I'm pretty sure he'd spend part of the
bounty for a present to her (a vacation, something like that), in
order to excuse himself for the evenings he might have spent on the
computer and not with her. This is just a (lame) example, I really
don't know nor care about personal situations, but I find these cheap
shots barely acceptable...
Ok, enough for now...
Kind regards,
Andrea
