3 ms·
You can do so, however, note that you still need acceptance for mainline. Obvious things such as line numbers, are obviously accepted once implemented properly
by zobzu 15y ago
You can do so, however, note that you still need acceptance for mainline.
Obvious things such as line numbers, are obviously accepted once implemented properly.
Note: the below comment is actually inaccurate, I though ruby tag was the language (as the author mentioned js as alternative).
Keeping it for the comments discussing it, but keep in mind I was actually wrong.
Things like a ruby tag might be more complicated than you'd think.
You see, the main difference between Firefox and Chrome (yeah, it's not the UI! ;P) is ideology.
Firefox folks believe in a standard and compatible web. Chrome folks believe in .. implement whatever we think is faster than what we have (or /flamebait hat on, whatever helps Google make money/adverts/lock-in users).
Supporting ruby might fall in the "but it's not standard" "it splits the web" category.
And that's be correct, in my opinion. So you might want to check on that before actually getting the code done, unless you plan to fork.
- jrockway 15y agoChrome folks believe in .. implement whatever helps Google make money/adverts/lock-in users. Citation needed.
- cytzol 15y agoWhile I can't provide a citation, I believe that the contrapositive is true: if it doesn't help Google, it's not going to be implemented. Right now, Google's interests are aligned with a standardised, compatible web, and when Google gets big enough, or greedy enough, it's going to take Chrome in its own direction. Opera still fares badly at Google's services, but they consider IE worth supporting.
- jrockway 15y agoI see. So you're blaming Google now for something you imagine they might do in the future. How could Google defend itself against your accusations?
- cytzol 15y agoNot blaming, but worrying about. There is plenty of software that can read Word's .doc files. Yet I store my data as plain text, as I imagine that the software will be killed or end-of-lifed in the future, even though I can use it fine right now. In the same way, I'd rather use a browser designed for an open, standardised Web. Chrome doesn't have nearly enough market dominance for me to make accusations about it; I just want to minimise any future disaster scenarios.
- azakai 15y ago> when Google gets big enough [..] it's going to take Chrome in its own direction Hasn't Google already taken Chrome in its own direction? Chrome includes lots of non-standard technologies like Flash, NaCl, Pepper, Chrome Apps, and soon a Dart VM. Google believes these technologies are good, but no other browser does, and not even WebKit. Maybe those are good and useful technologies, that is a separate matter. I'm just pointing out that Google is already well in the process of taking Chrome in the direction Google feels is best, regardless of what the rest of the web thinks.
- zobzu 15y agoI had the hat on. But for the sake of discussion, please keep entire quotes, instead of rewriting what I wrote initially. Chrome folks believe in .. implement whatever we think is faster than what we have For example SPDY is faster. NaCl is faster. That's not bad. It's just not the same focus. Now, NaCl also helps making money and helps with lock-in for example. There are several other examples in the -webkit functions and some things which are not part of the actual webkit (only Chrome's version) such as Dart and the like.
- tingletech 15y agoThe ruby tag is not related to the ruby language http://dev.w3.org/html5/spec/Overview.html#the-ruby-element http://dev.w3.org/html5/spec/Overview.html#the-ruby-element Seems to be part of the standard...
- zobzu 15y agoAlright, I did not actually know that. i'd say go right ahead. I'll note also that it's a draft - something that annoys me with HTML5. New drafts are sent every next day or so, so it's not actually very standard. It's a different story though.