Forum: Weblog comments

Robert,

Take it easy, relax. We make mistakes and the more important thing is to learn from them. Try to avoid from making the same mistakes again. Thanks for making software that thousands, if not millions, use day to day.

Stay away from those drinks too.

Kairo,

I would say that you've learned a powerful lesson, though I don't know that I agree with your assessment of what it is: it would seem to me you've learned more about organizational politics than mistakes you've made.

For what it's worth, for the "sin" of having spoken your mind frankly, honestly, and sincerely, you've been put in a "penalty box" along with plenty of other people.

I hope the disrespect toward you doesn't discourage you from keeping up the good work.

Robert, will be al ok . I strongly believe. You are the best !
But may be ... it's a sign !? Do you believe in it ? ...

just thought ...a sign to take a look a partly on some other things ...
for example ... a WebKit2 ... why not ...

-no, not to all it of cause , due to xul extensions miss if skip to html WebKit2 engine (Am I right ?)
but New Nitro JS engine (Is it possible to take only Nitro ?).... Nitro ... looks pretty fast as I seeing last 24 hours ...

-new SeaMonkey3 on fastest Nitro JS engine - why not !?

///just my stupid thought ...

The fastest JS engine by the time we can think of a SeaMonkey3 will be JägerMonkey, the then-default Mozilla JS engine. Believe me. Also, taking a step back from the add-on capabilities of the Gecko/XULRunner platform and to the incomplete standards compliance on WebKit is not an option for our project.

By the way , Robert do you know that JägerMonkey will use code from Nitro ?
I'm really not sure that such hamburger will work faster than Nitro3 (I mean Nitro from WebKit3) when will appeared.

My idea was in that now if just change TraceMonkey to Nitro2(WebKit2 Nitro) - mightly we can see a better speed with SM2.
And in a future when come Nitro3(WebKit3 Nitro) very likely that Nitro3 will faster too.

Is it theoretically hard to change JS engine without any writing of other code ?

It's just an example of stupid thought)...
I meant only that it would be interesting to look for some other useful code out there of MC ... and may be it will goes to reenforce SM more than using only one MC code.

And it's great to hear that SM won't leave xul extensions even if FF skip only to JetPack in the future.
(if I correctly did understand)

In any case, this post is not about the future of SeaMonkey. It's about me not being able to participate in the discussion of Mozilla's future.
Despite that, I still believe in Mozilla - and in SeaMonkey. Maybe I'm stubborn, but that's me.

Zuletzt bearbeitet von KaiRo am 10.06.2010 18:41

I believe in Mozilla and in SeaMonkey either. Wish them stay stronger against huge corporations.
And I hope one day SeaMonkey became browser number one in the world.

You don't sound happy. Personally, I'd go bonkers if I had to got to a lot of conferences and such. About people who praise 1.x, maybe you should look into giving the users what they want, if it doesn't interfere with more people want. It seems to me that SeaMonkey is getting the same dictator-style development (we'll do what we want; to hell with what the users want!) that Firefox has had for years.