175 karma · joined June 16, 2010
take some classic physical patent like the Bessemer process for steel--given a suitably general collection of industrial robots and reconfigurable equipment, "make steel like this" is "implementable" in software.
or any random machinery patent--"be this specific kind of rotary engine" is software if your hardware is a few trillion nanites.
what exactly the implications are for the patent system, i'm still not sure....
the one relevant to me on a daily basis is zyrtec/xyzal -- xyzal is just zyrtec filtered for the correct chiral form, but the prescription is cheaper than the OTC for me thanks to my insurances' rules.
this is like anthropic reasoning--always true, rarely useful.
> [...]
> Consider linking to your home page and/or site map [...]
For a second I thought you were advocating redirecting 404s to the homepage, and I was about to flame you. I hate that one, and I think it's harmful enough that you probably ought to have a point about not doing it in that article.
Sounds like Freenet USK's (see https://freenetproject.org/understand.html, search for USK (and boo on them for not having any anchors on that page)).
i find this to be an excellent example of (failing at) optimizing for the common case--probably >99% of the interactions people have with microwaves are pure timed-cook-at-100%-power, and requiring an extra button press to enter that mode is silly.
points in time are relative to some fixed point, and are (more or less) dimensionless. durations are not, and are (more or less) vectors. this has a couple consequences: durations are independent of epoch, while points aren't, and only certain types of math make sense with each.
basically, the only thing you can do with two points is subtract them (yielding a duration)--the rest of arithmetic (including addition) is meaningless. the only things you can do with a point and a duration is add or subtract them (yielding a point). you can't do anything at all with a point and a dimensionless scalar. the only things you can do with two durations is add or subtract them (yielding a duration) or divide them (yielding a scalar). the only things you can do with a duration and a scalar is multiply or divide them.
(personally i'd say that even the commutative operations shouldn't necessarily be commutative--i'd say point+duration->point, but duration+point->undefined--but that may be a bit too strict.)
as a quick rule of thumb, if your code would break if you changed epochs, it's already broken.
i just ran a quick test, and for a specific millisecond around now, about 13,000 distinct timestamps have the same string representation. if you use that string representation as a serialization of any one of those timestamps, it will always map back to a single float value, which will be only one of those 13,000, meaning the others aren't round-trippable.
the system implements a comparison tolerance for floating point numbers, but this helps only slightly, as only about 1100 of those 13,000 test as equal to the one you get if you enter it as a string.
the end result is that you can have data printing to the screen that you can't actually find in the system because its string representation doesn't match its internal one due to precision issues.
(the solution is not to use the type--they deprecated it in favor of one based on longs of nanos several years ago.)
zoneinfo's form has the benefit of having a nice, unambiguous way to refer to the various daylight-saving time exceptions (arizona, indiana, hawaii, etc.).
recently i've seen huge timezone lists that basically throw in the kitchen sink--they'll have the entire zoneinfo set, the common american names, miscellaneous other common regional names (euro, australia, etc.) and raw whole-hour offsets as well. makes for a long drop-down to navigate....
"Beware of bugs in the above code; I have only proved it correct, not tried it." - knuth
say what? afaik (speaking as a jew here), it's when the sun goes down. (moonrise, averaged over all time, happens at any point in the 24-hour cycle.)
possibly you're thinking of when (jewish calendar) months start?
<rimshot>
it's a bit like being on hold--i'd far rather hear hold music uninterrupted for five minutes at a time than hear the robot break in every 15 seconds to reassure me that whoever i'm waiting for values my loyalty.
gpsd is probably the project he's working on right now with the most potential for widespread use and importance
forgeplucker http://home.gna.org/forgeplucker/ (oddly not linked at http://www.catb.org/~esr/software.html) is probably the project he's working on right now that's the most interesting (and ironically something i expect RMS would be a huge fan of)
does anyone have any more recommendations for "in-depth general interest" magazines? the classic is the new yorker, and the one i (re)discovered recently (mostly through links from places like HN) is the atlantic monthly.
at the first level, you know enough to be able to look at existing code and have some idea what's going on. (this is me with C++.)
at the second level, you know enough to write new code with real functionality and have some chance of its working. (this is me with C.)
at the third level, you have a fairly thorough understanding of most parts of the language and know idioms, common pitfalls, etc., and can fix other people's code. (this is me with q, and it was me with java seven years ago when i was working in java.)
if you want to extend this, an extra level up could be "hack", where you contribute to the language itself--modify gcc or the python interpreter or whatever. (i aspire to get to this level in q, and i think i'm close.)
not sure how to wedge a fifth level into the system....