onenet云平台使用_使用平台

onenet云平台使用

The other day I was listening to the latest Shop Talk Show podcast while out for my morning run. They had Jen Simmons on the show, talking about (among other things) the standards process. It’s a great conversation, as you would expect—Jen’s super smart and has been doing great, meaningful work for a long time.

前几天，我在早上跑步时收听最新的Shop Talk Show播客 。 他们让Jen Simmons参加了展览，讨论了标准流程。 正如您所期望的那样，这是一次很棒的对话，Jen超级聪明，并且长期以来一直在做伟大而有意义的工作。

Among the things that she discussed is the care that has to go into new browser features because once shipped, it’s there for good. Most of us don’t have to worry about things to that same level because:

她讨论过的事情之一就是必须对新的浏览器功能进行维护，因为一旦交付，它就永远存在。 我们大多数人都不必担心相同水平的事情，因为：

…you can always delete all your code later. You can always say, ‘Oh, this thing I shipped quickly for my project, that was a bad idea. Let’s obliterate it and re-do it better later.’ But with the web, there’s two things. One, we don’t get to change it and ship it again later, almost ever. If we hurry up and we ship subgrid, and subgrid is crappy, there’s no, like, fixing it. We’re stuck with it.

…您以后总是可以删除所有代码。 您总是可以说：“哦，我为我的项目Swift发货了，这是一个坏主意。 让我们消除它，然后再做得更好。” 但是有了网络，有两件事。 第一，我们几乎不需要更改它，而以后再重新发送。 如果我们抓紧时间并运送subgrid，并且subgrid太烂了，就没有办法修复它了。 我们坚持下去。

This permanence to the web has always been one of the web’s characteristics that astounds me the most. It’s why you can load up sites today on a Newton, and they’ll just work. That’s in such sharp contrast to, well, everything I can think of. Devices aren’t built like that. Products in general, digital or otherwise, are rarely built like that. Native platforms aren’t built like that. That commitment to not breaking what has been created is simply incredible.

网络的持久性一直是令我最震惊的网络特征之一。 这就是为什么您今天可以在Newton上加载网站，并且它们可以正常运行的原因 。 这与我能想到的一切形成了鲜明的对比。 设备不是那样构建的。 一般而言，数字产品或其他产品很少像这样构建。 本机平台不是那样构建的。 不破坏已创建内容的承诺简直令人难以置信。

Jen’s other point, too, is an important one to remember:

詹(Jen)的另一点也是要记住的重要一点：

…And the other thing is that we’re not solving for one website. We’re not solving for facebook.com, or youtube.com, or codepen.io or for…whatever. We’re solving for the entire web and every use case ever all at the same time.

…另一件事是我们没有解决一个网站的问题。 我们不为facebook.com，youtube.com，codepen.io或任何其他方式解决问题。 我们正在同时解决整个网络和所有用例。

She gives an example, later on, discussing how even something seemingly simple, underlines, becomes so much more intense when you need to solve for everyone:

随后，她提供了一个示例，讨论了当您需要为每个人解决时，看似简单的下划线如何变得如此强烈：

Well, what about these languages that are typeset vertically? What is the typography in Japan? What’s needed for this kind of script that is completely different than the Latin alphabet? And there’s a long conversation about that and then, ‘Wow, we’re shipping something that actually works for all the languages and all the scripts around the world.’ Or it almost does and there’s a few pieces missing but we’re dedicated to going ahead and finishing those pieces as soon as we can.

那么，这些垂直排版的语言呢？ 日本的版式是什么？ 这种与拉丁字母完全不同的脚本需要什么？ 对此进行了漫长的讨论，然后，“哇，我们正在交付一种实际上适用于世界上所有语言和所有脚本的东西。” 或几乎可以做到，并且缺少一些内容，但是我们致力于尽快完成并完成这些内容。

There’s a lot of thought and consideration that goes into deciding what makes its way into this incredible platform and what doesn’t.

在决定什么因素进入这个令人难以置信的平台时，有很多想法和考虑。

Another person I have a ton of respect for and who has been doing incredibly important work for a long time is Alex Russell. In particular, he’s put an absurd amount of time and energy into advocating for being careful about the overreliance on JavaScript that is leading to much of the web’s current performance issues.

我一直很敬重并且做了不可思议的重要工作的另一个人是Alex Russell 。 特别是，他花费大量的时间和精力来提倡谨慎对待对JavaScript的过度依赖，而JavaScript过度依赖导致许多当前的Web性能问题。

I thought about Jen’s comments when I saw one person stating that Alex was trying to “sell you on fairy tales of Use the Platform”.

当我看到有人指出亚历克斯(Alex)试图“向您出售使用平台的童话”时，我想到了詹的评论。

I don’t want to single that person out because I’m not here to encourage a pile-on, but also because they’re hardly the first person to express that general sentiment. But, that statement about the “fairy tale of Use the Platform” has really stuck with me, because it feels…wrong.

我不想单挑那个人，因为我不是在这里鼓励积累意见，还因为他们几乎不是第一个表达这种总体观点的人。 但是，关于“使用平台的童话”的说法确实困扰我，因为感觉……是错误的。

