Presumably over time shared parking areas will get upgraded with charging infrastructure to keep attracting tenants.
8,502 karma · joined April 22, 2009
Co-founder and CEO at Riza, a company working on untrusted code isolation with WASM: https://riza.io / hello@riza.io
Previously COO at ngrok: https://ngrok.com.
I was the Founder and CEO of an MVNO/VoIP hybrid company called Charge (formerly known as Bolt): https://charge.co.
I worked at Twilio: https://www.twilio.com.
I wrote the original ruby library that wraps Twilio's HTTP API: https://github.com/twilio/twilio-ruby
Other projects include receive-only telephone numbers at https://oneway.tel and free HPKP report bin hosting at https://hpkp.org (now defunct).
[ my public key: https://keybase.io/andrewmbenton; my proof: https://keybase.io/andrewmbenton/sigs/m4O8mq4uxoPSm2XlB1RUT1XkH5v8KX7UR448y8T74mo ]
Presumably over time shared parking areas will get upgraded with charging infrastructure to keep attracting tenants.
Because the LLM can't "just connect" to an existing API endpoint. It can produce input parameters for an API call, but you still need to implement the calling code. Implementing calling code for every API you want to offer the LLM is at minimum very annoying and often error-prone.
MCP provides a consistent calling implementation that only needs to be written once.
The actual thing that's different is that an OpenAPI spec is meant to be an exhaustive list of every endpoint and every parameter you could ever use. Whereas an MCP server, as a proxy to an API, tends to offer a curated set of tools and might even compose multiple API calls into a single tool.
I don't think this is a silly theory at all. The only possibly silly part is that containers specifically helped solve this problem just for python. Lots of other software systems built with other languages have "dependency hell."
Seems more like it's fallen out of favor with senior devs who have moved to Go/Rust.
We use WASM to provide isolated runtimes for executing untrusted code, mostly generated by LLMs. Our customers do things like extract data from log lines at run time by asking claude-3-5-sonnet to generate a parsing function on-the-fly and then sending it to us for execution.
Things we need help with:
* Our janky account management dashboard (Postgres / Go / React / TypeScript)
* Our hosted and self-hosted runtime service (Rust, WASM)
* Integrations and demos with adjacent frameworks and tools (Python / JavaScript / TypeScript)
* New products
We have seed money, but the whole company is currently just me and Kyle working out of a converted warehouse on Alabama St. We’re second-time founders, so we know the risk we’re asking you to take and we’re prepared to compensate accordingly. Send an email to me at andrew at riza dot io or pop in our Discord (https://discord.gg/4P6PUeJFW5) and say hi.
(A quick demo of this in the langchain docs, using claude-3-haiku: https://python.langchain.com/v0.2/docs/integrations/tools/ri...)
[0]:https://riza.io [1]:mailto:andrew@riza.io [2]:https://discord.gg/4P6PUeJFW5
[0] https://platform.openai.com/docs/assistants/tools/code-inter...
How would they ever find out if I did file, and why would they care?
Early exercise is purchasing shares before your options vest, making you a shareholder sooner and solving a bunch of tax issues. The company retains the right (basically the obligation) to repurchase any unvested shares should you leave the company before fully vesting.
It just said QR code menus can speed up service, not replace servers. Seems logical to me that if servers are spending time bringing out food rather than standing around waiting for guests to tell them what they want and writing it down that service will generally be speedier.
> I think that, if you had only five minutes with a world-class trader, and you asked her “teach me the essentials of trading,” probably she would spend the five minutes on adverse selection. The essential lesson is that, if you are being offered a trade, that probably means it’s a bad trade; your job is to understand that thoroughly so you can figure out the exceptions.
Yes, but spending money on growth is probably the number one thing VCs like to invest in. If you happen to be profitable, but also can demonstrate a clear path to growth, then VCs will lean in.
This is not a good argument. Yes things aren't perfect in many areas of technology, but that doesn't mean we should give up.
The better version of this argument acknowledges that there are tradeoffs: allowing side loading may introduce risk but the risk is low relative to the other risks users face and the benefits outweigh the costs.
We'll check out the e2b code interpreter sdk. Looks interesting!