Hi HN. I’ve helped build an AI editor for your drafts. It’s called Owl Editor - it gives you a full editorial squad who get back to you in just a few minutes. They leave comments and suggestions right in your draft so you can accept/reject them at will. It’s the best writing feedback I’ve ever received from AI - check it out!
---
In Ancient Rome, the socio-economic divide was significant, and many poor Romans had to endure difficult, unpleasant, and dangerous jobs to survive. Some of the worst jobs for poor Romans during that period were:
Sewer Cleaner (Cloaca Maxima): Sewer cleaners were responsible for maintaining and cleaning the sewer systems in Rome. These workers had to wade through human waste, animal carcasses, and other refuse in the dark, damp, and disease-ridden underground passages.
Tanners: Tanners processed animal hides to make leather. This job involved soaking hides in vats of urine to remove hair and then treating them with a mixture of lime, water, and animal feces. Tanners were exposed to foul smells and harmful chemicals, and their work often led to skin and respiratory problems.
Fuller: Fullers were responsible for cleaning and bleaching woolen garments. They stomped on clothes soaked in a mixture of water and human urine, which acted as a natural detergent. Fullers were constantly exposed to the strong smell of urine and faced a high risk of skin infections due to the ammonia content.
Gladiator: Gladiators were slaves, prisoners of war, or criminals who fought in the arena for the entertainment of the Roman public. They faced brutal combat, often resulting in severe injuries or death. Although some gladiators gained fame and fortune, most lived a short and brutal life.
Miner: Roman miners, often slaves or criminals, worked in dangerous conditions, extracting valuable metals and minerals such as lead, silver, and gold. They faced the constant risk of cave-ins, toxic fumes, and lung diseases due to prolonged exposure to dust.
Street Cleaner: Street cleaners had to collect and dispose of the garbage, waste, and excrement that littered the streets of Ancient Rome. This job exposed them to infectious diseases and putrid odors.
Litter Bearer: Litter bearers carried wealthy Romans in litters (a type of carriage) through the streets. This physically demanding job often involved carrying clients up steep hills or for long distances under the hot sun.
Agricultural Laborer: Many poor Romans worked as agricultural laborers on farms, tending to crops and animals. These workers faced long hours in the fields, inadequate shelter, and meager food rations.
These jobs highlight the challenging and often hazardous conditions experienced by the poor in Ancient Rome, who had to endure such occupations to make a living.
* GPT-4 is decently faster when talking straight to the API
* The API is so stupidly cheap that it's basically a rounding error for me. Half an hour of chatting to GPT3.5 costs me $0.02
Would be curious what you mean by integrating the backend-api?
Greetings!YakGPT is a simple, frontend-only, ChatGPT UI you can use to either chat normally, or, more excitingly, use your mic + OpenAI's Whisper API to chat hands-free.Some features:* A few fun characters pre-installed* No tracking or analytics, OpenAI is the only thing it calls out to* Optimized for mobile use via hands-free mode and cross-platform compressed audio recording* Your API key and...
1. It doesn't show off the unique capabilities of firecracker very well.
2. The comparison not very fair.
2a. The docker-build step (which dominates the runtime) is run without any caching, just by adding 2 lines to your build-push-action, "cache-from: type=gha, cache-to: type=gha,mode=max" you can make it a lot faster.
2b. ~1m20s of the time is just "VM start". GitHub Actions has had a rough time recently, but you should never wait that long to get your CI running in day-to-day operation.
2c. The tests are unrealistically short at 20s which allows the author to get to their 10x faster number.
Let's say the GitHub Action starts in 5 seconds, the GitHub Actions cache reduces the build time to 2 minutes and the tests take 10 minutes to run. Now Firecracker is 20% faster ...
You can also get comparable performance out of https://buildkite.com/ which lets you self-host runners on AWS meaning you're almost guaranteed to get a hot docker cache (running against locally attached SSDs). You can now start running your tests (almost) as fast with much more mature tooling.