GITHUB . COM {}

Matching Content Categories {📚}

• Social Networks
• Video & Online Content
• Dating & Relationships

Content Management System {📝}

What CMS is github.com built with?

Github.com is powered by WORDPRESS.

Traffic Estimate {📈}

What is the average monthly size of github.com audience?

🚀🌠 Tremendous Traffic: 10M - 20M visitors per month


Based on our best estimate, this website will receive around 10,633,976 visitors per month in the current month.

check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush

How Does Github.com Make Money? {💸}

Subscription Packages {💳}

How Much Does Github.com Make? {💰}

Subscription Packages {💳}

Prices on github.com are in US Dollars ($). They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 5,306,226 paying customers.
The estimated monthly recurring revenue (MRR) is $22,286,147.
The estimated annual recurring revenues (ARR) are $267,433,769.

Wordpress Themes and Plugins {🎨}

What WordPress theme does this site use?

It is strange but we were not able to detect any theme on the page.

What WordPress plugins does this website use?

It is strange but we were not able to detect any plugins on the page.

Keywords {🔍}

matches, react, commented, fantasai, dom, specificity, rename, selectors, issue, shipping, webkit, time, exeboss, contributor, css, things, sign, makes, match, lot, current, make, cssmeetingbot, symmetry, sense, method, projects, gibson, close, type, discussion, proposal, long, implemented, doesnt, discussed, inoas, favour, implementation, bkardell, content, navigation, pull, requests, actions, security, closed, comment, live, introduce,

Topics {✒️}

prior csswg discussion css working group full irc log web content spec'ed today dom apis today stable selector features comment metadata assignees improved specificity rules type projects long time ago �functional pseudo-class nonzero-specificity pair current spec projects milestone current implementation selectors dom method css discussed rename discussion 👍 react changed spec dom api ideal world clear pairing org/show_bug involve changing moderately interested [subsequently eliminated sufficiently high alias thereof preferred spelling primary entity injecting dupes nth--child programming languages vendor prefix logical depending compelling cases potentially problematic issue deprecated alias specific case makes sense github milestone relationships related things webkit people live/snapshot fantasai

Payment Methods {📊}

• Braintree

Questions {❓}

