174 karma · joined August 5, 2020
Is it about the layout of where the assembly instructions end up, and spacing around them? Or the CPU pipelining working better? Or...?
Sometimes whether a cryptographic protocol relies on collision resistance can be surprisingly nuanced, so it should be phased out for this alone (and as we have better options) but for simple examples (e.g. to make a signed hash of an executable, which is probably equivalent to what you're describing) it's not broken.
One thing I enjoy about fish is that it's not just a shell, but also a modern scripting language alternative to sh/bash. Seems like I would lose this with Murex?
(There's no right or wrong choice for Murex here, just that has to choose one way or another.)
If I recall correctly, they changed how `re.escape` worked between Python 3.6 and 3.8 (I'm not sure which minor change exactly) in terms of which symbols received a backslash before them, thereby breaking my code.
For context, I did a Maths degree, so I'm familiar with them all. I just never find myself needing them.
Some of the VS Code extensions provide some nice added value, such as LLDB debugging for C/C++ and Rust, but you can actually get this in Neovim, you just need to install the extension in VS Code and then point to it from Neovim. If you dig around, you can see this in my dotfiles, linked in another comment. And this is only an issue for debugging compiled code to give nicer variable information for e.g. strings, which is quite specific.
I've also found Microsoft's recent move to Pylance from Pyright has meant a few small things aren't there for Python, which admittedly was disappointed, but again, broadly this isn't an issue at all.
Otherwise, I've not found this issue with Neovim at all.
I suppose it's equivalent here to whether knowing the meaning of a particular sentence in the alien language qualifies as understanding it, vs being able to meaningfully speak about it in this alien language, and use the sentence in a conversation. Seems like just semantics to me.
> I actually wouldn't have figured it out if he hadn't pointed out this is induction.
A lot of these other ones are not that complicated either, it's just hard to parse and sometimes requires a small bit of math knowledge, which I think is within reach if you're familiar with induction and would only take e.g. a minute for you to understand if someone explained it (ideally with a blackboard than in text).
Some of those are definitely nonsense to me. But, to put my money where my mouth is and to give some examples (as you spent the time to type that out), 'invariance under linear combinations' just means that, if something holds for f(x), then it holds for 2f(x), f(x) + 10, etc. (these are all linear combinations). So then saying 'suffices to check basis elements' means 'just check f(x), and the others all fall out for free'.
As another example, convex combinations: Google 'convex hull' for images, but basically this one is just saying just check the 'extreme elements', i.e. the 'corners' at the boundary, and everything in the middle falls out for free because we have 'invariance under convex combinations'. A convex combination here is just a some point in the middle of these extremes.
While these may not be immediately obvious when reading them, the pictures or ideas are actually sometimes quite simple.
I hope that helps.