gitarena VS probe-rs

GitArena - https://github.com/mellowagain/gitarena

GitArena is a GitHub/Gitea/GitLab clone written in Async Rust using Tokio and Actix-Web on the backend and server-rendered HTML with htmx for interactivity.

I commented on the "Who wants to be hired?" thread of this month with this being my main portfolio show-off project. It worked and I have gotten already 2 job offers now.

Hello! I'm Mari. I'm a self-taught software developer and have spent the past 10 years programming in my free time, mostly working on my own projects and contributing to open-source. I am currently working in retail and looking for a job as a software engineer in order to turn my passion into a living and getting a foothold in the industry.

My latest and greatest project I've recently been building is GitArena (https://github.com/mellowagain/gitarena), a software development platform similiar to the likes of GitHub, GitLab and Gitea. It features built-in vcs on top of Git and issue tracking, mostly focused on being able to be self hosted. It is written in Async Rust using Actix-Web running on the Tokio async runtime and PostgreSQL as persistent database. On the frontend it uses server rendered HTML with interactivity built in Vanilla JS and htmx. It also uses Semantic UI for CSS styling.

Thanks to my existing experience in retail, I'm very good at analyzing customer needs and can thus work efficiently on building and shipping customer-orientated solutions. I'm looking to take advantage of this in my future career.

Feel free to get in touch to learn more about me and my previous experiences.

Want debugging capabilities with anything with an am st link/jtag/other compatible probe? https://probe.rs/

/uj The SVG usage looks to be in a visualisation helper. Maybe ought to be a separate module, but I've seen worse.

There is a command to list supported chips for *flashing* in all our CLI tools. Furthermore https://github.com/probe-rs/probe-rs/tree/master/probe-rs/targets contains all targets for which we support *flashing*.

Under the hood, cargo-embed, knurling's probe-run, and Humility are all built atop probe-rs (https://probe.rs/) to provide debugging - I think in this case it's actually a great example of cooperation between projects! Probe-rs has received PRs from both Knurling and Oxide devs; it provides the common interface to use various types of debug hardware and talk to various types of microcontroller cores, essentially replacing OpenOCD.

Ryzen 3700X, 3200Mhz DDR4 tower builds http://probe.rs in 1m47s with fans fully spinning. M1 Pro: zero noise, 1m21s. Ryzen 3950X is on par with the M1 Pro. Actual speed difference will very much depend on your actual workload. Compiling for aarch64 apparently is more efficient than for amd64. Which is why compiling for you locally gives much more speed benefit than some generic benchmarks would indicate :) Also, you cannot forget that I can easily work for 10hrs on my MBP M1 Pro with rust-analyzer and frequent compiles running. You can forget that with any other suggested "on par" notebook. They will drain your battery instantly. Also, with the same thermal mass, other laptop builds will go into throttling much faster, which will lead to slower effective speed. XPS laptops and old macbooks know this issue very well :)

Anyone who fancies doing some coding for fun should have a go at an embedded project using rust's tools. Not just embassy, but the PACs, the HALs, probe-rs (probe-rs is bonkers good), and the community on matrix. My bet is on rust embedded seeing huge growth in the next few years.

probe-rs (embedded debugging toolkit for ARM and RISC-V which is supposed to be used in place of the above if you code with it as it aims to fully replace the GDB portion of the stack for Rust embedded development)

cargo install --git https://github.com/probe-rs/probe-rs probe-rs-debugger