To be fair, Google sends out multiple emails notifying that you won't receive new emails unless you upgrade or clear things out. If they read their emails even somewhat regularly -- which I acknowledge isn't a given for many people -- they'd know what's coming.
That isn’t the problem. The problem is Google photos pushes you to back up your tens of gigabytes of photos to your free Gmail account repeatedly until you say yes just once. At that point it fills up your email account with your photos and then disables your email until you pay them. Making statements about how often they warn you this is happening isn’t very helpful. No normal person would think of that as a consequence of using Google photos.
Especially as JSDoc is used for type annotations and even type checking in some projects. It's not in ECMA standard but widely used and well supported. The IR as it is implemented today will run into serious trouble.
It's funny they bother to bring up the half dead "Google Closure Compiler" as an example.
And my dumb brain still don't understand how IR is "better" than AST after reading this post. Current AST based JS tools working reasonably well, and it's not clear to me how introducing this JSIR helps tool authors or downstream users, when there are all those roadblocks mentioned at the end.
Why is it half dead? They only jettisoned the ancient support library, the compiler itself AFAIK remains best in class and has commits on GitHub as of 15 hours ago
Today, you get the more streamlined experience of push, 3 clicks to restart CI & container build, push 1000 yamls, click to restart the build again, cry when it all fails.
Not even in "tech circles". Anecdotally, most of my colleagues -- mostly software engineers -- don't use adblocker at home or at work. It hurts my eye to see their screens. But they don't care.
(The workspace does not disallow adblocker extensions.)
Even cool projects can learn from others. Maybe they missed something that could benefit the project, or made some interesting technical choice that gives a different result.
For the readers/learners, it's useful to understand the differences so we know what details matter, and which are just stylistic choices.
But it isn't the OP's responsibility to compare their project to all other projects. The GP could themselves perform the comparison and post their thoughts instead of asking an open ended question.
It isn't, but such information will be immensely helpful to anyone who wants to learn from such projects. Some tutorials are objectively better than others, and learners can benefit from such information.
Well, the person who asked the question, for one. I'm sure they're not the only one. Best not to assume why people are asking though, so you can save time by not writing irrelevant comments.
reply