Regarding mutation testing, you don't write any "tests for your test". Rather, a mutation testing tool automatically modifies ("mutates") your production code to see if the modification will be caught by any of your tests.
That way you can see how well your tests are written and how well-tested parts of your application are in general. Its extremely useful.
You have written tests for your code and now feel safe because your code is tested. But test quality is really hard to measure. The idea seems to be to introduce "vulnerabilities" (whatever that means...) and see if your tests catch them. If they do that's supposed to show that the tests are good and vice versa.
What issues have you had? Ive been using orca for about a year without any issues all. I'm running Mint, both stable and beta branch have been without issues for me.
Appimage doesn't start because it relies on a system package that does exist anymore, dialogs with grey text on grey backgrounds in dark mode, stl repair not included...
Flatpak is in the works but honestly and hope that helps bit I get better prints out of prusaslicer for some reason so not holding my breath or anything.
The image just isn't being built correctly which is more a problem with appimages but the fact it's still broken... Linux is clearly a neglected platform for them.
All the problems I listed have bug reports just nothings happening to fix them.
Libwebkit isn't actually chromium, it uses blink which is a fork of part of webkit. Understandable confusion though because webkit was part of kde, forked by safari, and then used by through chrome variants for a long time.
The rest of this comment is going to necessarily be nerdy Linux internals. sorry.
Unfortunately, I'm pretty sure chromium includes it inside it's binary and does provide or use any webkit libraries.
Orca uses it internally for it's browser so it won't start unless it has access to the library. When you build a Linux app it includes the name of the library which includes the ABI (basically the version). Newer Linux release include a different version.
Appimage is one of the ways you get around this distro problem by including the versions of libraries. That's why they're so big. There are problems with that like how big the apps are stale bundled libraries with security issues but I digress.
Orca hasn't bundled webkit in the appimage and because of another problem/feature of appimage it falls back on the os library. Since new distros have dropped the older obsolete library version orca can't start.
That's a lot but I hope it explains the problem better.
I would like to help but my personal computer doesn't currently have enough memory to compile orca so back to just watching warning people it's a coming problem for them too.
You're four forks deep now
Slic3r to Prusa Slicer to Bamboo's slicer to Orca. It also borrowed a lot of ideas from Super Slicer. Since it's open source, and has been gaining some momentum, it seems to have a decent amount of contributors
Why Orca?
all the features you know and love from things up the tree
a revamped UI
built in tuning tests (temp tower, extrusion multiplier, volumetric flow, pressure advance, etc)
The UI of Prusa slicer is hot garbage though. I started with prusa slicer and moved to orca after a few months. Orca is a much nicer experience, and the built-in test-models (temp towers etc.) are nice.
In find the location and grouping of parameters more intuitive in orca. I always had to look through several tabs to find the parameter I wanted to adjust when I was using prusa, it was never where I thought it should be.
I guess it's not relevant for your setup, but I like rofi because there is a fork that works in Wayland, and it's the only Wayland window switcher I have found that isn't tied to a specific window manager.
github.com
Newest