dark VS devtools

Yes. Darklang was originally in OCaml using js_of_ocaml, and we ported it to F# using Blazor (https://github.com/darklang/dark/tree/main/backend/src/Wasm). It works.

We found that in dotnet 6, the code was much slower, with long startup times and a much bigger download, than in js_of_ocaml. It also had a lot of issues in running in a Webworker, which wasn't the case for js_of_ocaml.

In dotnet 7, the webworker issues are better and AOT is easier, so startup is faster. Download sizes are still bad, and it's still slower than js_of_ocaml.

However, dotnet allows almost any code to run in WASM, which js_of_ocaml had large limitations. This meant a decent chunk of functionality had to be worked around to make separate js vs native targets, which also was a massive pain and took a long time. Dune's virtual targets wasn't ready at the time - I think we were one of the test cases for it.

Why should I use this instead of https://darklang.com/

First it was probably Dark. They made a lot of noise some years ago, but then I never heard of them again (looking at their current website, looks like they moved on to AI now, obviously).

Reminds me of Darklang. Personally, I don't think vendoring cloud services into a language is going to be beneficial. I'm curious how the language deals with vendor updates. Do I have to upgrade the language then? If so, I see a lot conflicts coming from this. Then it comes down to Javascript or HCL, the HCL bit makes me think that the below statement is not as truthy as it is on the surface:

We still don't have all that many users (~100 active), so I'm not sure you'll find an answer here. But we collect that sort of feedback publicly, which might answer your question: https://github.com/darklang/dark/discussions/categories/feed...

I wish I could remember what took me to YCombinator's website on the 10th of October, 2022. That was when I first heard about Wasp and another language called DarkLang. After I learned about Wasp, I was intrigued and curious to know how it works, which led me to join the discord server the next day.

Some languages that try to integrate an HTTP server and a database:

Ur/Web: http://impredicative.com/ur/

Dark (Darklang): https://darklang.com/

There are others in this space I did not assess like Encore, Shuttle, Modal, and Dark. These were not assessed for the sake of time. If you're interested in IfC, I encourage you to take a look at these others.

Oh, finally! I was waiting to build my serverless CRUD webapp in Dark (OCaml + JavaScript and Fsharp?) until they had support for returning negative numbers on a GET request!

Not at this time. I'm pretty full up at this point with day job ( https://replay.io ), conferences, and personal life stuff.

My current ongoing Redux maintenance task is trying to revamp our "Redux Essentials" tutorial to be TS-first. Making slower progress on that than I'd wanted, but hopefully can get that wrapped up in the not _too_ distant future.

Beyond that, we've got a ton of open RTK Query feature requests that I'd like to address later on this year.

Exactly - that's what we've already built for web development at https://replay.io :)

I did a "Learn with Jason" show discussion that covered the concepts of Replay, how to use it, and how it works:

- https://www.learnwithjason.dev/travel-through-time-to-debug-...

Not only is the debugger itself time-traveling, but those time-travel capabilities are exposed by our backend API:

- https://static.replay.io/protocol/

Our entire debugging frontend is built on that API. We've also started to build new advanced features that leverage that API in unique ways, like our React and Redux DevTools integration and "Jump to Code" feature:

- https://blog.replay.io/how-we-rebuilt-react-devtools-with-re...

- https://blog.isquaredsoftware.com/2023/10/presentations-reac...

- https://github.com/Replayio/Protocol-Examples

Replay's founders originally worked as engineers on the Firefox DevTools (and in fact our debugger client UI started as a fork of the FF Devtools codebase, although at this point we've rewritten basically every single feature over the last year and a half). So, the original Replay implementation started as a feature built into Firefox, and thus the current Replay recording browser you'd download has been our fork of Firefox with all the recording capabilities built in.

But, Chromium is the dominant browser today. It's what consumers use, it's devs use for daily development, and it's what testing tools like Cypress and Playwright default to running your tests in. So, we're in the process of getting our Chromium fork up to parity with Firefox.