• Already have an account?
• Also the DOM method doesn't have specificity either, so making it different is maybe useful?
• Also, before I forget, how about considering :or() instead?
• If we are now talking about 3 things - and one is special in that it has no specificity, perhaps having that thing have close symmetry with the single similar DOM method makes some kind of sense?
• In about 10?
• Maybe it's time to defer the less stable Selector features (like :has() and Live/Snapshot "profiles") to Level 5 and make the rest of Level 4 features transition to CR as fast as possible?
• Maybe that is interesting?
• Rossen: Is either 2 or 7 an option?
• What do you think?
• Astearns: How much web content uses :matches?
• Can we do that?
• Currently does, and :match() is the 0 specificity one?
• Dino: Why ?
• Of S) in WebKit conforming to the current spec?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:[selectors-4] Rename :matches() to :is()
      articleBody:Breaking this one out from https://github.com/w3c/csswg-drafts/issues/2143#issuecomment-433627117 ; @gibson042 wrote: > @fantasai We may not live in an ideal world, but I think we do live in one that's close enough to introduce `:is()` and redefine `:matches()` as a deprecated alias of it. What do you think? The benefits would be: It's much shorter to type, and it makes a clear pairing with :not(), which is its opposite. The downsides would be: It's already shipping in WebKit as `:matches()`. Here's the snippet of [prior CSSWG discussion](https://lists.w3.org/Archives/Public/www-style/2018Jul/0027.html), excerpted from [the naming of `:where()`](https://github.com/w3c/csswg-drafts/issues/2143#issuecomment-433627117): ``` frremy: Why use the :matches() name at all, it's a bad name leaverou: We're stuck with it anyway ... leaverou: Would you object to :is() if it did what :matches() currently does, and :match() is the 0 specificity one? fantasai: No, I would not ... frremy: :matches() was called that way because the DOM API is called that fantasai: Actually, it's very old, original :matches() proposal was from hixie a long time ago, before :any() <dbaron> I implemented :-moz-any() in Gecko in 2010 in https://bugzilla.mozilla.org/show_bug.cgi?id=544834 ericwilligers: It has been in webkit for a long time astearns: How much web content uses :matches? iank: Not a lot, looking at usecounter ericwilligers: usecounter may be wrong Rossen: Is either 2 or 7 an option? they involve changing :matches. webkit people, can we do that? myles: We could myles: We would be moderately interested in updating, but it's low priority dino: Why ? fantasai: Because a well-named proposal otherwise is :is(), but it is bad if it's specificity doesn't match :not() fantasai: So we could change :matches() to be the 0 specificity one, freeing :is() to do what :matches() does now ... [subsequently eliminated :matches() from the list of proposals for #2143, so this was not further discussed] ``` I believe other implementations besides WebKit are getting close to shipping `:matches()` so if we're renaming this, we need to do it asap.
      author:
         url:https://github.com/fantasai
         type:Person
         name:fantasai
      datePublished:2018-10-27T15:56:27.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:16
      url:https://github.com/3258/csswg-drafts/issues/3258
      context:https://schema.org
      headline:[selectors-4] Rename :matches() to :is()
      articleBody:Breaking this one out from https://github.com/w3c/csswg-drafts/issues/2143#issuecomment-433627117 ; @gibson042 wrote: > @fantasai We may not live in an ideal world, but I think we do live in one that's close enough to introduce `:is()` and redefine `:matches()` as a deprecated alias of it. What do you think? The benefits would be: It's much shorter to type, and it makes a clear pairing with :not(), which is its opposite. The downsides would be: It's already shipping in WebKit as `:matches()`. Here's the snippet of [prior CSSWG discussion](https://lists.w3.org/Archives/Public/www-style/2018Jul/0027.html), excerpted from [the naming of `:where()`](https://github.com/w3c/csswg-drafts/issues/2143#issuecomment-433627117): ``` frremy: Why use the :matches() name at all, it's a bad name leaverou: We're stuck with it anyway ... leaverou: Would you object to :is() if it did what :matches() currently does, and :match() is the 0 specificity one? fantasai: No, I would not ... frremy: :matches() was called that way because the DOM API is called that fantasai: Actually, it's very old, original :matches() proposal was from hixie a long time ago, before :any() <dbaron> I implemented :-moz-any() in Gecko in 2010 in https://bugzilla.mozilla.org/show_bug.cgi?id=544834 ericwilligers: It has been in webkit for a long time astearns: How much web content uses :matches? iank: Not a lot, looking at usecounter ericwilligers: usecounter may be wrong Rossen: Is either 2 or 7 an option? they involve changing :matches. webkit people, can we do that? myles: We could myles: We would be moderately interested in updating, but it's low priority dino: Why ? fantasai: Because a well-named proposal otherwise is :is(), but it is bad if it's specificity doesn't match :not() fantasai: So we could change :matches() to be the 0 specificity one, freeing :is() to do what :matches() does now ... [subsequently eliminated :matches() from the list of proposals for #2143, so this was not further discussed] ``` I believe other implementations besides WebKit are getting close to shipping `:matches()` so if we're renaming this, we need to do it asap.
      author:
         url:https://github.com/fantasai
         type:Person
         name:fantasai
      datePublished:2018-10-27T15:56:27.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:16
      url:https://github.com/3258/csswg-drafts/issues/3258
Person:
      url:https://github.com/fantasai
      name:fantasai
      url:https://github.com/fantasai
      name:fantasai
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:16
      interactionType:https://schema.org/CommentAction
      userInteractionCount:16

External Links {🔗}(5)

• How much does https://github.blog gross monthly?
• Get to know https://lists.w3.org/Archives/Public/www-style/2018Jul/0027.html's earnings
• How much revenue does https://developer.mozilla.org/en-US/docs/Web/CSS/:matches#Browser_compatibility bring in?
• How much cash flow does https://caniuse.com/#feat=css-matches-pseudo have monthly?
• Learn how profitable https://www.githubstatus.com/ is on a monthly basis

Analytics and Tracking {📊}

• Site Verification - Google

Libraries {📚}

• Clipboard.js
• D3.js
• Lodash

Emails and Hosting {✉️}

Mail Servers:

• aspmx.l.google.com
• alt1.aspmx.l.google.com
• alt2.aspmx.l.google.com
• alt3.aspmx.l.google.com
• alt4.aspmx.l.google.com

Name Servers:

• dns1.p08.nsone.net
• dns2.p08.nsone.net
• dns3.p08.nsone.net
• dns4.p08.nsone.net
• ns-1283.awsdns-32.org
• ns-1707.awsdns-21.co.uk
• ns-421.awsdns-52.com
• ns-520.awsdns-01.net