Comment by mionhe 3 months ago More accurately, why WebKit was forked from khtml by Apple. 3 comments mionhe Reply dontlaugh 3 months ago Sure. KHTML wasn’t embeddable outside KDE either until Apple made that happen. ASalazarMX 3 months ago That was always KHTML's goal, but Apple saw value in it for their business plan, just like it saw value in FreeBSD to reuse as their OS's base. dontlaugh 3 months ago Sure. I wasn’t trying to say that Apple made WebKit from scratch, merely that they developed it into something easily embeddable. That very much was novel at the time.
dontlaugh 3 months ago Sure. KHTML wasn’t embeddable outside KDE either until Apple made that happen. ASalazarMX 3 months ago That was always KHTML's goal, but Apple saw value in it for their business plan, just like it saw value in FreeBSD to reuse as their OS's base. dontlaugh 3 months ago Sure. I wasn’t trying to say that Apple made WebKit from scratch, merely that they developed it into something easily embeddable. That very much was novel at the time.
ASalazarMX 3 months ago That was always KHTML's goal, but Apple saw value in it for their business plan, just like it saw value in FreeBSD to reuse as their OS's base. dontlaugh 3 months ago Sure. I wasn’t trying to say that Apple made WebKit from scratch, merely that they developed it into something easily embeddable. That very much was novel at the time.
dontlaugh 3 months ago Sure. I wasn’t trying to say that Apple made WebKit from scratch, merely that they developed it into something easily embeddable. That very much was novel at the time.
Sure. KHTML wasn’t embeddable outside KDE either until Apple made that happen.
That was always KHTML's goal, but Apple saw value in it for their business plan, just like it saw value in FreeBSD to reuse as their OS's base.
Sure. I wasn’t trying to say that Apple made WebKit from scratch, merely that they developed it into something easily embeddable. That very much was novel at the time.