In a black hole though … who knows
195 karma · joined June 30, 2015
In a black hole though … who knows
[1] https://www.science.org/doi/10.1126/sciadv.aau9824 [2] https://www.science.org/action/downloadSupplement?doi=10.112...
[1] https://www.usgs.gov/media/audio/shaking-and-tweeting-usgs-t...
[1] Nima Arkani-Hamed - The End of Spacetime (Sep 2022) https://www.youtube.com/watch?v=GL77oOnrPzY
So python:
a = [0,1,2,3,4,5]
a[0:5] => [0,1,2,3,4] - half closed interval
a[0:-1] => [0,1,2,3,4] - negative indexing
a[:5] => [0,1,2,3,4] - skipping start index
a[3:] => [3,4,5] - skipping end index
nim: var a = [0,1,2,3,4,5]
a[0..5] = [0,1,2,3,4,5] - closed interval
a[0..^1] = [0,1,2,3,4,5] - closed interval with negative indexing
a[..4] = [0,1,2,3,4] - skipping start index
a[..<5] - Error - doesn't work
a[3..] - Error - doesn't work
a[0..<5] = [0,1,2,3,4] - half closed interval
a[0..< ^1] = [0,1,2,3,4] - half closed interval with negative indexing
(Important - the white space is required, it will crash otherwise!)
I'm sure that there are good reasons for this behaviour and that if you use nim a lot, you just get used to it but I find the python syntax just nicer. "\e[A": history-search-backward
"\e[B": history-search-forward
"\e[C": forward-char
"\e[D": backward-char[1] https://physicsworld.com/a/is-photosynthesis-quantum-ish/
"Because he tasks me! He tasks me! 'round the moons of Snivia, I chuckle at thee. Beyond the Corpian clouds I chuckle more at thee. Revenge is a dish best served with pinto beans and muffins! Kirk, old friend, I... Oh, sorry. [He fixes his tie.] Good-bye."
If it is stricter, it would have one type of field separator that is not commas since some locales use them as decimal places (I'm looking at you, France) but something like '|'. It would insist that dates were iso8601. It could define how fields can be escaped and quoted - although I would prefer if quoting was kept to a minimum. The format should also allow for comments i.e # so that people can comment their datasets inside the same file.
Alternatively or in addition, it could have some header lines:
1) A header that defines the encoding, separator, decimal separator, quote character, escape character, line ending character, date format ...
2) A header that defines each column's name
3) A header that defines each column's data type and formatting
4) A header that defines each column's unit like m/s or kg - ok, this is a bit of a stretch but it would be great to have.
or some variation of the above.
Fundamentally, this bsv format would still be csv and most programs would still be able to read it with the parsers that already exist or be quickly adapted to read it. It could still be easily edited by hand but the metadata would be present.
I suspect that this is just a pipe dream because people would find hundreds of ways to break it but toml took off and that didn't exist so long ago.
I live in France and the radiators have a control pin that accepts various 230V AC waveforms (!) to set different functions but luckily simply on/off can be used to toggle between the radiators' high and low temperatures (that I set via each radiator's internal interface). It's crude but effective. I use an app to control the remote switches; I'm not totally happy about relying on a cloud based app but I can always bypass the remote control locally if there's an issue and in summer the radiators' are simply switched off so the risks are minimal.