Bear Reviews

Temporal Reviews

Bear mentions (57)

• 7 Underrated Mac Apps Every Developer Should Try in 2026

  Bear is what you get when someone builds a notes app that respects developers. It's clean, fast, supports full Markdown, and syncs across devices. Unlike Obsidian, it doesn't require you to set up a vault structure and plugin ecosystem before you can write a single note. - Source: dev.to / 4 months ago

• Quiet UI: My Creative Outlet

  I kept track of bugs and ideas in Bear which, if you're in the Apple ecosystem, I highly recommend. When I stumbled on a good idea for a component that might be fun to build (sup, flip card), I'd write it down. - Source: dev.to / 10 months ago

• Bear is now source-available

  It's odd that this blogging system is using a name also in use by a writing tool: https://bear.app/. - Source: Hacker News / 11 months ago

• Bear is now source-available

  I got this confused with the Bear note-taking app for a minute (https://bear.app/), since it's in a closely adjacent domain and even has similar value statements. Unfortunate naming collision. - Source: Hacker News / 11 months ago

• After court order, OpenAI is now preserving all ChatGPT user logs

  Bear app is so damn good at markdown (by default) https://bear.app. - Source: Hacker News / about 1 year ago

Temporal mentions (17)

• Temporal in Production: Sharp Edges & Good Practices

  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

• Your Agent Bills While It Waits. Here's the Fix.

  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

• Compiler as Custodian

  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

• How we turned our workflow editor into a real SDK

  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

• Three days debugging a missing trace

  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