1,604 karma · joined August 8, 2017
But most users are probably disappointed and expected more from it, so I understand why they weren't able to continue that line
The interesting part of the article to me is: okay, now that we have a better compression option, how do we deploy it to an existing ecosystem? And suddenly we're looking at a 4 year migration path!
No easy win at all.
That's also the notation `ip` on Linux supports
Fortunately PG is very good at keeping the documentation structure the same between major versions and provides crosslinks to the proper documentation for all PG versions on (almost?) all pages
\u0000 works fine with firefox with the proper syntax
JSON.parse(`"\\u0000"`)
"\u0000"
and jq supports it too printf '{"null":"\u0000"}' | jq
{
"null": "\u0000"
} echo '<zero>�</zero>' | xmllint -
-:1: parser error : xmlParseCharRef: invalid xmlChar value 0
<zero>�</zero>
^
printf '<?xml version="1.0" encoding="utf-8"?><zero>\0</zero>' | xmllint -
-:1: parser error : Premature end of data in tag zero line 1
<?xml version="1.0" encoding="utf-8"?><zero>
^
And not in theory: https://www.w3.org/TR/2006/REC-xml11-20060816/#sec-well-form... Character Range
[2] Char ::= [#x1-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF] /* any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. */
[2a] RestrictedChar ::= [#x1-#x8] | [#xB-#xC] | [#xE-#x1F] | [#x7F-#x84] | [#x86-#x9F]It's a pity the catalog format doesn't support an 'import' or relative URLs for schemas - would have made local extensions a bit easier.
The original iPhone which killed flash didn’t even ship with the App Store. They assumed we’d only be using web apps.
It’s in the original Steve Jobs presentation when he announced the iPhone.
It seems the only way are tools that directly edit each respective browsers setting files (ie from the command line) but I’d rather not go down that path.
Of course there's always something else that can go wrong, but a big part of why flying is so safe today is that they've gone through a lot of trouble to enumerate and mitigate everything that has gone wrong in the past
It's weird that this has been known for over a decade, and noone ever added a 'pass on the argv[] array unchanged' in all that time
Now that I know I can't fix this in stock openSSH I think I'll just look into throwing argv[] into a base64 encoded JSON array and somehow have jq fix and exec it on the other end.
Whereas a desktop often has users on it who enter banking details or corporate login credentials. Much juicier targets.
It still wouldn’t be runtime typing, the compiler would just insert a constant wherever you use such a macro so I don’t think it would conflict with typescript’s goals. But it would make it a lot easier to build extra checks when deserializing data - or just give richer debug information.
But it would probably be hard for eg esbuild to support such a feature if tsc adds it. So I couldn’t use it anyway :)
Well, for one they still need Ireland's DPA approval before they release it to the EU.
was it ever offered for standardisation?