northernskys30

There is better open source availability than 20 years ago, I think, let say JUMP in Julia.

But I would say the culprit as to why mathematical optimization is not hyped and not as open sourced is the fact that to the layman, mathematical optimization is less impressive than say Midjourney or ChatGpt. The solution of a bus route optimization might be impressive to a public transport planner, but it requires domain knowledge.

Also, problems that are solved with mathematical optimization are often big organization problems. Sure you can model, as in this blog post, access to opiod treatment center, but to see the "product", you would have to implement the solution of the LP, aka building the treatment centers, which is unlikely to happen unless you work for the government. With generative ML, you can see something coming out of your code that is not only x1= 1, x2=3, etc.

I meant sexy in the sense of fashionable. People are impressed if you can solve TSP for a few nodes with a NN, but they don`t really care if you can solve for 100k of nodes with good ol' branch-and-cut.

Concerning combinatorial optimization, for what it is worth, I've been working in that field for the last three years! Mainly on public transport optimization algorithms. It is less "sexy" than ML, and paid less, but I find it very interesting work, and quite challenging, as the state of the art constantly evolves.

That would be Knights of the Old Republic 1 for me. The story is really good, and it has the best BIG REVEAL of any game I played. I used to replay it two times every year, one full evil run and one full lawful good.

It compiles to a sort of byte code that is executed by a stack based virtual machine.

I did my CS degree at umontreal and this was an assignment in a second year class. This was a pretty interesting introduction to compilers, and even if this is a toy subset of C, this was challenging, at least for me. We would get 0 if there were any memory leak, so we were pretty paranoid about it.

The second assignment was writing a Scheme interpreter.