So much care and planning has gone into creating the web platform, to ensure that even as new features are added, they’re added in a way that doesn’t break the web for anyone using an older device or browser. Can you say the same for any framework out there? I don’t mean that to be perceived as throwing shade (as the kids say). Building the actual web platform requires a deeper level of commitment to these sorts of things out of necessity.

为了创建Web平台，已经进行了很多工作和计划​​，以确保即使添加了新功能，对于使用旧设备或浏览器的人来说，添加新功能的方式也不会破坏网络。 您可以针对任何框架说同样的话吗？ 我的意思并不是要被当作投掷阴影(就像孩子们说的那样)。 构建实际的Web平台需要承担这些事情出于需要更深层次的。

And as some frameworks are, just now, considering how they scale and grow to different geographies with different constraints and languages, the web platform has been building with that in mind for years. The standards process feels so difficult to many of us because of the incredible amount of minutiae that becomes critical. That security issue that might maybe be a problem? Maybe you feel comfortable taking that risk but when you’re creating something that everyone, everywhere is going to use, it becomes a valid reason for not shipping.

而且，就目前而言，考虑到某些框架如何扩展并发展到具有不同限制和语言的不同地理位置，Web平台多年来一直在考虑这一点。 对我们许多人来说，标准流程感到如此困难，因为大量的细节变得至关重要。 该安全问题可能是个问题？ 也许您会冒险冒这个险，但是当您创建所有人都可以使用的东西时，这便成为不发货的正当理由。

People talk a lot about the web being accessible or performant by default, and while it’s not perfect, it’s also not that far from being true. Creating the platform means you have to prioritize these things.

人们经常谈论默认情况下可访问或性能良好的Web，虽然它并不完美，但也离真实不远。 创建平台意味着您必须优先考虑这些事情。

If you care at all about reaching people outside of the little bubbles we all live in, using the platform can’t be a fairy tale: it has to be the foundation for everything that we build.

如果您根本不在乎与我们所有人生活中的小气泡接触，那么使用该平台绝不是童话故事：它必须是我们构建的一切的基础。

That doesn’t mean that foundation is enough, or always right.

这并不意味着基础就足够，或者永远都是正确的。

Are there limitations? Absolutely! There’s a reason why we still have a standards body, 26 years or so after HTML was first specified: because the work isn’t done and never (knock on wood) will be. (It’s also why I find it very encouraging that folks like Nicole Sullivan are hard at work to identifying some of the things we need frameworks for that should probably be in the browser instead.)

有限制吗？ 绝对！ 有一个原因为什么我们仍然有一个标准机构，在第一次指定HTML后约26年：因为这项工作还没有完成，也永远不会(敲敲木头)。 (这也是为什么我感到鼓舞的是，像Nicole Sullivan这样的人正在努力确定我们需要的某些框架，这些框架可能应该在浏览器中。)

The web thrives on a healthy tension between stability and the chaos of experimentation. It’s perfectly fine, and necessary at times, to use tools to augment issues and limitations we may have on the web. I have no problem with that at all.

在稳定性和实验混乱之间，健康的张力使网络蓬勃发展。 使用工具来增加我们在网络上可能存在的问题和局限性是非常好的，而且有时是必要的。 我一点都没有问题。

But it’s important that we do so very carefully because there are definite trade-offs.

但是重要的是，我们必须谨慎行事，因为存在一定的取舍。

To create the standards that make it into the platform, careful care is given to each and every feature to minimize the security risks. Every new feature has to be carefully considered from an accessibility perspective to make sure that not only does it not cause harm, but that assistive technology has all the information it needs to be able to provide people with a usable experience. Performance has to be top of mind for each new standard, to ensure that shipping it won’t cause undue bloat or other performance issues.

为了创建将其纳入平台的标准，我们会仔细注意每个功能，以最大程度地降低安全风险。 从可访问性的角度出发，必须仔细考虑每个新功能，以确保它不仅不会造成伤害，而且确保辅助技术具有所需的所有信息，以便能够为人们提供可用的体验。 对于每个新标准，性能都必须放在首位，以确保发布时不会引起过大的膨胀或其他性能问题。

And each of these things must not be considered simply in one single context, but for all sites and across geographies, languages, devices, and browsing clients.

而且，这些事情中的每一项都不能仅仅在一个单一的上下文中加以考虑，而应针对所有站点以及跨地域，语言，设备和浏览客户端。

Can you say, with confidence, that the same level of care is given in the tools and frameworks we use or build?

您能否满怀信心地说，我们使用或构建的工具和框架给予了同等的关注？

Use the platform until you can’t, then augment what’s missing. And when you augment, do so with care because the responsibility of ensuring the security, accessibility, and performance that the platform tries to give you by default now falls entirely on you.

除非无法使用，否则请使用该平台，然后增加缺少的内容。 而且，当您进行扩充时，请务必谨慎，因为确保平台默认为您提供的安全性，可访问性和性能的责任现在完全落在了您身上。

翻译自: https://timkadlec.com/remembers/2019-10-21-using-the-platform/

onenet云平台使用