| 00:38 | <MikeSmith> | jgraham: transpiler outputs source code, not object code, right? |
| 00:39 | <MikeSmith> | Mateon1: sounds like Swift |
| 00:40 | <MikeSmith> | from what little I remember hearing about stuff that swift has |
| 00:43 | <MikeSmith> | the benefit in practice of Optional is mainly preventing NPEs, right? |
| 00:43 | <MikeSmith> | (I'm asking) |
| 00:44 | MikeSmith | decides to read up some |
| 00:48 | <MikeSmith> | ... or avoiding segfaults or whatever consequence is |
| 01:40 | <MikeSmith> | anybody have opinions on what HTTP client library is best practice to use in Java code these days? |
| 01:41 | <MikeSmith> | context is https://github.com/validator/validator/issues/61 |
| 01:42 | MikeSmith | wonders about https://developers.google.com/api-client-library/java/google-http-java-client/setup but the fact that page causes a mixed-content warning doesn't inspire huge confidence |
| 01:44 | <MikeSmith> | oh anyway that's not a general-purpose libary ("provides simple, flexible, access to Google APIs for Java client applications") |
| 09:43 | <jgraham> | MikeSmith: If you like. But early C++ compilers ouput C code and invoked an existing C compiler on that. The modern Nim compiler, for example, does the same thing. Other compilers like GHC have options to output C or JS code rather than object files. So it seems to me to be an arbitary distinction that doesn't really capture the most interesting part of what a compiler does. |
| 09:51 | <terinjokes> | Domenic: what archive formats? |
| 10:27 | <Domenic> | terinjokes: https://w3ctag.github.io/packaging-on-the-web/ |
| 11:17 | <roc> | jgraham: indeed |
| 11:18 | <roc> | Mateon1: JS Typed Objects give you some of what you want. |
| 12:53 | <The-Compiler> | So it seems foo::bar would be a valid URL, right? I'm writing a browser and wonder if I should always treat foo::bar as a searchterm (think C++) instead of a link with an explicit scheme - are there any common protocols which use URLs with a :bar path? |
| 16:27 | <terinjokes> | Domenic: i didn't think that went anywhere, since it wasn't very popular at EWS |
| 16:28 | <terinjokes> | I've been shimming this for about 2 years now |
| 17:28 | <jgraham> | I might be very stupid, but I don't see where new Event() initializes the bubbled and cancelable attributes |
| 17:33 | <miketaylr> | jgraham: new Event("plop", {"bubbles":true, "cancelable":false})? |
| 17:34 | <jgraham> | miketaylr: I mean if you do new Event() with no arguments, per the spec |
| 17:34 | <miketaylr> | ah |
| 17:35 | <miketaylr> | it looks like, both as false? |
| 17:35 | <miketaylr> | in the IDL https://dom.spec.whatwg.org/#dfnReturnLink-0 |
| 17:35 | <miketaylr> | but i don't see any prose other than that, no |
| 17:36 | <miketaylr> | better link https://dom.spec.whatwg.org/#interface-event |
| 17:40 | <jgraham> | Oh right, that thing there. |
| 17:44 | <Ms2ger> | Yeah, event constructors are defined pretty magically |
| 23:30 | <jsbell> | Heh. encoding/single-byte-decoder.html has "interesting" behavior in Chrome. In the iframe test, Chrome sniffs the byte stream ([0x00, 0x01 ... 0xFF]) - per [[MIMESNIFF]] - and overrides the content type as application/octet-stream and offers to download the file. Or, well, 167 files. :P |
| 23:34 | <jgraham> | Fun :) |