我为什么要关心歌剧?

发布于 2024-09-11 12:20:31 字数 454 浏览 2 评论 0 原文

首先,我并不反对Opera。似乎当我遇到跨浏览器问题并进行一些研究时,我总是能找到“解决方案”,但后来我看到一条评论大喊大叫,说我正在寻找的跨浏览器解决方案在 Opera 中不起作用。

我应该关心吗?随着 IE 终于与 IE 9 一起行动,谷歌的 Chrome 和其他类似 Safari 的浏览器进展顺利,而 Firefox 一如既往地稳定,这是我需要担心的问题吗?如果这很耗时,那么我是否值得在 Opera 运行之前四处闲逛? Opera 真的有那么创新吗?其市场份额将超越 Safari、Firefox、IE 和 Chrome?

我现在的倾向是等待 Opera 迎头赶上,并保留我支持四大浏览器的脚本不变。当然,在 Opera 中调试脚本可以帮助我学习新东西。但有时我有更大的拳头要炸。 Opera 要么迎头赶上,要么消亡。它可能已经赶上了,我知道 Opera 的发布周期现在相当快。所以也许我在论坛中看到的问题此时是空的。

同意还是不同意?

Firstly, I'm not against Opera. It just seems when I encounter cross browser issues, and do a little research, I always find "the fix", but then I see a comment crying foul that the cross browser solution I'm looking at doesn't work in Opera.

Should I care? With IE finally getting its act together with IE 9, Google's Chrome and other Safari like browsers coming along nicely, and Firefox rock stable as always is this an issue I need to worry about? Is it worth it to me to fool around until I get Opera working if it is time consuming? Is Opera really that innovative to where it's market share will shoot up past Safari, Firefox, IE, and Chrome?

My inclination at this point is to wait for Opera to catch up and leave my scripts that support the big 4 browsers as is. Sure debugging the scripts in Opera could help me learn something new. But sometimes I have bigger fist to fry. Opera will catch up or die. It might already have caught up, I know the release cycle is fairly quick now for Opera. So maybe the issues I see in the forums are null at this point.

Agree or disagree?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(6

难得心□动 2024-09-18 12:20:31

我会考虑这里的客户并尝试获取有关不同市场的统计数据。

在某些地区,Opera 是排名前 3 的浏览器落后 IE 和 Firefox 不太远(例如,俄罗斯),因此如果您不想失去客户,您应该关心 Opera。在其他地区如美国歌剧院的份额几乎不存在。

I would think about my customers here and try to get stats about different markets.

In some regions Opera is the Top 3 browser & not too far behind IE and Firefox (for example, Russia) so you should care about Opera if you don't want to lose customers. In other regions like US Opera's share is almost non existent.

葬心 2024-09-18 12:20:31

答案是,这取决于你的市场研究。如果您的用户/平台现在或将来都不可能使用 Opera,那么也没关系。如果您的公司有一个更大的团队来决定支持哪些浏览器,而您支持 Opera,那么您别无选择。

另一方面,如果您正在做出决定,并且您没有太多关于您的市场的信息,或者您的用户的现有统计数据,您可以进行一般研究:http://www.w3schools.com/browsers/browsers_stats.asp

对于平台示例,任天堂似乎强烈支持 Opera:http://www.opera.com/devices/

我理解技术头脑有时(游戏行业作为例如)推动市场。他们具有很强的口碑代表性,能够引领潮流。

说到口碑,激怒用户通常对业务不利:)

为了支持奇怪的浏览器,许多开发人员创建了包含怪异模式的库,并简单地调用这些库,而不用担心每个页面的问题。我不是网络开发人员,但我知道现有的库也可以做到这一点。

这个网站看起来也很有前途:http://www.quirksmode.org/

The answer is, it depends on your market research. If none of your users/platforms are likely to use Opera now, or in the future, then it doesn't matter. If your company has a larger group making the decisions of which browsers to support, and you are supporting Opera, then you have no choice.

On the other hand, if you are making the decisions, and you don't have much information on your markets, or existing statistics from your users, you could go with general research: http://www.w3schools.com/browsers/browsers_stats.asp

For platform examples, Nintendo seems to strongly support Opera: http://www.opera.com/devices/

I understand that tech-heads sometimes (the gaming industry as an example) drive the market. They have a strong word-of-mouth representation, and can lead trends.

Speaking of word-of-mouth, angering your users is generally bad for business :)

