Is it a shared object like any other Haiku library? Maintaining it separately might be unnecessary if that’s the case.
“Wrong. Next question.”
I am not sure that your answer to SamuraiCrow was in the best traditions of internet intercourse, and nor was it an example of the helpfulness and comradeship that normally characterise this forum.
But we all have bad days, and no doubt that was the cause.
Any chance you could enlarge on your answer and explain why it was the wrong question? SamuraiCrow is not the only one who would benefit.
2 Likes
Yes,there’s libWebKitLegacy.so.1 in the HaikuWebKit package that contains the web rendering,and a separate libJavaScriptCore.so.18 for Javascript.
libWebKitLegacy depends on libJavaScriptCore,but it’s installed on a standard Haiku system anyway and you can turn off Javascript support in runtime to avoid the overhead.
1 Like
Re:libWebKitLegacy.so.1
That may be just the leverage I need.
Exactly. If the current question cannot be provably answered wrong, it’s not time to move on. “Wrong” is just an opinion without proof.
Yes, it was a bit spiffy. In any case, the answer was a bit to-the-point because the quoted “argument” is ridiciious. This is just like the waste of time that the “ICU is bloated” topic was.
No, the JavaScriptCore interpreter is not bloated, too slow, introduce more overhead “than they are worth”. I think it is utterly ridicilous to go and utter such BS after admitting to not even knowing where the software lives, what it does, and how it is written or architectured.
You were sprouting nonsense without Proof. Hence “Wrong” is all that it required.
Anyhow, this topic has clearly run it’s course. We will not be adjusting webkit for this usecase.
3 Likes