英文:
Any pointers on Apps Script deprecation path?
问题
我对在这项技术上构建一些东西感到好奇，但也担心这个停用计划：https://developers.google.com/apps-script/guides/support/sunset
在一方面，上面的链接提到了在过去几年中停用了许多相关部分。另一方面，Apps Script核心尚未列在像这样的审查网站上：https://killedbygoogle.com/
有人可以分享关于为什么/何时Google会放弃这项脚本技术的见解的指示（文章、链接）吗？
谢谢！
英文:
I'm curious about building some things on this technology, but also worried about this sunset schedule: https://developers.google.com/apps-script/guides/support/sunset
On one side, the above link mentions sunset of many collateral parts in last few years. On the other hand, the Apps Script core is not yet listed in review sites like this one: https://killedbygoogle.com/
Can anyone share pointers (articles, links) with insights on why/when would Google ditch this scripting tech ?
Thanks!
答案1
得分: 4
考虑到这一点，大多数已经退役的功能在那个停用列表上都已经被类似的技术替代了。
最初，Apps Script支持基于小部件的工具（带有拖放停靠面板，曾经是GUI构建器和UIService API的可编程组件），但现代开发人员希望更多地控制其应用程序的外观和感觉，因此该技术堆栈被替换为允许开发人员在客户端使用HTML/CSS/JavaScript的API（通过HtmlService）。
有些服务只是被新的实现所替代。例如，SOAP和XML类被XMLService替代。
还要记住，仅因为Apps Script授予对某项服务的访问权限并不意味着它是不可或缺的。Apps Script只是Google广泛的API和服务生态系统的一部分，有时当其中一个服务被弃用并移除时，对该服务的访问权限也必须从Apps Script中移除。这种情况发生在Google Domains API和Fusion Tables上；这两个服务都独立于Apps Script，但为了方便起见，提供了API包装器，允许开发人员直接从Apps Script中以编程方式与这些服务交互。当这些服务被淘汰时，这些包装器被移除是很自然的。
最后，Google将Add-ons的部署移到了他们自己的专用市场（GSM）并将它们从Chrome Web Store中移除。因此，Chrome Web Store被弃用。
所以我不认为App Script会很快就被淘汰。
作为一个计划在这个平台上构建应用的开发人员，你应该关心的是它的限制。你需要了解Apps Script及其配额限制，如果你计划提供一个面向公众的应用程序（比如一个公共插件），你需要了解Google的用户数据政策和敏感/受限范围（查看Google的OAuth2 FAQ）。
英文:
Consider this, the majority of the retired features on that sunset list have been replaced with analogous tech.
Initially Apps Script supported widget-based tools (with drag-and-drop docking panels for what was once a GUI builder and a UIService API as a programmatic component) but modern developers wanted more control over the look and feel of their apps, so that tech stack was replaced with APIs that allowed devs to use HTML/CSS/Javascript (via HtmlService on the client side).
Some services were simply replaced with new implementations. For example, the SOAP and XML classes were replaced with XMLService.
Also keep in mind that just because Apps Script grants access to a service does not mean it is integral to it. Apps Script is just one part of Google's extensive ecosystem of APIs and services and sometimes when one of those services is deprecated and removed, then access to that service has to be removed from Apps Script as well. Such is the case with Google Domains API and Fusion Tables; both of those services are independent of Apps Script but for the sake of convenience API wrappers were supplied that allowed developers to interact programmatically with those services directly from Apps Script. Its only natural that those wrappers are removed when those services are retired.
Finally, Google moved deployment of Add-ons to their own dedicated marketplace (GSM) and removed them from the Chrome Web Store. Hence the Chrome Web store deprecation.
So I don't see App Script going the way of the Dodo bird anytime soon.
What should concern you as a developer looking to build something on this platform are its limitations. You'll need to understand Apps Script and its quota limitations, and if you are planning on offering a public facing application (say a public add-on) you'll need to be aware of Google's User Data Policy and sensitive/restricted scopes (look up Google's OAuth2 FAQ).
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论