nteon

10 ms·

31.
by nteon 10y ago
We use Web Workers as the basis for our processes, and processes perform system calls to the kernel (running on the main browser thread). Our standard system call mechanism is asynchronous and uses the standard postMessage API to/from
32.
by nteon 10y ago
I know you were kidding, but one of the co-authors of Browsix wrote the Doppio JVM: http://doppiojvm.org/ a full JVM in pure JavaScript. It will soon run under Browsix!
33.
by nteon 10y ago
not yet :) We're currently focused on command line programs -- it would be really neat to see Haskell running by adding support for Browsix into http://haste-lang.org/
34.
by nteon 10y ago
Author here. One thing to emphasize is that all processes run in the browser and are isolated from whatever underlying OS/filesystem the browser is running on - there is nothing special to think about in terms of sandboxing or securit
35.
Browsix: Unix in the browser tab(browsix.org)
19 points by nteon 10y ago|5 comments
36.
by nteon 10y ago
I'm quite serious. What's your concern - that it is unrealistic, or that we should stick with mostly-static, single-threaded web-pages forever?
37.
by nteon 10y ago
Yea - the shell is an MVP, to say the least. I plan on replacing it later this week with something like term.js to provide a more consistent terminal experience.
38.
by nteon 10y ago
The emterpreter is really an interpreter, but as you guessed, you can direct the compiler to compile parts of your code to ASM.js so that you can benefit from native-like performance for CPU-intensive parts of your app. Yield is relatively
39.
by nteon 10y ago
A number of things - do you have a small microservice that was easier to write as server-side code, but you don't want to worry about scaling it? Run it in-browser without code changes or worrying about jank - the server is run in a W
40.
by nteon 10y ago
First, (as silly as it is), 'cd' is not yet implemented, as that is a shell intrinsic. Second, Firefox stable (46) is currently supported, but something has changed in the nightly that breaks us. It should be simple to track down
41.
by nteon 10y ago
Hi, one of the authors here. Thanks! We have a tech report, that has more details on what we are aiming for here: https://web.cs.umass.edu/publication/details.php?id=2414 As another example of what we can do with real
42.
by nteon 10y ago
Hi, I'm one of the main authors of Browsix. One of our goals is to run C code - we have simple utilities from sbase running, and more complex code like latex and GNU make (the README needs updating). The main complication is that C c
43.
by nteon 10y ago
The Chromium team's blog post about this suggests that > 99% of HTTP/2 connections are _already_ negotiated with ALPN [1]. I imagine all of the CDNs and other large providers already use ALPN, so this mostly affects the long t
44.
by nteon 11y ago
MathQuill is amazing, I haven't seen anything else as nice for inputting moderately complex formulas.
45.
by nteon 11y ago
Can you describe an example of a better, real-world unit test you have in mind? Do you also advocate against writing ES6 and using Babel?
46.
by nteon 11y ago
Pierce's Types and Programming Languages ( https://www.cis.upenn.edu/~bcpierce/tapl/ ) is great - I'm working throught it now. Its goes through both untyped and statically typed languages. It also goes
47.
by nteon 11y ago
what is memory usage like in terms of number of allocations and peak RSS with B3 vs. LLVM?
48.
by nteon 11y ago
You could easily do a syscall to get a signalfd file descriptor, then call os.NewFile to turn that numerical FD into a Go *os.File ( https://golang.org/pkg/os/#NewFile ). It seems like that should work fine!
49.
by nteon 11y ago
C doesn't have generics, and is certainly a systems language. I don't think you have a strong point here. Systems != embedded.
50.
by nteon 11y ago
"I still wonder why we can omit commas on import/var/const blocks and just can’t on lists and maps. Anyway, Rob Pike knows better than me! Viva la Readability!" import/var/const blocks rely on semicolon inserti
51.
by nteon 11y ago
Has Debian really not given up? Bundling is why chromium is (still) not in Fedora's repos[0], yet Debian has shipped it for years. I've assumed Debian was more lax on bundling or build reproducability issues - is there another re
52.
by nteon 11y ago
A 'replacement' for systemd should be designed to be drop-in: /sbin/init should read unit files (which in general are much nicer than init scripts), should provide systemctl with the same options, and if dbus is also und
53.
by nteon 11y ago
V8 uses a function's length in characters, _including comments_, to make optimization decisions. By removing comments and shortening var identifiers internal to a function, I can imagine a number of functions dropping under that 600-c
54.
by nteon 11y ago
for an example, checkout this: http://pasky.or.cz/dev/glibc/ifunc.c Two implementations are compiled (one is optimized using instructions only available on certain processors), and the decision of which one to use
55.
by nteon 11y ago
If you're using shared libraries in your program, you already have this extra indirection - at compilation/link time the compiler/linker doesn't know where in memory the shared library will be when the program is run, so
56.
by nteon 12y ago
very neat. It definitely seems useful to be able to do a speculative read/write from an eventloop, and only defer the IO to another thread if it would block.
57.
by nteon 12y ago
Table 1 is looking specifically at getting a chunk of data off the wire and into the users code. Look at Table 2 for a comparison of redis read/write. Average time for a write is 163 μs - of which 137 μs is spent in fsync(2)
58.
by nteon 12y ago
To be clear, 80% of kernel-time in that 1KB write is spent in fsync(), _not_ in the network stack. Network overhead is roughly similar between read & write requests. What Arrakis seems to be able to do is avoid the overhead of write &
59.
by nteon 12y ago
agreed - redis is a single binary with minimal dependencies, this seems like so much more work for no gain.
60.
by nteon 12y ago
no - its not the job of the compiler to choose your memory allocator. There is talk, however, of replacing the current glibc allocator with jemalloc[1], which is the more appropriate place for that decision to be made. 1 - https:/&#x

More ›