mockoon VS dioxus

Mockoon - Used as a logging server instead of using print in the console.

Hopefully, 2024 is the year I can stop freelancing and live the dream! Work on an open-source project I love while not feeling guilty about not bringing enough money home :D

--> https://mockoon.com

The project I'm working on is https://mockoon.com

Mockoon- Mockoon is the easiest and quickest way to design and run mock REST APIs.

Startup Name / URL: Mockoon (https://mockoon.com)

If you are looking for something with a GUI, I made https://mockoon.com It's open source, supports Faker.js and has a CLI to run the mocks in your CI env (or elsewhere).

I maintain an open-source app built with Electron. It serves tens of thousands of users every months and nobody complained in 5 years that it is being built with Electron. Not saying that Electron is perfect, and that it couldn't be a bit more performant, but as a solo maintainer (and entrepreneur) it helps me ship something that save people time. The burden of maintaining an application is already huge. Having to juggle with multiple environments would be a hassle and I definitely wouldn't do it.

That being said, if a "drop-in" alternative would be available I would probably try to switch at one point. But the alternative would have to be on par with the ecosystem (including packaging, binaries signing, etc.), the community, the ease of use... I don't think there is such a thing yet.

The app, if you are interested: https://mockoon.com

Company: https://mockoon.com

I recommend Mockoon https://mockoon.com/ it’s simple like Postman without create mock api server with code

This may not be what you're looking for, but have you seen Mockoon?

Dioxus Labs (http://dioxuslabs.com) | Founding Rust Engineer | San Francisco | in-person | Full-time | 125-150k | 0.5-3% equity

I'm Jonathan, the creator of Dioxus (YC S23). Dioxus is a popular crossplatform GUI library for Rust that, imo, is the easiest way to ship apps that are beautiful, fast, and robust.

Dioxus is quite popular, almost 20k stars on GitHub, and we recently raised a sizable seed round from "top vcs." We have a lot of exciting projects on the horizon:

- in-place binary patching for rust hotreloading (http://github.com/jkelleyrtp/ipbp)

- a WGPU powered HTML/CSS renderer (http://github.com/dioxusLabs/blitz)

- experiments with LLM-based component generation (http://github.com/dioxusLabs/dioxus-ai)

- upcoming mobile tooling

- TUI-based devtools for a ruby-on-rail like experience

- a deploy platform for web/desktop/mobile/backend and all the fun that entails...

I'm looking for a founding systems engineer passionate about Rust, WASM, apps, the web, compilers, linkers, and devex - basically someone who's not afraid of anything. Dioxus is a very lean organization and we've been able to move so quickly since we keep our team small and high trust. No annoying standups or corporate bureaucracy. If you want to contribute to OSS, move the needle, and work in a startup that's closer to deeptech with hard problems, this role is for you.

I'm specifically looking for people who are excited by this space and doing this type of work. If you're just looking for a job then this probably isn't the right role for you.

Apply on our yc page or are reach me directly at jon at dioxuslabs dot com

https://www.ycombinator.com/companies/dioxus-labs/jobs/dRPOo...

We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f...

Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys

I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.

While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.

You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).