Readit NewsIt'd be an interesting experiment to take memory snapshots after each step in a workflow, which an API like Firecracker might support, but likely adds even more overhead than current engines in terms of expense and storage. I think some durable execution engines have experimented with this type of system before, but I can't find a source now - perhaps someone has a link to one of these.
There's also been some work, for example in the Temporal Python SDK, to overwrite the asyncio event loop to make regular calls like `sleep` work as durable calls instead, to reduce the risk to developers. I'm not sure how well this generalizes.
Trigger.dev currently uses CRIU, but I recall reading on HN (https://news.ycombinator.com/item?id=45251132) that they're moving to MicroVMs. Their website (https://feedback.trigger.dev/p/make-runs-startresume-faster-...) suggests that they're using Firecracker specifically, but I haven't seen anything beyond that. It would definitely be interesting to hear how it works out, because I'm not aware of another Durable Execution platform that has done this yet.
I feel sorry for their database because I was a teenager with a bunch of guitar pedals and an ongoing need for 9V batteries. I made up a LOT of phone numbers.
We had to invent our own buttons if we wanted it to look the same everywhere. I could be wrong though.
I'm sure I'll trigger a lot of designers by saying this, but I'm probably not alone in valuing basic usability FAR above styling. I much rather have an ugly button that looks like 90's era Tcl/TK than something pretty that doesn't behave like I expect it to.
10 years ago someone decided that dragging links is so much more important than selecting text, selecting text is scarcely possible. I'm going to have to fork a browser to give link-dragging the demotion it deserves. It was probably those DIV guys.
I find non-selectable text maddening, but I recently found an macOS app called TextSniper that restores my control. It lets you select an area with the mouse (as you would when taking a screenshot) and it then OCRs the text and puts it into your clipboard. It almost makes Google Analytics usable again.
From a value proposition, it seems good. Our group definitely goes through keyboards and mainboards from spilled tea at least annually it seems, but AppleCare is just a no-brainer, and away we go.
I still drive on my original M1 at home without complaint, and use my M3 at work. Anyone have the early Frameworks still in daily use? How are they?
Build quality of the MBP is better. The machine feels more solid. The battery life is better, although to be fair, I run Linux on the Framework so the hardware itself isn't the only difference.
The Framework 16 wins hands-down when it comes to ports, one of my biggest pain points with any Apple laptop in the last 10 years. It has six of them and I can mostly arrange them according to my needs. In the rare cases where I plug it into an external monitor, I swap out one of the USB ports for an HDMI port. If I'm using more older devices than normal, I replace the USB-C ports with USB-A ports. I say "mostly" here because not all ports work in all positions.
The repairability and openness of the Framework laptop were the big draws for me and it delivered well on both counts. I'm happy with it.
But in fact, customer call centers tend not to be able to even know that you called in yesterday, three days ago and last week.
This is why email-ticketing call centers are vastly superior.
Nor what you told the person you talked to three minutes earlier, during the same call, before they transferred you to someone else. Because their performance is measured on how quickly they can get rid of you.