Consider the text:
Sent in my résumé! 😮💨
Computers represent that as zeroes and ones:
To me, #1360 "First-Class Stacks" seems like it started out great, in particular primitive stack-switching seems like a great low-level building block for everything you'd want to do including algebraic effects (#1359); but then it seems to me like it ended up both overly complex and yet also underspecified. In particular, stack extension and redirection seem like they should be extensions to stack-switching added later; whereas creating stacks seems like it would be immediately necessary for priority use cases like the Go and Erlang runtimes, and it seems like it would be a simple win to be able to send normal, non-exception values and thus remove the dependency on the exception-handling work.
Just like the TinyGo author suggested, it seems to me like it would be simplest to just have 3 instructions for creating, using, and destroying stack continuations, respectively:
// https://jsbin.com/xirefor/edit?js,output | |
var paper = Raphael("paper", 600, 600) | |
var n = 7 // number of boolean variables | |
var C1 = function(x1, x2, x3, x4, x5, x6, x7) { | |
return !x2 || !x3 || !x4 || x5 | |
} | |
var C2 = function(x1, x2, x3, x4, x5, x6, x7) { | |
return !x1 || !x5 || x6 |
<?xml version="1.0" encoding="utf-8"?><VisioDocument xml:space="preserve"><FaceNames><FaceName CharSets="1614742015 -65536" Flags="357" ID="1" Name="Arial Unicode MS" Panos="2 11 6 4 2 2 2 2 2 4" UnicodeRanges="-1 -369098753 63 0"/><FaceName CharSets="-2147483648 0" Flags="261" ID="2" Name="Symbol" Panos="5 5 1 2 1 7 6 2 5 7" UnicodeRanges="0 0 0 0"/><FaceName CharSets="-2147483648 0" Flags="261" ID="3" Name="Wingdings" Panos="5 0 0 0 0 0 0 0 0 0" UnicodeRanges="0 0 0 0"/><FaceName CharSets="1073742335 -65536" Flags="325" ID="4" Name="Arial" Panos="2 11 6 4 2 2 2 2 2 4" UnicodeRanges="-536859905 -1073711037 9 0"/><FaceName CharSets="262145 0" Flags="421" ID="5" Name="SimSun" Panos="2 1 6 0 3 1 1 1 1 1" UnicodeRanges="3 680460288 6 0"/><FaceName CharSets="1048577 0" Flags="421" ID="6" Name="PMingLiU" Panos="2 2 5 0 0 0 0 0 0 0" UnicodeRanges="-1610611969 684719354 22 0"/><FaceName CharSets="1073873055 -539557888" Flags="421" ID="7" Name="MS PGothic" Panos="2 11 6 0 7 2 5 8 2 4" UnicodeRanges="-536870145 179149 |
Date,Open,High,Low,Close,Adj Close,Volume | |
1927-12-30,17.660000,17.660000,17.660000,17.660000,17.660000,0 | |
1928-01-03,17.760000,17.760000,17.760000,17.760000,17.760000,0 | |
1928-01-04,17.719999,17.719999,17.719999,17.719999,17.719999,0 | |
1928-01-05,17.549999,17.549999,17.549999,17.549999,17.549999,0 | |
1928-01-06,17.660000,17.660000,17.660000,17.660000,17.660000,0 | |
1928-01-09,17.500000,17.500000,17.500000,17.500000,17.500000,0 | |
1928-01-10,17.370001,17.370001,17.370001,17.370001,17.370001,0 | |
1928-01-11,17.350000,17.350000,17.350000,17.350000,17.350000,0 | |
1928-01-12,17.469999,17.469999,17.469999,17.469999,17.469999,0 |
What: A capability-secure version of Node.js, and an ecosystem of capability-secure repackaged versions of existing NPM packages, community-contributed and hosted on GitHub like Homebrew & DefinitelyTyped.
Why: Immediately, this provides strong defense against malicious dependencies (supply chain attacks) like event-stream
, electron-native-notify
, typosquatting like crossenv
, and thousands more; as well as vulnerable dependencies like JS-YAML, [`express-fileupl
I don't like:
A design for a paranoid, secure-by-default, defense-in-depth JS sandbox.
3 different, complementary layers:
These are very complementary: the first layer is simple and hard for us to get wrong, but reliant on the browser not get wrong; the second layer is hard for the browser to get wrong, but reliant on us not to get it wrong, at runtime; the third and final layer is really hard for the browser to get wrong, but really reliant on us not to miss anything.
<style> | |
body { | |
font-family: monospace; | |
font-size: 16px; | |
color: #202122; | |
white-space: pre-wrap; | |
} | |
.nibble-sep { | |
margin: 0 -.15em; | |
font-size: 0.8em; |
TL;DR: You can simulate 8-bit safe "bytestrings" in JavaScript by restricting each character to code points U+0000 to U+00FF, and there are even tricks to easily convert between ordinary UTF-16 JS strings and UTF-8 encoded as such a JavaScript "bytestring".
unescape()
:
binary_str = unescape(encodeURI(utf16_str))
utf16_str = decodeURIComponent(escape(binary_str))
encodeURI()
/encodeURIComponent()
first convert to UTF-8, then percent-encode each byte into 3 ASCII charactersescape()
directly percent-encodes each UTF-16 code unit into 3 or 6 characters, depending on whether it's >U+00FF or notunescape(encodeURI(utf16_str))
is parsing the 3-character percent-encoded byte values as code points, producing "bytestrings" of code points all U+0000 to U+00FFdecodeURIComponent(escape(binary_str))
is parsing the 3-character per