You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's a good point. We have had informal compatibility targets a year ago, particularly regarding display resolution, based on the demography we observe on our traffic @ landing and blog websites.
But it is true that this policy should be a company/product-wide requirement. We will check again how are ours stats regarding that to target X% (e.g. 95%+) and adapt with some heuristics or other stats on top to be a bit broader (e.g.: more users are more likely to be using Windows than our current visitor user base shows).
Sure. Also we'll need different targets for landing/blog and gitbase-web/bblfsh-web. I think it's safe to assume that the later could support less browsers (it's already the case).
Note: Not adding IE/Edge support because of data, but this could eventually change in the future if becomes a requirement for certain web products running on enterprise settings. On the bright side, MS pushing for Windows updates more aggressively and dropping the Edge engine in favor of Chromium should help it in the long run.
Looking at the data segmented by month, it looks like 2 latest for Chrome, 1 latest for Firefox and 1 latest for Safari would cover pretty much our current audience (82%). And 3 latest for Chrome, 2 latest for Firefox and 2 latest for Safari if we want to be more conservative (86%).
Activity
marnovo commentedon Oct 11, 2018
That's a good point. We have had informal compatibility targets a year ago, particularly regarding display resolution, based on the demography we observe on our traffic @ landing and blog websites.
But it is true that this policy should be a company/product-wide requirement. We will check again how are ours stats regarding that to target X% (e.g. 95%+) and adapt with some heuristics or other stats on top to be a bit broader (e.g.: more users are more likely to be using Windows than our current visitor user base shows).
smola commentedon Oct 11, 2018
Sure. Also we'll need different targets for landing/blog and gitbase-web/bblfsh-web. I think it's safe to assume that the later could support less browsers (it's already the case).
marnovo commentedon Jan 17, 2019
@smola from https://github.com/src-d/product/issues/302#issuecomment-455313094:
smola commentedon Apr 5, 2019
Looking at the data segmented by month, it looks like 2 latest for Chrome, 1 latest for Firefox and 1 latest for Safari would cover pretty much our current audience (82%). And 3 latest for Chrome, 2 latest for Firefox and 2 latest for Safari if we want to be more conservative (86%).