meal-scheduler VS electron-browser-shell

I use Minizinc in a personal toy project (https://gitlab.com/dustin-space/meal-scheduler), and GECODE or Google's ortools solver at the backend. It's used for meal planning. Unfortunately it's way way slower than I'd hope. I suspect I just have the domain not modeled efficiently. Maybe if I had a few days to put into it, and learn how to properly debug the CSP solver step by step, it might help...

That sounds like a fun application, both the usage and the implementation.

I wonder if you have any interesting example data-files that could be used with the model, preferable both something small and something larger? Would be fun to test the model locally to see how it behaves.

Notes: I'm assuming here that https://gitlab.com/dustin-space/meal-scheduler/-/blob/master... is the model used.

Tired of walled gardens and increased limitations of Chrome extensions, I'm building enough of the web extensions API to let me run them in my own desktop browser. Eventually I plan to build products from this project.

https://github.com/samuelmaddock/electron-browser-shell

Chrome extension support for Electron-based web browsers: https://github.com/samuelmaddock/electron-browser-shell

Despite a fair amount of folks disliking Electron for replacing traditional desktop apps, I find it's a great fit for building unique web browsers.

I believe there's a lot of opportunity for making interesting web browsers, but building and maintaining them by forking something like Chromium or Firefox is a ton of work.

With Electron, it's possible to create something interesting with a team of one.