ld-find-code-refs VS samples

Taplytics is a broad A/B testing platform for marketing teams. While DevCycle is a feature flagging tool built for developers. Taplytics actually has feature flagging, but DevCycle is much more focused and plans to compete directly with incumbents like LaunchDarkly by building a better developer experience (more on how later). But with Taplytics they built so many features and every customer was using them in a different way that it became hard for such a small team to maintain. Meanwhile, feature flagging is a much narrower problem where most customers will have similar use cases. In addition, Taplytics required lots of face-to-face time selling to executives, while DevCycle is more of a bottoms-up, self-serve sales process. Finally, we didn't cover it in the interview but feature flagging is a huge market. LaunchDarkly was valued at $3billion in 2021.

I had a custom rule added to Little Snitch that blocked the following domains: launchdarkly.com, clientstream.launchdarkly.com, mobile.launchdarkly.com

10. LaunchDarkly

There are however Saas to implement directly a feature management system. Several solutions exist like LaunchDarkly, Flagsmith or Unleash.io. Using a SaaS (Software as a Service) feature flagging solution offers the advantage of a faster and more straightforward implementation process. These services are readily available and can be quickly integrated into your project.

Currently, there are numerous feature flag systems available. Options include our own company's open-source system, "Bucketeer", and the renowned SaaS "LaunchDarkly" among others. When comparing these, the following considerations might come into play:

A variety of tools can cover some of these use cases. PLG tools like Segment and journy.io can track activity. Maybe you use a feature flag service such as LaunchDarkly. Stripe or Chargebee might manage some of the billing-related aspects. Meanwhile, problems related to authentication might be visible in your Auth0 account. However, it’s unlikely that you’re using all these platforms. Even if you are, you probably can’t cover some use cases.

If you have not used it and wonder what I am talking about: https://launchdarkly.com/.

I record video from a webcam using MediaRecorder 100ms segments in the way described here. When the piece is ready, I send it using socket.io to the server (on a node.js 6.3.0 server). The server writes this piece to the database and gives it to everyone else on the socket. It is known for sure that the correct data is coming to the server, I can save any piece and start the video (then I glue them together and get the recording). The problem is that when the data is returned back to the client, it is invalid.

Thank you so far :) the "complex data processing" is a webpacked DSP hardware simulator, which has to exist in the global scope as it manipulates the DOM and cannot re-instantiate within the AudioWorkletGlobalScope. I have found this, which uses MediaStreamTrackProcessor, MediaStreamTrackGenerator and TransformStream to expose the microphone samples to the global scope and then "cheats" by sending them to an audio HTML component instead of directly to the audiocontext destination, mimicing actual realtime processing. This is what I was looking for, however:

WebRTC: https://webrtc.github.io/samples/

Demos are often snapshots in time, created to showcase an aspect of technology. They are typically small, self-contained, and single-purpose. Demonstrative projects can range from the practical stress-testing of a particular feature to creative, wacky ways to use them. Examples include WebRTC samples and the Dependabot Demo.

This repo includes all the tutorials that are on https://webrtc.github.io/samples/. The aim of the project is to convert all the sample code to a Svelte app.

Maybe you can identify which part of WebRTC is failing using some test webpages like https://webrtc.github.io/samples/

Here's a few samples. The video chat example will be very useful to you.