ryanrussell
Very curious if you can elaborate on Vectorize. More than edge GPU's, entering the Vector DB marketplace and a CF proprietary integration is interesting (and a bit scary) to build on.
- Will Vectorize ever get OSS'd?
- If you want to migrate either direction from some other Vector DB(Milvus, Weaviate, Qdrant, Pinecone, etc), what should you expect in terms of level of effort and features?
- What inherent advantages(latency? features?) would you get exclusively from Vectorize?
Are there any plans for Corrosion to be published as OSS?
I am still absolutely amazed at how much more performant websockets throughput in bun vs node.
Congrats on 1.0!
Is anyone who is more familiar with Waterfox and LibreWolf able to objectively expand on the differences between these projects?
It sounds like the unsigned binary may be a maturity issue that will get tackled based on the mission statement(educated guess?).
Would greatly appreciate anyone with more knowledge about these projects elaborating.
A huge thank you to Colin Percival for sharing this.
Particularly love the "Once the low-hanging fruit was out of the way" line... which to Colin means custom bus_dma patch(es).
Now anyone can now enjoy for free:
"with 1 CPU and 128 MB of RAM, the FreeBSD kernel can boot in under 20 ms"
If you're used to devops with k8s clusters or lots of docker, this is absolutely amazing.
Michael - Don't take the bait.
As someone who has zero affiliation with Fly.IO other than a few PR's to their OSS(I don't even know Michael), I greatly appreciate the contributions they have given back to the community.
There are a lot of great hosting companies. Fly.IO stands out due to their revolutionary architecture and contributions back to the OSS community. I wish more companies operated like this.
It's understandable some are upset about an outage. But Fly is doing really interesting and game-changing things, not copying a traditional vmware, cpanel or k8s route.
Just as a reminder to what this company has offered back to everyone.
SQLite: Ben Johnson's OSS work around SQLite stands out. Fly.IO and his work have really made sqlite a contender. - https://fly.io/blog/all-in-on-sqlite-litestream/ - https://fly.io/blog/introducing-litefs/ - https://github.com/superfly/litefs - https://github.com/benbjohnson/litestream - https://fly.io/blog/sqlite-internals-wal/ - https://fly.io/blog/wal-mode-in-litefs/
Who really considered sqlite as a production option before Fly and Ben? Not me.
Firecracker: Firecracker is amazing, but difficult to debug when something bad happens. There aren't a ton of people in devops who would share what they have. If you've ever used Firecracker, you've really been helped a lot by the various guides they have provided back to the community like these: - https://fly.io/docs/reference/architecture/ - https://fly.io/blog/fly-machines/ - https://fly.io/blog/sandboxing-and-workload-isolation/
Their architecture is beautiful and revolutionary. They're probably the first or second ones to find a lot of the new edge cases as they grow.
It's a lot harder to be the first one over the wall than it is to copy. They've literally given the average developer a blueprint to build scalable businesses that compete with their own.
The tool may be great, but the title leaves me skeptical of anything else.
From: https://github.com/uptrace/uptrace/blob/master/LICENSE
Business Source License 1.1
Parameters
Licensor: Uptrace Licensed Work: Uptrace The Licensed Work is (c) 2021 Uptrace Additional Use Grant: You may make use of the Licensed Work, provided that you may not use the Licensed Work for a Tracing and Metrics Service.
A "Tracing and Metrics Service" is a commercial offering
that allows third parties (other than your employees and
contractors) to access the functionality of the
Licensed Work so that such third parties directly benefit
from the tracing and metrics of the Licensed Work.