webtransport VS codewars.com

WebTransport is now enabled by default and will be going to release with 114. As the original Explainer notes, it enables multiple use-cases that are hard or impossible to handle without it, especially for Gaming and live streaming. It covers cases that are problematic for alternative mechanisms, such as WebSockets. Built on top of HTTP3 (HTTP2 support will be coming later). The current implementation in Firefox is passing 505 out of 565 Web-Platform Tests.

WebTransport is still an emerging technology. As of November 2022, WebTransport is a draft specification with W3C, and there’s always a chance that aspects related to how it works may change.

Sort of. The browser will re-use the connection if you have a bunch of resources in the HTML. When rendering it sees that it needs 2 images and 3 javascript files from the same server, so it pipelines all of those. But for requests initiated from javascript, you're going to get a new connection for each one unless you're using a library that implements the long-polling hack. SocketIO can use the long-polling hack as a fallback if websockets is not supported. HTTP/2 (formerly SPDY) gets part of the way to replacing websockets, but it's not a synchronous link. Only the client can send messages to the server and the server can only respond to those message (with websockets, either side can send messages once the connection is open). FWIW, less than 50% of websites use HTTP/2. HTTP/3's webtransport looks like it could replace websockets, but it also looks like it'll live along side websockets.

If it's streaming data like dashboard statistics the new WebTransport API might be a much better base: https://github.com/w3c/webtransport/blob/main/explainer.md

Are you guys looking into the Web Transport protocol for the future? Right now you have to tunnel the websocket connections over http2 and it will probably be the same for http3 afaik.

I know there is this work in progress (https://w3c.github.io/webtransport/) and websockets are probably fine for a long time but sooner or later (unless there is an update to websockets) it will probably be faster to just do normal http requests and listen on server sent events.

What are your thoughts for Liveview for the future? Will it forever stay on websockets or would you be open to change the underlying technology if / when new stuff becomes available?

The W3C draft is here: https://github.com/w3c/webtransport

It's taken nearly 10 years for QUIC to be refined and adopted in the wild and we're basically there. There's even a new browser API in the works called WebTransport.

tl;dr using WebRTC just for realtime client<->server data sucks, but WebTransport[1] is coming soon to serve that exact usecase with an easy API

WebRTC has data channels, which are currently the only way to achieve unreliable and unordered real-time communication (UDP-style) between the browser and other browsers or a server. This is pretty essential for any networked application where latency is critical, like voice and video and fast-paced multiplayer games.

As other commenters have noted, it's a royal pain in the ass to set up WebRTC if all you want is UDP-style communication between a server and browser, since you need to wrangle half a dozen other protocols in the process.

However! A new API, WebTransport[1], is actively being developed that will offer a WebSockets-like (read: super simple to set up) API for UDP-style communication. I am extremely excited about it and its potential for real-time browser-based multiplayer games (which I'm working on).

https://github.com/w3c/webtransport

I did some traveling around the western US in late 2022 to take stock of where my life was and where I was going. During that time I decided that I would go all-in with my coding education, and committed to learning the remaining material listed on those bootcamp syllabi that I had not yet studied – namely, connecting the pieces of the MERN stack; learning about automated testing and data structures & algorithms; and studying development paradigms & methodologies like Agile, Scrum & Kanban, and OOP design patterns & principles – as well as continue to develop my programming fundamentals on platforms like Leetcode and Codewars.

My first encounter with regular expressions was in a solution for a coding problem on Codewars, specifically Count the smiley faces! Which asks you to count the number of smiley faces in a given array but the catch is each smiley can have 1 of 2 kinds of eyes (: or ;), may or may not have a nose represented by 1 of 2 symbols (- or ~), and 1 of 2 symbols (D or ) ) for the smile. In total there are 12 different combinations that are a valid smiley. I, being the young and naive programmer I was, hard coded all 12 of those faces and checked every element against that list. And it worked! But the top solution included some strange syntax that I had never seen before

Embrace Challenges: Challenge yourself with platforms like Exercism and Codewars that offer a wide range of coding challenges of varying difficulty levels. Additionally, consider exploring niche topics through courses on platforms like Coursera and edX.

@OP DO NOT go on the path of perfecting it and parting with your time and money. Go with Jake Vanderplas's whirlwind tour of python whirlwind tour of python to get some basics and then jump into the river codewars and swim upstream daily and religiously until you reach to katas level 5. You will be good to go. My personal experience.

Codewars: Codewars

You can try Codewars, they have a diverse range of practice problems(Cryptography, Data Science, etc.). Basically if you wanna get good in a programming language, you have to work on a lot of projects and practice problems.

Codewars is a good platform. Here you can practice code kata's daily in your preferred programming language. Link: https://www.codewars.com/

If you're looking for something that is closer to a combat style game you could try https://www.codewars.com/