W3Techs
provided by
Q-Success
Home Technologies Reports API Sites Quality Users Blog Forum FAQ Search

Featured products and servicesadvertise here

Blog Categories

All

News
AddThis
AddToAny
Adobe DTM
AdRoll
Advertising Networks
Akamai
Alibaba
Amazon
Amazon CloudFront
Angular
Apache
ASP.NET
ASP.NET Ajax
Baidu Analytics
Baidu Share
Bitrix
Blogger
Bootstrap
CDNJS
CentOS
Character Encodings
China Telecom
China Unicom
Chitika
Client-side Languages
Cloudflare
Cloudflare Server
ColdFusion
Compression
Concrete CMS
Content Delivery
Content Languages
Content Management
Cookies
CSS Frameworks
Data Centers
DataLife Engine
Debian
Default Protocol Https
DigiCert
DigiCert Group
Discuz!
DNS Servers
Dojo
DoubleClick
Drupal
Elementor
Email Servers
Ensighten
ExoClick
Facebook
Facebook Pixel
Fastly
Fedora
Flash
Full Circle Studies
Gemius
Gentoo
GlobalSign
Gmail
GoDaddy Group
Google
Google +1
Google Ads
Google AdSense
Google Analytics
Google Hosted Libraries
Google Servers
Google Tag Manager
GridPane
Gunicorn
Histats
Hostinger
Hotjar
HTML
HTML5
HTTP/2
HTTP/3
IdenTrust
Image File Formats
Infolinks
IPv6
Java
JavaScript
JavaScript Libraries
Joomla
JQuery
JQuery CDN
JsDelivr
Let’s Encrypt
Liferay
LinkedIn
Linux
LiteSpeed
Magento
Markup Languages
Matomo
Matomo Tag Manager
Microsoft
Microsoft-IIS
Modernizr
MooTools
New Relic
Newfold Digital Group
Nginx
Node.js
Operating Systems
OVH
PHP
Pinterest
Plesk
Plone
PNG
PopAds
PrestaShop
Prototype
Python
Quantcast
React
Red Hat
Reverse Proxies
Ruby
RunCloud
Scala
Scientific Linux
Sectigo
Server Locations
Server-side Languages
SharePoint
Shopify
Silverlight
Site Elements
Social Widgets
SPDY
Squarespace
SSL Certificate Authorities
Symantec Group
Tag Managers
Tealium
Team.blue
Tomcat
Top Level Domains
Traffic Analysis Tools
Twitter
TYPO3
Ubuntu
Umeng
Underscore
United Internet
Unix
Unpkg
UTF-8
VBulletin
Web Hosting
Web Panels
Web Servers
WhatsApp
Windows
Wix
WooCommerce
WordPress
WordPress Jetpack
Xandr
XHTML
Yandex.Direct
Yandex.Metrica
YUI Library

Changes in client-side programming languages surveys

Posted by Sam Soltano on 16 June 2011 in News, Client-side Languages

Summary:

We stopped publishing the market share data in the client-side programming languages surveys. They were no longer useful.

We used to show both usage data and market share data in our client-side programming languages surveys.

We found that the surveys benefit from dropping the market share data for two reasons:

First, JavaScript had a "market share" of almost 100%. That means that almost all the sites that used any client-side programming language, also used JavaScript. The consequence of that was, that the market share values in the various reports were the same as the usage data, just 10% higher (JavaScript us used by 90% of the sites). Therefore, that value gave little extra information, and was just a source of confusion.

Second, some of the reports, such as the Ranking Breakdown report were based on market share data. Since this was always near 100% for JavaScript, one could not see the differences in the various ranking groups. In the new form of the report (the current form), we see that JavaScript is used more by high-traffic sites compared to average sites (96.9% vs. 89.5%), whereas Flash is used less (25.8% vs. 27.3%). That was not so clearly visible before.

It is rare, that leaving out data makes a survey better, but we think that is the case here.

_________________
Please note, that all trends and figures mentioned in that article are valid at the time of writing. Our surveys are updated frequently, and these trends and figures are likely to change over time.

Share this page


About Us Disclaimer Terms of Use Privacy Policy Advertising Contact
W3Techs on   LinkedIn LinkedIn Twitter Twitter Mastodon Mastodon Bluesky Bluesky
Copyright © 2009-2024 Q-Success