Currently, our Chromium for Linux fork is fully stable in terms of actual recording capability, and we use it extensively for recording E2E tests for ourselves and for customers. (in fact, if you want to, all the E2E recordings for our own PRs are public - you could pop open any of the recordings from this PR I merged yesterday [0] and debug how the tests ran in CI.)

But, our Chromium fork does not yet have the UI in place to let a user manually log in and hit "Record" themselves, the way the Firefox fork does. It actually automatically records each tab you open, saves the recordings locally, and then you use our CLI tool to upload them to your account. We're actually working on this "Record" button _right now_ and hope to have that available in the next few weeks.

Meanwhile, our Chrome for Mac and Windows forks are in early alpha, and the runtime team is focusing on stability and performance.

Our goal is to get the manual recording capabilities in place ASAP so we can switch over and make Chromium the default browser you'd download to make recordings as an individual developer. It's already the default for configuring E2E test setups to record replays, since the interactive UI piece isn't necessary there.

Also, many of the new time-travel-powered features that we're building rely on capabilities exposed by our Chromium fork, which the Firefox fork doesn't have. That includes the improved React DevTools support I've built over the last year, which relies on our time-travel backend API to extract React component tree data, and then does post-processing to enable nifty things like sourcemapping original component names even if you recorded a production app. I did a talk just a couple weeks ago at React Advanced about how I built that feature [1]. Meanwhile, my teammate Brian Vaughn, who was formerly on the React core team and built most of the current React DevTools browser extension UI, has just rebuilt our React DevTools UI components and started to integrate time-travel capabilities. He just got a working example of highlighting which props/hooks/state changed for a selected component, and we've got some other neat features like jumping between each time a component rendered coming soon. All that relies on data extracted from Chromium-based recordings.

[0] https://github.com/replayio/devtools/pull/9885#issuecomment-...

[1] https://blog.isquaredsoftware.com/2023/10/presentations-reac...

I made a Replay recording of the sandbox:

Hiya folks! In addition to all my free time spent working on Redux, answering questions, and modding this sub, my day job is working on Replay.io. Today we're thrilled to announce our new Replay for Test Suites feature, which lets you record and time-travel debug Cypress (and Playwright) E2E tests as they ran in CI!

FWIW, the Firefox devs who were doing the WebReplay time travel debugging POC weren't, as far as I know, fired. Instead, they left and started Replay ( https://replay.io ), a true time-traveling debugger for JavaScript.

I joined Replay as a senior front-end dev a year ago. It's real, it works, we're building it, and it's genuinely life-changing as a developer :)

Not sure how well this would have fit into Firefox as a specific feature, given both the browser C++ runtime customizations and cloud wizardry needed to make this work. But kinda like Rust, it's a thing that spun out of Mozilla and has taken on a life of its own.

Obligatory sales pitch while I'm writing this:

The basic idea of Replay: Use our special browser to make a recording of your app, load the recording in our debugger, and you can pause at any point in the recording. In fact, you can add print statements to any line of code, and it will show you what it would have printed _every time that line of code ran_!

From there, you can jump to any of those print statement hits, and do typical step debugging and inspection of variables. So, it's the best of both worlds - you can use print statements and step debugging, together, at any point in time in the recording.

See https://replay.io/record-bugs for the getting started steps to use Replay, or drop by our Discord at https://replay.io/discord and ask questions.

I also recently did a Learn with Jason show episode based on this, where we went through many of the same topics, and also looked at the Replay.io time-traveling debugger that I build as my day job:

My day job is working at a company called Replay ( https://replay.io ), and we're building a true "time traveling debugger" for JS. Our app is meant to help simplify debugging scenarios by making it easy to record, reproduce and investigate your code.

I currently work for Replay.io, where we're building a true time-travel debugger for JS apps. If you haven't seen it, check it out - it makes debugging so much easier, and I've solved many bugs that would have been impossible otherwise