Hacker News Reader

lyang2821on Audioscrape: Building in Rust When Everyone Said I Shouldn't

For frontend in Rust, there're Yew, Sycamore, Dioxus and Leptos to choose from. Leptos fits me the best in terms of DX.

lyang2821on Audioscrape: Building in Rust When Everyone Said I Shouldn't

I bootstrapped Lapdev (https://lap.dev/) all in Rust too. Axum for the backend and Leptos for the frontend. Sharing structs between backend and frontend is quite nice.

Besides the memory safety, type system etc, Rust gives you the confidence that you know it can scale in pretty much all scenarios in terms of performance.

lyang2821on Show HN: Lapdev, a new open-source remote dev environment management software

A few things Lapdev can probably do better:

Devcontainer spec is probably more developer centric than Proxmox templates

I would guess with your Proxmox setup in a team setup, you'd need to assign a hostname/ip for different developers, where with Lapdev you have a single point of access.

Lapdev can proxy http traffic to the workspace containers with authentication, which makes it easy to preview things with security.

lyang2821on Show HN: Lapdev, a new open-source remote dev environment management software

Yes that's correct.

To start with, I would suggest you to try VSCode Remote out with your own Linux box if you've got one, just to get a feel of "remote" development. You might like it or might not.

lyang2821on Show HN: Lapdev, a new open-source remote dev environment management software

Hi, Lapdev dev here. Let me try to answer your question.

It's installed on a remote server so it provides remote environments. If you use VSCode remote, then you can "open" it through VSCode remote ssh.

The environment that Lapdev provides essentially is a container (other format is on the roadmap) with things pre-installed as defined in Devcontainer(https://containers.dev/) format.