In order to support strange browsers, many developers create libraries that includes quirk-modes, and simply call into those, instead of worrying about problems per-page. I am not a web developer, but I understand there are existing libraries that also do this.

This site also looks promising: http://www.quirksmode.org/

要走就滚别墨迹 2024-09-18 12:20:31

当您选择浏览器作为主要测试平台时,您就隐含地选择了一组功能和怪癖。在开发过程中,您将习惯性地避免这些怪癖(有时会出现有风险或损坏的解决方法)并使用这些功能(可能是特定于供应商的或专有的)。

当在尽可能多的浏览器中进行测试和关注时,您将更加了解哪些功能是标准化且可靠的,您将了解到针对 A 怪癖的解决方法在哪些地方存在风险并会破坏 B,并且您的代码通常会得到改进。对我来说,最好的答案(不仅仅是“测试用户使用的内容”)是今天更好的代码可以为您提供更好的未来兼容性。也许今天使用 Opera 进行的测试将识别出可能导致 IE10 出现问题的 CSS 片段?

(我实际上认为您不应该解决小型浏览器中的错误 - 如果您确定错误存在于浏览器中而不是您的代码中,请报告错误并保留它。)

When you choose a browser as your main test platform, you make an implicit choice of a set of features and quirks. While developing you will habitually avoid those quirks (sometimes with risky or broken workarounds) and use those features (which may be vendor-specific or proprietary).

When testing in and caring about as many browsers as possible, you will be more aware of what features are standardised and reliable, you will learn where a workaround against A's quirks is risky and breaks B, and your code will generally improve. For me the best answer (beyond just "test in what your users use") is that better code today gives you better future compatibility. Perhaps testing with Opera today will identify a CSS snippet that would have caused problems in IE10?

(I would actually argue you should not work around bugs in minor browsers - if you're certain the bug is in the browser and not in your code, report the bug and leave it.)

夏末 2024-09-18 12:20:31

如果你关心手机用户,你也应该关心 Opera。我开发 C#,我注意到 Opera 呈现网站的方式与手机浏览器(通常是黑莓)相同。对于 xml、cdata、javascript 语法也同样严格。当firefox、chrome和IE渲染网站时,Opera和手机会发现自己的错误。只是一个简单的测试工具:)

Also you should care about Opera if you care about mobile phone users. I develop C# and I noticed, that Opera renders websites the same way as mobile phone browsers (usually blackberry).. It's the same strict about xml, cdata, javascript syntax. When firefox, chrome and IE would render websites, Opera and mobile phones would find their own errors. Just an easy testing tool :)

甜扑 2024-09-18 12:20:31

我关心的唯一原因是它仍然拥有市场份额,忽视它会疏远一定比例的用户(无论多小)

Only reason I care is that it still has a market share and to ignore it alienates a percentage of users (no matter how small)

巨坚强 2024-09-18 12:20:31

你不应该关心。 Opera 的实现比MSIE 还要差。

例如,考虑他们的“开发控制台”:

http://dev.opera.com/tools/

这是他们提供的用于加载它的代码(在该页面上的“开发人员控制台”按钮处):

function(){
  var ele=document.documentElement.appendChild(
    document.createElementNS('http://www.w3.org/1999/xhtml',
                             'script')
    );
  ele.onload = function(){
    this.parentNode.removeChild(this);
  };
  ele.src='http://devfiles.myopera.com/tools/developer/8679/devConsole.js';
})()

问题是,指向 JavaScript 源的链接已损坏并返回 404:

http://devfiles.myopera.com/tools/developer/8679/devConsole.js

你真的想要基于一家甚至无法管理自己的 Web 开发(或网站)的公司的产品进行 Web 开发?

使用人们实际使用的浏览器继续前进并提高工作效率。

You shouldn’t care. Opera’s implementation is even worse than MSIE’s.

Consider, for example, their “Development Console”:

http://dev.opera.com/tools/

Here's the code they provide to load it (at the “Developer Console” button on that page):

function(){
  var ele=document.documentElement.appendChild(
    document.createElementNS('http://www.w3.org/1999/xhtml',
                             'script')
    );
  ele.onload = function(){
    this.parentNode.removeChild(this);
  };
  ele.src='http://devfiles.myopera.com/tools/developer/8679/devConsole.js';
})()

Problem is, that link to the JavaScript source is broken and returns a 404:

http://devfiles.myopera.com/tools/developer/8679/devConsole.js

Do you really want to do web development based on a product from a company that can’t even manage their own web development (or website)?

Move along and be productive with browsers that people actually use.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文