I just spilled my coffee; sorry for the trivial remark, but the name means 'pubic hairs' in Romanian. Apologies.. I thought it's better for you to know and ignore than not to (not quite a big population target for you, I imagine, anyway).
nxobject [3 hidden]5 mins ago
As Coq (now Rcoq) found to their chagrin... I'm convinced half of the reason Lean has surpassed Coq in mindshare in formal mathematics was because it's impossible to not chuckle at the name sometimes.
luis_cho [3 hidden]5 mins ago
There was once a cloud conference in Brazil called ConaCloud. I'm guessing "cona" means something different in Brazilian Portuguese than it does in European Portuguese.
In Portugal is a slang word for vagina.
Do Greek people really say "Here comes the spunk!" when they're... you know?
Vasbarlog [3 hidden]5 mins ago
Hahahaha, have never personally heard that.
khimaros [3 hidden]5 mins ago
though not nearly as popular of an expression in that category as μαλάκας
stevekemp [3 hidden]5 mins ago
One of the later pages mentions that the name came from "cirrocumulus floccus", the cloud formation.
adrian_b [3 hidden]5 mins ago
In this case it is misspelled.
The Latin word is "flocci", which means hairs of wool, and it was also used to denote an insignificant thing.
English normally preserves the double consonants of Latin, and in this case it has already done this in the English words derived from "floccus", e.g. "to flocculate" and "flocculent".
In clouds, it was used due to the resemblance of those clouds with curly sheep wool.
illiac786 [3 hidden]5 mins ago
You mean like Flikr, sonarr, tumblr, Waze…?
coolca [3 hidden]5 mins ago
Also it means gays (not in a flattering way) in italian if you just change a letter.
pi-victor [3 hidden]5 mins ago
you got here before me, had a good laugh tho.
thegagne [3 hidden]5 mins ago
The cool part of this is it’s an example of what’s possible with a community of users armed with AI.
Many users, (myself included), had need to test cloud stuff locally, but had no tool to do so. Localstack exists, but it started rug pulling the free tier and they didn’t support all the features.
Meanwhile, Floci makes it easy to write your own cloud compatible test suite, then implement the feature to match. I was able to get a good enough coverage on a few features created in a weekend on the $20 tier of Claude to make it useful to me, then others picked up the work to round it out.
It’s really cool to see it grow.
didgeoridoo [3 hidden]5 mins ago
I’d love to see this for stuff like Stripe, Twilio, etc - they’ve got sandboxes but this would be a lot easier and faster.
catlifeonmars [3 hidden]5 mins ago
Both localstack and floci live in this weird spot where for a lot of my applications, all the cloud-vendor specific stuff is abstracted out anyway. So the only time I need to touch the cloud is for testing the abstractions and do end to end testing. The abstractions can be tested against real cloud APIs as it is generally cheap to do and provides the highest fidelity results. End to end testing includes testing against a production-like environment, so again, more bang for your buck to just test against the cloud.
I’ve definitely reached for these local cloud tools from time to time, but in a well-architected piece of software, you aren’t getting that much value from them. Either you don’t have a hard cloud dependency, or you want a high fidelity test of a specific cloud dependency.
microflash [3 hidden]5 mins ago
Been using it for a while to run integration tests with Testcontainers [1]. It's very good and much more lightweight than Localstack.
Would someone be interested in this but intended for production? Im already running a whole bunch of cloudflare and AWS services in my own AWS fake and it works surprisingly well! :)
michaelastreiko [3 hidden]5 mins ago
Local stubs for cloud services are a lifesaver when you're a one-person shop and don't want a surprise bill just to test a webhook path.
mkirsten [3 hidden]5 mins ago
This looks very cool! Is this only intended for testing and development, or as a feasible way to migrante away from e.g., GCP as well?
I’m interested in something that would allow me to over time migrante away from a GCP project that uses many services today - e.g., Datastore, FileStorage etc.
_bohm [3 hidden]5 mins ago
Definitely not feasible to migrate off of actual cloud services using something like this.
VoidWhisperer [3 hidden]5 mins ago
Most likely a false positive, but worth noting for the people who run the project: Malwarebytes currently flags the site as 'potentially unsafe' when trying to visit it - not sure what the best avenue for them to get that fixed beyond reaching out to Malwarebytes might be
n738 [3 hidden]5 mins ago
This is awesome, hope to see it mature over the years!
The Latin word is "flocci", which means hairs of wool, and it was also used to denote an insignificant thing.
English normally preserves the double consonants of Latin, and in this case it has already done this in the English words derived from "floccus", e.g. "to flocculate" and "flocculent".
In clouds, it was used due to the resemblance of those clouds with curly sheep wool.
Many users, (myself included), had need to test cloud stuff locally, but had no tool to do so. Localstack exists, but it started rug pulling the free tier and they didn’t support all the features.
Meanwhile, Floci makes it easy to write your own cloud compatible test suite, then implement the feature to match. I was able to get a good enough coverage on a few features created in a weekend on the $20 tier of Claude to make it useful to me, then others picked up the work to round it out.
It’s really cool to see it grow.
I’ve definitely reached for these local cloud tools from time to time, but in a well-architected piece of software, you aren’t getting that much value from them. Either you don’t have a hard cloud dependency, or you want a high fidelity test of a specific cloud dependency.
[1]: https://testcontainers.com/
I’m interested in something that would allow me to over time migrante away from a GCP project that uses many services today - e.g., Datastore, FileStorage etc.
For us, floci-oci for object storage looks interesting. For everything else we have our own stack.