Most of your post was repetitive, and way too long.  lol

On Thu, 15 Oct 2015 18:47:08 +0900 Carsten Haitzler (The Rasterman)
<[email protected]> wrote:

> hahahah. :) but seriously i know your complaint. the problem is that
> i don't buy it given copious reasons.

I don't buy your arguments either.  Especially not your copious
arguments that "but you already have plenty of law violating code".
Considering how much I did manage to disable, there's a lot less than
you ranted on and on about.  There is a threshold for how much excess
code in publicly available libraries can be used.  Minimising that is
still kosher, and it then becomes a "best commercial effort" thing.
"Best effort" in this case means using the tools that the library
provides (not bothering to compile all of it, using lots and lots of
--disable-* configure options, etc).  "Best effort" in this thread means
trying to convince you not to make my best efforts much less effective
AND not making my effort way harder, in your plans.

Mind you, I have other reasons for this, I mentioned some of them
already.  Which you ignored, as predicted.

I guess we can agree to disagree, and I'll stick with 1.7 for these
embedded projects.  Like those other people Cedric mentioned that
stuck with 1.7, for pretty much the same reason.

> > Don't even get me started on efreet.  Crap code written to replace
> > crap code I had half written, coz someone thought mine was too crap
> > (based purely on style??!?!??!!), and they wouldn't give me a
> > chance to finish it.  Mine was destined to be less crap, but the
> > FDO protocol itself is crap, my initial code reflected that.  There
> > are still bugs in efreet being solved today that my original didn't
> > have.  I had a half hearted plan to rewrite efreet, but I got busy
> > writing applications.  After that, all the work I did to get
> > Enlightenment start up time down to much less than a second has
> > been wasted as well, now it takes so long that we need to provide a
> > splash screen.  Not happy Jan!  
> 
> i added a splash screen form like almost the first days of e17. so i
> don't buy that. it had nothing to do with efreet. but indeed dealing
> with fdo standards is a pain.

What, you don't remember how excited you got when I managed to reduce E
startup time to a fraction of a second?  It was your idea, and you
helped.  Not long enough to be able to actually see a splash screen.
Remember my test P100 used for the benchmarking?

And correct, startup time had nothing to do with efreet, it's just
that's when the slow down started to happen after my speed ups.  Hence
why I said "After that" when introducing the startup time bit.  Probably
should have been two paragraphs.  My efreet rant is separate from my
startup time rant.  Both things however contributed to my reasons for
not doing much EFL library work these days.  There are other reasons.
Why work so hard, if my results are almost immediately broken /
replaced by others?  Efreet replaced my efforts without even waiting
for me to finish them, a complete waste of my time.  I don't mind stuff
I wrote being replaced later, like the Edje Lua bindings, that's the
EFL way after all.  Just give it fucking time to show if it should be
replaced, don't replace something that's not finished simply coz you
don't like the style.  Like Vincent though, I might come back and do
more EFL work later.  Hell, I actually made an EFL commit this year!
My priority for spare coding time these days is my EFL based virtual
worlds project though, so don't expect any big EFL coding efforts from
me for a while.  Cedric may yet convince me to do some Evas_3D work
though, he's trying.

</rant>

In my opinion, splash screens on anything are just to distract users,
coz the startup time is too long.

-- 
A big old stinking pile of genius that no one wants
coz there are too many silver coated monkeys in the world.

Attachment: signature.asc
Description: PGP signature

------------------------------------------------------------------------------
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to