vim-sendtowindow VS Pion WebRTC

I have been using https://github.com/karoliskoncevicius/vim-sendtowindow

I use R with Vim. Usually the R script file is open on top and there is a :terminal window with R running below. And I use a small vim-plugin [1] for sending commands from the editor to the REPL.

This has a few advantages, major being that you can run any language with a dynamic REPL this way, without changing your setup. Or, you can even have two files, written in two different languages, open side by side with a corresponding REPLs running beneath each of them. The downside of course is that you miss on auto-completion and other integrations like that. These are not impossible, but you would have to torture your Vim setup quite a bit in order to implement them.

[1]: https://github.com/karoliskoncevicius/vim-sendtowindow

I often have to perform statistical tests on genomic data. Which in practice means running the same test on every gene (row of a matrix). Running it separately on each row is often slow, specially in R. So to speed it up I started an R package "matrixTests": https://github.com/karoliskoncevicius/matrixTests which is a lot faster and deals nicely with edge case scenarios (missing values, infinities, empty matrices, etc).

Another notable mention is maybe vim plugin "sendtowindow": https://github.com/karoliskoncevicius/vim-sendtowindow which implements an operator for sending text to another window. Handy for sending code in a REPL within vim ":terminal" buffer.

I am really excited about https://github.com/sepfy/libpeer. It has examples ready for ESP32 etc....

When working on KVS I wasn't familiar with the embedded space at all. I saw 'heavyweight' embedded where you were running on Linux. Then you had RTOS/No OS at all. I wasn't prepared for these devices at all. If we can make WebRTC work in the embedded space I think it will really accelerate what developers are able to build!

Remotely driven cars, security cameras, robots in hospitals that bring iPads to infectious patients etc... Creative people are building amazing things. The WebRTC/video space needs to work harder and support them :)

-----

I love how diverse the WebRTC space is now. Outside of this implementation you have plenty of other options!

* https://github.com/shinyoshiaki/werift-webrtc (Typescript)

* https://github.com/pion/webrtc (Golang)

* https://github.com/webrtc-rs/webrtc (Rust)

* https://github.com/algesten/str0m (Rust)

* hhttps://github.com/sepfy/libpeer (C/Embedded)

* https://webrtc.googlesource.com/src/ (C++)

* https://github.com/sipsorcery-org/sipsorcery (C#)

* https://github.com/paullouisageneau/libdatachannel (C++)

* https://github.com/elixir-webrtc (Elixir)

* https://github.com/aiortc/aiortc (Python)

* GStreamer’s webrtcbin (C)

See https://github.com/sipsorcery/webrtc-echoes for examples of some running against each other.

I have worked four jobs related to https://github.com/pion/webrtc and one for https://webrtcforthecurious.com

Two companies used Pion. The other two were just using the protocol (WebRTC)

In my experience Go has been relatively approachable for people that are good at PHP. It has a great standard library and a pretty solid ecosystem, though frameworks aren’t as popular in Go. There are some well regarded libraries for things like WebRTC via https://github.com/pion/webrtc WebSicket via https://github.com/nhooyr/websocket

Don't try to make RTC yourself, it looks easy, but in fact, it's a really hard problem to solve. Use https://pion.ly/ it's a pretty solid package they also have a discord/slack channel with a lot of helpful people there.

Maybe you can reuse some of this code: https://github.com/pion/webrtc/blob/master/examples/data-channels/main.go