HNHacker News
TopNewBestAskShowJobs

ridruejo

4,109 karma · joined June 2, 2009

Endor (https://endor.dev) cofounder. Parallelize your coding agents with Rover: https://github.com/endorhq/rover . Previously cofounder Bitnami (YC W13) and https://wasmlabs.dev
submissionscomments
ridruejo··on The ReMarkable Streaming Tool v2: Elevating Remote Work Efficiency
I wish something like this existed for the Amazon Scribe…
ridruejo··on Welcome to Datasette Cloud
Simon is a great technologist. I have learnt quite a bit from his videos and articles. I hope this works out for him!
ridruejo··on Westfield’s San Francisco centre mall lost 46% of its stores since 2020
It is pretty much as he described. Much much worse in parts of Soma.
ridruejo··on HashiCorp just let go 8%
"HashiCorp just let go 8%. Investors listening to earnings heard it before most employees." As much as I can empathize with the employees let go (it sucks), Hashicorp has a legal duty to inform investors of material information like this as soon as it becomes public, so it is normal that employees learn this way. There are a bunch of things that can be done better (or worse) handling layoffs but this one is hard to get around
ridruejo··on Hardening Drupal with WebAssembly
For a different approach that has FastCGI and MySQL support: https://wasmlabs.dev/articles/wordpress-nginx-fcgi-mysql/
ridruejo··on Hardening Drupal with WebAssembly
Kind of what you want, with wasmEdge and FastCGI https://wasmlabs.dev/articles/wordpress-nginx-fcgi-mysql/
ridruejo··on Hardening Drupal with WebAssembly
This is also the case with similar popular platforms like WordPress, there is always tension between expanding what you can do to include nearly everything people can think of, and at the same time keeping some basic checks/safeguards. There is also the issue that the most popular platforms and plugins will receive the most attention from attackers. Technologies like Wasm at least provide hope to alleviate some of those concerns by "sandboxing" the modules (ie if a module is a spellchecker it should not be allowed to connect to the network, etc.)
ridruejo··on Hardening Drupal with WebAssembly
VMware is a big company and there's a lot of interesting ways Wasm is being used internally. In our particular case, the aim of our group is not the one you outline. It is a bit higher level: how can we bring the most developers possible into the Wasm ecosystem? PHP + mod_wasm support is a way of getting the "LAMP stack" crowd an easy on-ramp. There are other ecosystems like Rust that already have had great Wasm support since early on and that's not necessary. There is work going in the direction that you point out, and there was a WasmEdge article a few hours ago on how to run on ARM, etc. https://news.ycombinator.com/item?id=36110253
ridruejo··on Hardening Drupal with WebAssembly
We are working on adding all that functionality, explanation here: https://news.ycombinator.com/item?id=36115146
ridruejo··on Hardening Drupal with WebAssembly
You are completely correct. These are just the early steps to get it into people's radars. We follow the Unix approach of "Make it work, make it right, make it fast". We are on the "make it work" step and moving to "make it right", for which we will focus to run as many unmodified applications as possible. This requires better support for PHP features that still depend on WebAssembly-related features that are not fully baked yet (ie threading, WASI preview 2) as well as adding over the network database support (ie MySQL) since most apps don't use SQLite in production.

Once all that is in place, you can move into the "make it fast" part, but for many scenarios where security is an issue (high profile websites) even a significant performance penalty (that can be offset with beefier hardware or caching) may be desirable.

ridruejo··on Hardening Drupal with WebAssembly
Capabilities based means that by default Wasm cannot do anything with the outside world. You have to explicitly declare the specific access you are giving, for example if the runtime implements WASI filesystem access you need to specify which parts of the underlying filesystem will be accessible to the module

Not yet public means exactly that. You may have a buffer overflow issue in your code that you are unaware of. There are technologies that help mitigate those when/if discovered. Wasm is one of them but not the only one (ie most modern compilers have specific settings to harden the binaries against some issues)

ridruejo··on Container Runtimes and WasmEdge benchmarking on Arm
Same applies to Wasm. See Fastly equivalent of 35 microseconds https://www.fastly.com/edge-cloud-network/serverless#:~:text....
ridruejo··on Container Runtimes and WasmEdge benchmarking on Arm
Meaningful benchmarks are hard. Having said that, in this particular context it is a good metric to measure the latency for the simplest possible function invocation as that is important for serverless at the edge (and why you put those workers/functions as close as possible to the clients in the first place)
ridruejo··on Container Runtimes and WasmEdge benchmarking on Arm
"Nobody is deploying large-scale services on top of what would be essentially the CGI model." Yes, they are. That's basically the Cloudflare workers model (which certainly qualifies as large-scale) and many other V8/Wasm based serverless solutions
ridruejo··on SQLite builds for WASI since 3.41.0
Correct!
ridruejo··on Extending web applications with WebAssembly and Python
You are not running a VM inside a VM. You are compiling to another target and modern Wasm runtimes allow AOT and JIT so performance is close to native while preserving all the other goodness of Wasm (sandbox, portability to 'weird' environments like browsers and IoT, etc)
ridruejo··on Extending web applications with WebAssembly and Python
By that logic, you can transpile your Python to C and then compile to Wasm
ridruejo··on Extending web applications with WebAssembly and Python
How is it misleading? It is the whole point that you can compile CPython or PHP interpreters to target this as another target platform like x86 or ARM
ridruejo··on Extending web applications with WebAssembly and Python
One of the aspects I find tremendously exciting about Wasm is not just the portability, security, performance, etc. but the fact that you can do this with your language of choice. Lowering the barrier to adoption without hindering some of the advanced use cases tends to work well to get developers onboard ...
ridruejo··on FaaS in Go with WASM, WASI and Rust
Wasm is the simplest target format and more generic than Java Bytecode, I’d start there
ridruejo··on FaaS in Go with WASM, WASI and Rust
This is where it is going, checkout the component model https://cosmonic.com/blog/engineering/evolution-of-wasm-stan...
ridruejo··on Docker is deleting Open Source organisations - what you need to know
Without entering into the specifics of this situation, I don’t understand the hate for Docker the company. They are providing a huge service for the community and looking for ways to make money from it to make it sustainable. I would give them a bit more empathy/benefit of the doubt as they iterate on their approach. Somewhere, somehow, someone has to pay for that storage and bandwidth whether directly or indirectly (I am old enough to remember what happened with sourceforge so I rather them find a model that works for everyone)
ridruejo··on WebAssembly: Adding Python support to WASM language runtimes
Looking forward to it!
ridruejo··on WebAssembly: Adding Python support to WASM language runtimes
Sure. Everything in computing pretty much builds on top of everything else. Wasm is no different and incorporates a lot of the learnings from previous technologies like Java and .NET
ridruejo··on WebAssembly: Adding Python support to WASM language runtimes
Not with that level of granularity. Wasm is able to run in severely constrained environments (ie microcontrollers) and non-posix OS that may not be able to support containers
ridruejo··on WebAssembly: Adding Python support to WASM language runtimes
Our most immediate goal is to be able to run traditional web apps written in PHP, Ruby, Python mostly unchanged but with the additional layer of isolation and sandboxing. We see this (once fully matured) as a great way to improve security without changing how web developers work
ridruejo··on WebAssembly: Adding Python support to WASM language runtimes
Correct, it is just CPython compiled to Wasm (similar to compiling to x86 or arm)
ridruejo··on WebAssembly: Adding Python support to WASM language runtimes
Yes! Single store is a great team. We are currently using some of their work for this Python release, like libz
ridruejo··on WebAssembly: Adding Python support to WASM language runtimes
Pyodide is for the browser, this is intended for server side environments, so it can interact with files, sockets etc via WASI standard
ridruejo··on WebAssembly: Adding Python support to WASM language runtimes
This one is designed to run on the server side and interface with the OS via WASI, so it can read/write files etc
← PreviousPage 3 of 16Next →