Comment Re:Uah no (Score 1) 147
About 25 years ago, I was at a bbq where I spent the evening chatting with this guy named Lars Knoll. Even though I was busting my butt with my team to develop the Opera for Linux web browser, this guy had been hired by TrollTech after he had developed something called Konquerer which was becoming the default HTML rendering engine in the KDE project. He wrote the whole thing on top of the KDE libraries which were painfully slow. He rendered text and for controls using the KDE objects which were rarely more than Qt objects with a little KDE specific stuff on top. I remember thinking "there's no point thinking much about this because there's no chance it could compete with a real browser like Opera".
Shortly after, I was in Cupertino sitting across from a strange product manager type. His name was Tim Cooke. We were discussing developing the default web engine for this new Mac OS X project which was coming along. We would have to develop for Carbon because Apple hadn't implemented Objective C++ yet and we were a C++ shop and we couldn't use half the developers in the company to make a C abstraction layer for Cocoa. We came to an agreement and Apple sent us a palette full of the latest G4 macs and screens. I remember fighting over the 21" screens like children. We had an idiot project manager who insisted that we implement the browser the way Adobe was demanding. It didn't matter that we were pretty much the "experts" on making cross platform embedded browser engines. He was like "Adobe said it... it must be done this way... they are gods".
Well long story short, while we were implementing a crap Carbon based browser engine using crap tools from Metrowerks instead of the good Apple tools (which weren't that good yet). Apple put together a team which abstracted the KDE libraries and built bindings to C and then Objective-C/Cocoa. And they abstracted out everything that was platform specific otherwise from KHTML (Konquerer's underlying html widget) and wrapped it in a Cocoa wrapper and a Carbon wrapper and shipped it as Webkit and Safari. And man did it suck.
Who would have ever imagined that Lars Knoll's half assed KDE web browser would have eventually become the defacto Web standard and the default web browsing engine in every operating system... including Windows... except the strange 5 user corner case operating systems.
Don't bash a project like this. It has value. I immediately considered that I have had many cases in recent times where it could have been of value to me. That said, I wouldn't run a C based web browser engine ever. It's not that you can't write a good web browser in C. It's just that it's the wrong tool for the job. At 160,000 lines, it's a small job to port to something else. When JavaScript evolves into a JIT and the JS runtime is thunking the heck out of the DOM, then it's pretty much no longer an option. Oh, and someone will think it's a good idea to implement proper form controls. That's an insanely massive project, especially when adding WebGL as well. If this browser core catches on, which unfortunately due to the license, I don't expect it will, it will likely be 5 million lines of code almost overnight.
Shortly after, I was in Cupertino sitting across from a strange product manager type. His name was Tim Cooke. We were discussing developing the default web engine for this new Mac OS X project which was coming along. We would have to develop for Carbon because Apple hadn't implemented Objective C++ yet and we were a C++ shop and we couldn't use half the developers in the company to make a C abstraction layer for Cocoa. We came to an agreement and Apple sent us a palette full of the latest G4 macs and screens. I remember fighting over the 21" screens like children. We had an idiot project manager who insisted that we implement the browser the way Adobe was demanding. It didn't matter that we were pretty much the "experts" on making cross platform embedded browser engines. He was like "Adobe said it... it must be done this way... they are gods".
Well long story short, while we were implementing a crap Carbon based browser engine using crap tools from Metrowerks instead of the good Apple tools (which weren't that good yet). Apple put together a team which abstracted the KDE libraries and built bindings to C and then Objective-C/Cocoa. And they abstracted out everything that was platform specific otherwise from KHTML (Konquerer's underlying html widget) and wrapped it in a Cocoa wrapper and a Carbon wrapper and shipped it as Webkit and Safari. And man did it suck.
Who would have ever imagined that Lars Knoll's half assed KDE web browser would have eventually become the defacto Web standard and the default web browsing engine in every operating system... including Windows... except the strange 5 user corner case operating systems.
Don't bash a project like this. It has value. I immediately considered that I have had many cases in recent times where it could have been of value to me. That said, I wouldn't run a C based web browser engine ever. It's not that you can't write a good web browser in C. It's just that it's the wrong tool for the job. At 160,000 lines, it's a small job to port to something else. When JavaScript evolves into a JIT and the JS runtime is thunking the heck out of the DOM, then it's pretty much no longer an option. Oh, and someone will think it's a good idea to implement proper form controls. That's an insanely massive project, especially when adding WebGL as well. If this browser core catches on, which unfortunately due to the license, I don't expect it will, it will likely be 5 million lines of code almost overnight.