I use UpNote in part because it's not block-based. Blocks really screw up the way I like to edit. But if it's important to you, and if you're on a Mac you might look at Craft. It's not as user-friendly as UpNote, but it's just as feature-rich, and is block-based, with fantastic reciprocal linking. Source: about 3 years ago

Have a look at Craft and it's templates. https://craft.do/. Source: over 3 years ago

Don't apologize! It was perfect! I'm sorry, I at first thought Craft.js was referencing craft.do, as they're both kind of page editors, so I didn't realize what it was at first. This is such wonderful work! Thank you for pointing it out to me! This looks like exactly what I need! Source: over 3 years ago

Craft Docs (https://craft.do/) | Engineering (multiple roles) | Full Time | Remote (EU Timezone) or hybrid in Budapest (HU) or Edinburgh (UK) --- We're building an app for crafting beautiful documents and taking notes. Already available for 2 years, won the Mac App of the year 2021 award by Apple, good user base (individuals and business) and community (11k+ on Slack), raised a series B recently, plenty of runway,... - Source: Hacker News / over 3 years ago

The website and app works on every other network (cell, non-orbi wifi). I've tried the app and tried the web interface for Orbi, but haven't been able to find any way to unblock a specific domain. It's also not listed in the "Armor" settings as being a blocked threat. I have two office locations, both of which use Orbi, and both locations won't load craft.do. Source: over 3 years ago

When a team moves from a monolith into microservices and event-driven, asynchronous systems, it inherits a class of problems that used to be someone else's: work that fails halfway through, steps that must not run twice, calls that return before the work is done. Temporal is a durable execution engine that handles a lot of this - you define a multi-step process, and it guarantees the process runs to completion... - Source: dev.to / 2 days ago

Durable execution — the pattern implemented by Temporal, Inngest, Rivet Actors, and now Cloudflare Workflows — treats waiting as a continuation rather than a loop:. - Source: dev.to / 8 days ago

Two specific moves stand out in Duncan's account. The first is durable execution, via Temporal — Mercury replaced fragile cron-and-database state machines with workflow code whose failure semantics are platform-handled (replay, retry, timeout, cancellation). Mercury open-sourced its hs-temporal-sdk, which wraps Temporal's official Rust Core SDK via FFI and provides a Haskell-native API. The dovetail with Haskell's... - Source: dev.to / about 1 month ago

We picked Temporal as the first reference engine on purpose. Temporal has the strictest execution model we know of – a V8 sandbox, determinism constraints, replay-driven recovery. If our port contract holds up against that, easier engines – an in-memory test double, a BullMQ queue, or JSON-first platforms like Inngest or Restate – plug in through the same two interfaces. We're shipping Temporal first; the rest is... - Source: dev.to / about 2 months ago

The trick is to find whatever metadata channel the queue already gives you and use that and thankfully, almost every mature queue has one (probably because of this scenario). SQS has message attributes, Temporal has context propagators built into the SDK, and Hatchet (which we use to run our workflows) has a metadata field called additionalMetadata. - Source: dev.to / 3 months ago