Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kentonv
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
73 ms
·
961.
▲
by
kentonv
4y ago
> containers aren't a mechanism to increase compute granularity Yes they are. Instead of thinking in terms of a whole running operating system with dozens of services, now you are thinking in terms of individual (micro?)services tha
962.
▲
by
kentonv
4y ago
> isolates aren't really meant to isolate untrusted code. They totally are meant for that. That's arguably the main thing they are designed to do. The fact that people add defense-in-depth layers on top of it doesn't mean
963.
▲
by
kentonv
4y ago
> all it takes is one bad Chromium commit All it takes is one bad Xen commit, or one bad design choice at Intel, for VM-based clouds to be broken. Every isolation mechanism has bugs, this is not unique to V8. > for this model to fall
964.
▲
by
kentonv
4y ago
Yes, I didn't mean to imply that Chrome wasn't multi-process all along. But Chrome historically used it more for fault isolation (= crashing one tab doesn't crash them all) rather than security isolation. Historically window.
965.
▲
by
kentonv
4y ago
The future of compute is fine-grained. Cloudflare Workers is all about fine-grained compute, that is, splitting compute into small chunks -- a single HTTP request, rather than a single server instance. This is what allows us to run every cu
966.
▲
by
kentonv
4y ago
Thread switching is much cheaper than process switching. Threads are just stacks. Processes are whole address spaces. All kinds of caches need to be flushed when you switch processes (especially if you have more processes than you have PC
967.
▲
by
kentonv
4y ago
Chrome's use of strict process isolation is a fairly new thing. For most of its history, it was trivially easy to open any other site in the same process as your own site (via window.open(), iframe, etc.), and V8's sandboxing was
968.
▲
by
kentonv
4y ago
Ah hah... Well... I have no intuition for what might succeed in the cryptocurrency space. With Sandstorm we did plan to have paid apps and in-app purchases eventually, believe it or not...
969.
▲
by
kentonv
4y ago
I see. Well, I hope you are able to succeed at that. For what it's worth, we initially focused on consumer use but weren't able to find a path to revenue there. Despite a lot of noise on HN, we had only a few hundred signups for o
970.
▲
by
kentonv
4y ago
No, it's not Open Source. It's a perfectly justifiable decision, but it's not Open Source, nor is it equivalent. Yes, your license means that individual users can make little patches to customize the product to their needs, a
971.
▲
by
kentonv
4y ago
In my Tesla I've had the experience a couple times of trying to hit the break, but accidentally pressing both petals at once. When this happens, a notice appears on the dashboard saying both petals are being pressed and so the car has
972.
▲
by
kentonv
4y ago
If you have a fast, repeatable automated test that triggers the behavior you want to debug, then just about everything a debugger can do can be accomplished more easily by injecting code and re-running the test.
973.
▲
by
kentonv
4y ago
It's true you can do something similar with Lambda, but our architecture is much better suited to do this efficiently, especially in the case of scripts that aren't invoked very often. This is a new product in the very early stage
974.
▲
by
kentonv
4y ago
> If we had some "Open Worker Initiative" where I can build my software and then choose where I want to deploy it, it would sound ok. To that end, two announcements from yesterday: * Cloudflare, Deno, and others have formed a w
975.
▲
by
kentonv
4y ago
I think the easiest way to explain is this: Think of any SaaS app that has webhooks to notify users of events, and an API for automations to respond to those events. For example: * Chat service -> Chat bots * Forums -> Moderator bots
976.
▲
by
kentonv
4y ago
Right. The APIs are actually the place where the different runtimes are most similar to start with -- most of the APIs implemented by Workers were standards taken from browsers in the first place. The Workers Runtime is hugely different fro
977.
▲
by
kentonv
4y ago
Yes, apologies that we had to announce this before the code was actually ready. As you'll see, it's important context for our other announcements this week. But there's some work we still need to do to release the code. This
978.
▲
by
kentonv
4y ago
See also this blog post: https://sandstorm.io/news/2014-08-19-why-not-run-docker-apps
979.
▲
by
kentonv
4y ago
The quote matches my own understanding of the system from when I worked on Google Search circa 2005. Human ratings were used to facilitate an automated test that could tell you if your new algorithm actually made search results better or no
980.
▲
by
kentonv
4y ago
> or 50ms paid It's actually 30 seconds these days (for Workers Unbound pricing model). > do the entire process on CF's servers. Entire process of what, exactly? If you are just streaming the bytes through, that takes neglig
981.
▲
by
kentonv
5y ago
> Current solutions like Docker, Sandstorm, Cloudron, command line scripts etc. are "easy" for developers but not for ordinary users. What is easy for ordinary users? Installing a web app by uploading files to a folder on a ser
982.
▲
by
kentonv
5y ago
Yes? Is that surprising?
983.
▲
by
kentonv
5y ago
Author here. I'm now the lead engineer on Cloudflare Workers, and we use Cap'n Proto pretty heavily. The Workers team actively maintains and improves the Cap'n Proto C++ implementation. With that said, outside of C++, the sto
984.
▲
by
kentonv
5y ago
I think that optimization should still work when using Wasm, unless the Wasm code does something silly like manually pump the stream (read from one, write to the other), but I think you'd have to go out of your way to do that, and anyw
985.
▲
by
kentonv
5y ago
There's no time limit on requests, as long as the client is still connected. However, two things you might be thinking of: * If you use waitUntil() to schedule async work that completes after the HTTP response has been sent, this work
986.
▲
by
kentonv
5y ago
That's the thing... It can already do that without a V8 vulnerability.
987.
▲
by
kentonv
5y ago
Are in-app browsers in Electron even secure in the first place? Does it use Chrome-style sandboxing with multiple processes, etc.? Do bugs in the Electron engine get patched in a timely fashion? Genuinely asking here. I've never writte
988.
▲
by
kentonv
5y ago
This is a 0 day for anything that uses V8 to execute possibly-malicious JavaScript. Node.js and Electron aren't designed to do that in the first place, so this doesn't really affect them.
989.
▲
by
kentonv
5y ago
Mostly I'd say "no". At least, not much better than Cap'n Proto supports now. If you could convince multiple languages to share the same notion of a heap (including how to malloc() and free() memory), you might be able t
990.
▲
by
kentonv
5y ago
> One thing I've observed is Protobuf has caveats when mutated in-place (used as in-memory mutable application state) and Cap'n Proto is effectively impossible to resize objects To clarify slightly: Encoded Protobufs cannot be
More ›