The real answer here is that configuring HTTPS clients to trust a self-signed cert (or signed by an internal CA) shouldn't be as difficult as it is. I find it extremely annoying that every programming language has it's own idea of where certificates should live instead of just checking the os trust store.
> detailed information about specific retractions is usually confidential and can only be shared with the relevant authors.
Good luck sharing that information with Max Planck. It's amazing how robotically humans can act sometimes. I suppose this could be an AI or automated response, but it's just as likely it's someone following the letter of the law without using any critical thought.
> the right fix is not "handle every malformed case." ... [LLMs] will still attempt to handle now impossible errors.
This is the number one code smell from LLMs and I don't know why they are so obsessed with it. In python, it often comes as `hasattr` checks on types that are defined to have that attribute, in a code base that is fully type-checked.
Why do they do that? Is it from pre-training or re-enforcement? If that latter, can the labs please fix this?
Mostly unrelated, but what is going on with the "I specifically approve section ... of the terms and conditions" when you sign in without an account. Is this a new requirement somewhere?
Other than that, seems interesting! Simulink could always do with a competitor, although I'm always saying Simulink needs a text-based interface. Same signal flow programming model that supports scopes and continues time integrators, just with text instead of drag-and-drop.
> A bad design with a good presentation is doomed eventually. A good design with a bad presentation is doomed immediately.
- Akin's 20th law of spacecraft design
I always really enjoyed making a slick presentation. It was a lot of fun figuring out how to scope the hardest problem you are sure you can finish in 24hr while still having time to polish your presentation and make the app look good. I find picking a problem that lets you put a big map on the screen helps with the latter.
It will be fascinating to see the facts of this case, but if it is proven their algorithms are discriminatory, even by accident, I hope workday is held accountable. Making sure your AI doesn't violate obvious discrimination laws should be basic engineering practice, and the courts should help remind people of that.
No, I'm not super certain, but I believe most solvers are trained to be game theory optimal (GTO), which means they assume every other player is also playing GTO. This means there is no strategy which beats them in the long run, but they may not be playing the absolute best strategy.
I wouldn't be so sure that writing those toolboxes is cheap. You need an aerospace engineer to write the aero toolbox, or you are going to miss subtleties. I assume you need a biologist to write the biology toolboxes. All of these domain experts are really expensive, and I would not trust a toolbox that hadn't been review by them.
It doesn't seem to be the example here, but I know that X.transpose() does not work if X is a (3,) and not a (3,1), which is the common way to present vectors in numpy. MATLAB forcing everything to be at least rank-2 solves a bunch of these headaches.
Interesting... I wrote a similar post about MATLAB's syntax a while ago, and I still think MATLAB is one of the best calculators on the market.
RunMat is an interesting idea, but a lot of MATLAB's utility comes from the toolboxes, and unless RunMat supports every single toolbox I need, I'm going to be reaching for that expensive MATLAB license over and over again.
Yah, it is very strange to equivocate using AI as a spell checker and a whole AI written article. Being charitable, they meant asking the AI re-write your whole post, rather than just using it to suggest comma placement, but as written the article seems to suggest a blog post with grammar errors is more Human™ than one without.