Good point. You'd need at least 215 bits to represent all measurably distinct times (in multiples of the Planck time, approximately 10^-43 seconds) out to the projected heat death of the universe at 100 trillion (10^14) years. That should be sufficient for even the most detailed and lengthy simulation.
nybble41
joined 2 years ago
Why does bi-weekly mean "every two weeks?" This has always bothered me because intuitively it should mean "twice a week."
Why does bi-weekly mean "every two weeks?" This has always bothered me because intuitively it should mean "twice a week."
bi- means two, as in bicycle: two wheels (circles)
semi- means half, as in semicircle: half of a circle
The problem is that the prefixes can be parsed as affecting either duration/interval as in (bi-week)ly, every two weeks, or frequency as in bi-(weekly), two times weekly. The same applies to semi-.
Personally I find the frequency interpretation a bit of a stretch—"two" is not the same as "two times" or "twice"—so I would tend to read e.g. bimonthly as every two months rather than twice each month.
The fact that you've made it impossible to roll an 8 by replacing 2d4 with 1d6+1 might impact the game just a bit. Also with 2d4 a 5 is 4x as likely (1+4, 2+3, 3+2, 4+1) as a 2 (1+1) or 8 (4+4); with 1d6+1 all outcomes from 2 to 7 are equally likely, so you're far more likely to get a critical hit or critical miss (if the game has that sort of thing, and you adjust it for the reduced range).
If you want one-second resolution, sure. If you want nanoseconds a 64-bit signed integer only gets you 292 years. With 128-bit integers you can get a range of over 5 billion years at zeptosecond (10^-21 second) resolution, which should be good enough for anyone. Because who doesn't need to precisely distinguish times one zeptosecond apart five billion years from now‽
It might be more accurate to say that Unix time is the number of days since Jan 1st, 1970, scaled by 24×60×60. Though it gets a bit odd around the actual leap second since they aren't spread over the whole day. (In some ways that would be a more reasonable way to handle it; rather than repeating a second at midnight, just make all the seconds slightly longer that day.)
Cx File Explorer supports SMB, FTP, SFTP, and WebDAV remotes out of the box. There is an option to browse the local network.
It's similar, but JavaScript would use : and , for separators rather than = and ;.
This is valid Lua table syntax, however. A program creates an embedded Lua environment with an item callback function and runs this file inside it. Something similar could be done to convert it to another format; just define item to output the data as JSON, or whatever other format you prefer.
The Prosody XMPP server, written in Lua, generates files of this type when serializing lists with the "internal" storage manager. See functions list_store and list_load in util/datamanager.lua.
I believe the point was that it didn't fit the setting for the main characters of a typical fantasy plot—not being well-suited to traveling significant distances in rough terrain, among other things—not that they wouldn't have the basic tech. You don't see many active-duty soldiers or mercenaries fighting in wheelchairs and it seems likely the same considerations would apply to adventurers. You can come up with settings where it isn't totally implausible, but it will require some careful thought and ingenuity.
Cx File Explorer has a similar feature, along with a built-in FTP client. Another option would be to run an SSH server like SimpleSSHD on the device you want to share files from so you can access them via SFTP, which Cx File Explorer also supports. This permits more secure public key-based authentication rather than just a password.
bi-sect: cut into two parts; from Latin "bi-", two, and "secare", to cut.
The "sect" part is critical. "bi-" on its own doesn't imply division.