204 karma · joined December 31, 2020
(1)[m^4 kg^2 s^-7 A^-2]
Edit: actually, I realize I don't know whether you meant 'macro' in the C sense or the Lisp sense. I was thinking C
Schrödinger's Panacea: measure a problem with sufficient inaccuracy and any arbitrary contribution can be disregarded.
>Hypothetical shape charge liner. High density is a benefit but equally low speed of sound indicate s that it may be no better than uranium. An advantage may be found in its ductility, if it leads to greatly improved jet formation relative to its cost.
It seems that sound speed and density are considered more valuable, so tungsten, zirconium, molybdenum.
I could be wrong about the depth to which her burns penetrated, I can't find where I initially read that.
I offer instead a lesser argument: it is not absurd that a burn penetrate deep enough to affect bone, especially at the pelvis where bone is close to the surface.
I will not link photos, they are indeed horrifying and if you go look for them they are more persuasive than anything I can say
- She was hospitalised for 8 days, suffered burns to her pelvic /bones/, was disabled for 2 years.
- She offered to settle for the cost of her hospital bill, McD refused.
- McD were keeping the coffee at 190°F
zig: no macros plz
nim: macros are amazing
yes, that is the default, but it is also possible to
`from package import nil`
which gives you python's `import package` behaviour or
`from package import symbol`
which is just like python
maybe i just dont have that stack well enough built in my head--if im editing in a plugin-free vim, i do find i have to backtrack and count to make sure i've put the right number of kets at the end of a nested expression.
if i used s-expressiony instead of tab-heavy languages more often i'm sure i'd be better at it.
it makes me tear my hair out for the thing it lacks: a path to a production-worthy version. It encourages bad programming practices for the sake of simplicity (all tabs share a single namespace; global variables everywhere) which all but guarantee that once a sketch has reached a certain level of complexity it's a tangled mess of spaghetti.
Refactoring it at that point is A) challenging, and B) changes the api so much that the poor non-coder who's asked you to fix their broken code hates the new restrictions.
even if you can, surely you're wasting time and/or focus on an automatable task.
But we all have something we do 'the hard way' because it feels like more effort to relearn the task than its worth, or because we tried the easy way once and were put off by some side-effect.
paren highlighting never comes as a single unit, its always packaged with other 'helpful' tools, some subset of which will always be infuriating to someone.