webextensions-examples VS proposal-type-annotations

Check out Firefox examples on github, you’ll like it, I’ve had great experience learning from them to add nifty features to my browser:

https://github.com/mdn/webextensions-examples

This is a place to start https://github.com/mdn/webextensions-examples.

I downloaded Content script registration repository from MDN webextensions-examples on GitHub.

In some cases it does Banning a user doesn't magically make your bugs go away; Can't get response in Ubuntu #506.

It's pretty straightforward with the provided example.

I tried a couples: for example this one is working perfectly but not printing using console.log https://github.com/mdn/webextensions-examples/tree/main/commands

I believe there are already extensions for that. In fact, there's even one on the Mozilla Developer Network's GitHub called Theme Switcher which is essentially a dropdown menu with all of your themes.

I modified this https://github.com/mdn/webextensions-examples/blob/main/native-messaging/app/ping_pong.py example Python Native Messaging host slightly to point to python3 on the shebang line and pass -u to python3

You dont need much. You can use this https://github.com/mdn/webextensions-examples/tree/master/discogs-search as a template

That proposal is not fully compatible with Typescript: https://github.com/tc39/proposal-type-annotations?tab=readme...

They held a meeting a few months ago so it's alive but probably still years away.

https://github.com/tc39/proposal-type-annotations/issues/184

I particularly like this thread in the TC39 types proposal. TypeScript IS a development trojan horse and locks you into the Microsoft Way of being a JS developer.

Edit: There is a proposal to extend JavaScript with type annotations, which would allow ("a reasonably large subset") of TypeScript to run directly in the browser. Yay!

https://github.com/tc39/proposal-type-annotations

More importantly, TypeScript typically commits to build things into itself when the proposal in JavaScript reaches Stage 3. The pattern matching proposal in JavaScript is Stage 1, but depends on many other proposals as well that may or may not need to be at Stage 3 as well for it to work. This particular proposal is interested on pattern matching on JavaScript Objects and other primitives, just like Python does with it’s native primitives. These are also dynamic types which helps in some areas, but makes it harder than others. Additionally, the JavaScript type annotations proposal needs to possibly account for this. So it’s going to be awhile. Like many years.

this is exactly what I want from the _Types as Comments_ proposal[0] as I think it's the only way that types can feasibly become part of the language. It's hard to imagine how all of the concepts TS introduces via special syntax can be covered otherwise.

[0] https://tc39.es/proposal-type-annotations

Crossing my fingers that the proposal for allowing (browser-ignored) type annotations in javascript progresses: https://tc39.es/proposal-type-annotations/

Between that, HTTP2/3 and ES modules many of the downsides for building apps with no compile step are almost completely mitigated.

JSDoc can get you pretty far, but it can be clumsy sometimes. There’s a [TC39 proposal](https://github.com/tc39/proposal-type-annotations) to allow types to live in JS code and be treated as comments (similar with Python types today)