render VS caniuse

i make two kinds of websites:

- static. markdown rendered to html using github’s api[1].

- dynamic. a go binary and an html file with inlined js zipped together and shipped somewhere[2].

it’s nice to never consider the machinery of either of these anymore. instead i think about building interesting things.

1.

https://github.com/nathants/render

https://nathants.com/

2.

https://github.com/nathants/aws-gocljs

https://gocljs.nathants.com/

github exposes an api to render markdown the same way it renders readmes.

i use that to render markdown to html with a tiny scaffold:

https://github.com/nathants/render

We do have a great tool such as CanIUse and of course, BaseLine is not going to replace it.

Can I use...

Lots of parts to WebRTC ( https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API ) but none that I know that can knock out something outside of your browser. It could maybe overload RAM and get killed.

Try using the offending website on a browser/OS that _doesn't_ have WebRTC such as https://caniuse.com/?search=webrtc. Or try with WebRTC disabled.

Possible you're getting throttled by your router or ISP when certain connections are made.

And there's this https://browserleaks.com/webrtc

A11ySupport.io: The caniuse of accessibility. Lists compatibility of various browser accessibility features for different screen reader and browser combinations.

Ah yep! I just didn't wait long enough. Very cool. Seems like it took a lot of work. And it seems better than other browser-based video editors I've seen in the past, so kudos.

TIL about the webcodecs API to get frames of video and chunks of audio: https://caniuse.com/?search=webcodecs

Can I X, is a question about the readiness/compliance of a certain thing at time = now. Can I use CSS version X was the iconic early meme.

https://caniuse.com/?search=css3

For a generalized example, if you wanted to know if the basketball courts were ready for you to “ball it up” in a certain city, it’d be caniball.com

If you want to know if you can use a certain frontend technology, the idea is like: canwefigma?

It’s a glorified feature matrix, and usually a project of a passionate community. I approve, even if some of the memes are a bit dank.

https://caniuse.com/ is a popular tool to check what web features are working across different browsers - "can you use this and assume that it will work for others".

The article uses custom css @properties which are awesome and have 88% browser support [1].

One thing to watch out for is differences in how browsers handle setting the fallback initial-value. Chrome will use initial-value if CSS variable is undefined OR set to an invalid value. Firefox will only use initial-value if the variable is undefined. For most projects, this won't be an issue, but for a recent project, I ended up needing to use javascript to set default values in Firefox to iron out the inconsistency between browser implementations.

[1] https://caniuse.com/?search=%40property

Safari is the only browser that doesn't support extending HTML element

https://caniuse.com/?search=Custom%20Elements

You forgot to mention (Web)Workers. This is explicit creation, management, and communication with additional threads within JavaScript. What's more, they've been around in JavaScript longer than the V8 engine has even existed!

https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers...

https://caniuse.com/?search=webworkers