4 ms·
Does WebKit face a troubled future now that Google is gone?
- tambourine_man 14y agoThis divorce is going to be painful.
- general_failure 14y agoIt would be if there was some divorce
- Someone 14y agoIMO, there definitely is a divorce. It seems as amical as divorces can be, though. From what I read, both parties seem to think it's better for them to split ways, and both parties are offering each other assistance to make moving house as nice as possible for both parties. Google, in particular, is offering assistance in removing compile-time options from the source, offers to keep their build servers running until Apple has a replacement, etc.
- moomin 14y agoI'd say it's a bit more like Google walking out and leaving Apple with the kids. I doubt Apple will be able to sue for maintenance.
- DannyBee 14y agoGiven that Google offered repeatedly on the mailing lists to help remove any code/features that webkit no longer wanted, i don't see how it's like that at all?
- cube13 14y agoAnd how does that help with maintaining the current functionality that Google engineers are supporting? Presumably, the code that the Webkit team wants to remove is the interface with Chrome/Chromium. That's the easy part, in the grand scheme of things. The hard part is getting new people to pick up the features and functionality that was being worked on by people who have moved to Blink. That's going to be a huge challenge, especially for features that were half implemented.
- DannyBee 14y agoSorry, but people and companies come and go from open source projects all the time. You act as if this is not the typical happening in an open source project. Just because it happens to involve a large company, or a well known project, doesn't change anything. Either the project will find/attract new contributors to support those features, or it won't. If it doesn't, it generally means it wasn't going to stay viable. Plenty of companies left GCC and left features unmaintained. They either find new maintainers, or get removed, and the project moves on. This is the life of an open source project. It's not like a divorce at all. It's like a large collaboration where people are free to leave at any time. When people leave, either the collaboration absorbs the loss, or it doesn't.
- tambourine_man 14y agoSorry, but people and companies come and go from open source projects all the time. Yes, bad things happen all the time. Frequency doesn't turn a bad thing good though.
- DannyBee 14y agoUh? It's not necessarily bad or good for a company or person to leave. It all depends on whose perspective you are using (and i'm not talking about either the company or the project). Sometimes things are bad for one project, but good for an ecosystem. Or the reverse. Folks who started EGCS, including a company worth of folks, left GCC to do so. Was this bad for GCC? Most people with gut reactions thought it was "bad". It certainly ended up improving the state of the world, and in fact, later turned out very good for the GCC project because it got a much better GCC out of it. Basically, I think you may need a little perspective here.
- general_failure 14y agoYet another article full of FUD and speculation. If this, if that, maybe this, maybe that. Seriously, please. Someone reform the media industry for me. Are there any startups here doing this? Back to the article. WebKit won't allow hooking in random JS engines. Allowing this slows things down because many DOM access optimizations can be achieved by assuming a specific engine. This is totally reasonable thing. People who are complaining don't contribute to the project at all and are just armchair critics. Same goes for this web developer who is complaining on webkit-dev. He is an arm chair critic. Apple is talking about removing a feature that no one is stepping up to maintain. CSS variables is not a _standard_ and not close to being a standard and that is the key. If it was, Apple won't be removing it. I don't know whats worse - armchair critics or media creating whole articles based on speculation and armchair critics.
- criley 14y agoYou're an armchair critic of armchair critics, how meta of you.
- general_failure 14y agoI am webkit contributor (committer). I didn't say it before because it doesn't matter to this conversation. And neither do I want my comment to have some magical weight because of my contribution status. Your argument is not valid though. I am not actively writing media articles 'prediciting' that WebKit project is going to have a painful time or going on webkit-dev telling people what to do.
- saraid216 14y agoYes. Clearly what journalism needs is more profit motivation.
- widdershins 14y ago>Are there any startups here doing this? These kinds of articles generate more pageviews than boring, measured, and technically correct articles, so presumably if there were startups doing what you suggest, they wouldn't be doing very well. Media sensationalism stems from human nature, so it's not an problem I see being solved any time soon.
- richardwhiuk 14y agoThe root problem seems to be that Oracle and Samsung want WebKit to continue allowing Nashorn and V8 integration without actually providing any developer resource to the problem.
- tambourine_man 14y agoNope, it's worse than that. https://lists.webkit.org/pipermail/webkit-dev/2013-April/024491.html https://lists.webkit.org/pipermail/webkit-dev/2013-April/024... https://lists.webkit.org/pipermail/webkit-dev/2013-April/024484.html https://lists.webkit.org/pipermail/webkit-dev/2013-April/024...
- mmariani 14y agoPuff piece, a.k.a link bait. Anyone that goes through the discussion threads from which this article originated from will see developers cordially debating about pertinent engeneering topics regarding the future of the project. Nothing more. I personally think both projects will thrive as a result of this fork.
- jfoutz 14y agoAs with all headlines that end with '?' the answer is no.
- solox3 14y agoIn this case, the link is scrotal, like you suggested. However, Betteridge's Law of Headlines was proven wrong by Betteridge himself. For example, "What was life like opposite Thatcher?" cannot be answered by the word "no".
- kyrias 14y agoIt can, most people would just feel like it didn't make sense.
- lnanek2 14y agoGoogle used to contribute to Firefox before Chrome and Firefox is still alive, although more people use Chrome and IE now so it lost its popularity.
- ttrreeww 14y agoI expect WebKit to have similar fate as KHTML actually...
- mitchty 14y agoI doubt it entirely. WebKit has been around since 2001, and given Apple is the creator and primary users, it will stick around.
- amputect 14y agoNo
- glasshead969 14y agoI am disappointed by this article coming from ARS, a site I have huge respect for. The article ignores parts of conversation and chooses the ones which suits its narrative. Developers were concerned about leaving unmaintained code left in the tree, which was previously only used by chrome. If you follow the thread devs were more than happy to keep it as long as someone maintained it. And finally that's what happened. Either way discussions like these are common in Open source project , any project as a matter of fact, but to spin it like this is simply manufacturing a story for page views.
- doe88 14y agoI think this may not be the easiest path (at least short-term) but I would be Apple I would only actively maintain my own JS engine but I would also try to make a nice abstraction for others JS engines, i.e. what Google chose not to do. Maybe it wouldn't be ideal for short term performances, but community wise and future wise it would be a great choice I think. Sadly I don't think this is the path Apple is going to take.
- kmfrk 14y agoThis is one of my favourite things about Hacker News; it allows you to take a peek at an article you assume is clickbait, before you give them the hits and traffic they might be angling for.
- michaelwww 14y agoIt's telling that no one is asking "Will Google be able to go it alone without Apple's help?