I build a demo web app for realime transcribing using OpenAI's newest gpt-4o-transcribe/gpt-4o-mini-transcribe models with their WebSocket realtime API.
Maybe I didn't communicate well, but I was trying to manage the repo you starred, instead of your own repo. You only need this if you have starred a lot of repos.
Where it really shines is when you want to combine routing with state management layer, e.g. Redux. This way route information can be fully consumed by your data layer.
I've used `nav` or `section` for a long time, never found of the difference from `div`. Screen readers? Maybe for `nav`, what about `section` and other 1000 tags with subtle different semantics?
Totally agree. I see front end job descriptions asking for understanding of Java and .Net but no mentioning of JS, CSS or any HTML. There could be easily a miscommunication of misunderstanding what the company want. Not saying the job description used here is wrong, just an example of miscommunication.
Web Playground is command line tool for quick prototyping, demo, tutorial or presentation in the browser. It works by quickly scaffolding just one HTML, one JavaScript and one CSS file, and opening a browser with live reloading. Optionally, you can update playground.yml to enable common preprocessors such as Babel or SASS, or add additional script/style tags to the page.