謎のGoogle社内Webフレームワーク「Wiz」を追う
Closure Library is in Maintenance Mode · Issue #1214 · google/closure-library
TL;DR: Closure Library will be sunset over the next 9 months, from November 1, 2023, to August 1, 2024. We no longer see it as meeting the needs of modern JavaScript development, and we recommend that users look for alternative solutions. Feel free to skip the background and go straight to the FAQ. In the nearly 14 years since Closure Library was first made public, it's broken a lot of ground and
The saga of the Closure compiler, and why TypeScript won | Hacker News
Interesting read. I wrote the original compiler back in 2002/2003, but a lot changed by the time it was open sourced (including the confusing name -- I just called it a javascript compiler).One detail this story gets wrong though is the claim that, "The Gmail team found that runtime JavaScript performance was almost irrelevant compared to download times." Runtime performance was actually way more
Effective TypeScript › The Saga of the Closure Compiler, and Why TypeScript Won
Here's something that makes me feel old: in just six months, Gmail will celebrate its 20th anniversary. If you weren't actively developing web sites at the time, it's hard to capture just how revolutionary it was. This was a time when JavaScript was held in almost universally low regard. The idea that you could build a sophisticated web app using it was mind-boggling. But it clearly worked and it
packelyze - お前の TypeScript はもっと小さくなる
TypeScriptの型定義ファイルから積極的な圧縮を行うための @mizchi/optools をリリースした。まだ実験中だが、結構動くはず。使う場合は自己責任で。 追記: optools を packelyze に rename した。これは optools という CLI 名が ImageMagick の提供するコマンドとぶつかったため。 試行錯誤の過程は https://zenn.dev/mizchi/scraps/1bdf01f5efb147 にある。 このライブラリは、自分の所属する Plaid の業務時間中に作成した。 想定ユーザー ライブラリ作者 ビルドサイズ厳しいフロントエンド開発者(サードパーティスクリプト等。自分が業務で作った理由がここ) リスクとってでもビルドサイズを縮めたいフロントエンド作者 動機 世の中な TypeScript で書かれたコードは、その型情報を使
TypeScriptのJSDocサポートでできること、できないこと
JSDocで型を定義してTypeScriptの恩恵を受ける
Conformance for Frameworks | Blog | Chrome for Developers
In our introductory blog post, we covered how we've learned a lot while building and using frameworks and tools to develop and maintain large scale web applications such as Google Search, Maps, Photos, and so on. By safeguarding developers from writing code that can negatively affect user experience, we proved that frameworks can play a key role in shifting outcomes for performance and application
DevTools architecture refresh: migrating DevTools to TypeScript | Blog | Chrome for Developers
This post is part of a series of blog posts describing the changes we are making to DevTools' architecture and how it is built. Following up on our migration to JavaScript modules and migration to Web Components, today we are continuing our blog post series on the changes we are making to Devtools' architecture and how it is built. (If you have not seen it already, we posted a video on our work of
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - nicopowa/snippet
Suggestion: minification · Issue #8 · microsoft/TypeScript
GitHub - theseanl/tscc: A collection of tools to seamlessly bundle, minify Typescript with Closure Compiler
JavaScript type annotation syntax comparison
GitHub - toshi-toma/closure-codemod: Closure codemod scripts
Officially mark this repository as end-of-life by nex3 · Pull Request #151 · google/closure-stylesheets
GitHub - jsdoc-type-pratt-parser/jsdoc-type-pratt-parser: A pratt parser for jsdoc types
Fold "String#replaceAll" when all the values involved are literals. · google/closure-compiler@d91bd1b
GitHub - Blodwynn/-VSCODE-.soy-language-server-client: Visual Studio Code .soy language server + client
GitHub - ChadKillingsworth/closure-calculate-chunks: A utility to parse JS files, determine dependencies and specify which output chunk source files appear in for closure-compiler.
IE 11 Support Removal · Issue #1086 · google/closure-library