Something fishy is going on down there in the field of browsers. Blink Webkit probably will endanger and split some features of the browsers. As it seems, the developers will have a hard time adapting to the browsers which will lose some of the features, for example the CSS variables. They will find a way, but they will need to stay patient.
CSS variables present a handy tech to ease the programming of the Web page. This can be one casualty in Apple’s Safari browser with Google choosing to move its resources to Blink. Some of the engineers working in Google wanted to use the WebKit engine project just to underlie Google Chrome and Safari so they can speed up the Chrome process and adopt some of the changes to fit them into a single project with open-source. However, splitting WebKit away from Blink will make each web browser more nimble and it will be hard for these two to cooperate.
It will be hard because these common features must be made and maintained by teams which are similar and working for each project, rather than developed by one single team. It’s a complicated open-source, and this was situation in the cases of LibreOffice and OpenOffice.org for office suites, EGCS vs. GCC for software compilers, Joomla and Mambo for software projects.
Over this past weekend, WebKit started combating with CSS variables. This Web standard lets developers define variables, for example “main-bg-color” and then they will have the possibility of using that variable repeatedly.
The “talk” about these CSS variables began this Sunday with a post from Andreas Kling which was posted on the WebKit’s mailing list of the developers. He wrote:
“I’d like to remove the CSS variable feature from the tree now that Chromium has left, as they were the only ones shipping it AFAIK. If we were to keep the feature, my only concern will be that someone needs to maintain this code.
This is not about variables being a bad feature, it’s about removing unmaintained code. We can easily restore the code and continue/complete the implementation later, if/when the functionality is wanted. “
Karen Shaeffer is an open-source programmer and she said that she might be able to handle this problem and maintain the feature. She added that she is interested in WebKit and that this is the perfect time when she can step up and take one for the team. Karen requested a week to bring a decision if she was going to help or not. On this, Apple’s Benjamin Poulain responded that if a week means getting the solution that sounds like a good idea.