Marko – A declarative, HTML‑based language that makes building web apps fun
Hacker News (score: 40)Description
More from Hacker
Show HN: Fresh – A new terminal editor built in Rust
Show HN: Fresh – A new terminal editor built in Rust I built Fresh to challenge the status quo that terminal editing must require a steep learning curve or endless configuration. My goal was to create a fast, resource-efficient TUI editor with the usability and features of a modern GUI editor (like a command palette, mouse support, and LSP integration).<p>Core Philosophy:<p>- <i>Ease-of-Use:</i> Fundamentally non-modal. Prioritizes standard keybindings and a minimal learning curve.<p>- <i>Efficiency:</i> Uses a lazy-loading piece tree to avoid loading huge files into RAM - reads only what's needed for user interactions. Coded in Rust.<p>- <i>Extensibility:</i> Uses TypeScript (via Deno) for plugins, making it accessible to a large developer base.<p>The Performance Challenge:<p>I focused on resource consumption and speed with large file support as a core feature. I did a quick benchmark loading a 2GB log file with ANSI color codes. Here is the comparison against other popular editors:<p><pre><code> - Fresh: Load Time: *~600ms* | Memory: *~36 MB* - Neovim: Load Time: ~6.5 seconds | Memory: ~2 GB - Emacs: Load Time: ~10 seconds | Memory: ~2 GB - VS Code: Load Time: ~20 seconds | Memory: OOM Killed (~4.3 GB available) </code></pre> (Only Fresh rendered the ansi colors.)<p>Development process:<p>I embraced Claude Code and made an effort to get good mileage out of it. I gave it strong specific directions, especially in architecture / code structure / UX-sensitive areas. It required constant supervision and re-alignment, especially in the performance critical areas. Added very extensive tests (compared to my normal standards) to keep it aligned as the code grows. Especially, focused on end-to-end testing where I could easily enforce a specific behavior or user flow.<p>Fresh is an open-source project (GPL-2) seeking early adopters. You're welcome to send feedback, feature requests, and bug reports.<p>Website: <a href="https://sinelaw.github.io/fresh/" rel="nofollow">https://sinelaw.github.io/fresh/</a><p>GitHub Repository: <a href="https://github.com/sinelaw/fresh" rel="nofollow">https://github.com/sinelaw/fresh</a>
Show HN: DBOS Java – Postgres-Backed Durable Workflows
Show HN: DBOS Java – Postgres-Backed Durable Workflows Hi HN - I’m Peter, here with Harry (devhawk), and we’re building DBOS Java, an open-source Java library for durable workflows, backed by Postgres.<p><a href="https://github.com/dbos-inc/dbos-transact-java" rel="nofollow">https://github.com/dbos-inc/dbos-transact-java</a><p>Essentially, DBOS helps you write long-lived, reliable code that can survive failures, restarts, and crashes without losing state or duplicating work. As your workflows run, it checkpoints each step they take in a Postgres database. When a process stops (fails, restarts, or crashes), your program can recover from those checkpoints to restore its exact state and continue from where it left off, as if nothing happened.<p>In practice, this makes it easier to build reliable systems for use cases like AI agents, payments, data synchronization, or anything that takes hours, days, or weeks to complete. Rather than bolting on ad-hoc retry logic and database checkpoints, durable workflows give you one consistent model for ensuring your programs can recover from any failure from exactly where they left off.<p>This library contains all you need to add durable workflows to your program: there's no separate service or orchestrator or any external dependencies except Postgres. Because it's just a library, you can incrementally add it to your projects, and it works out of the box with frameworks like Spring. And because it's built on Postgres, it natively supports all the tooling you're familiar with (backups, GUIs, CLI tools) and works with any Postgres provider.<p>If you want to try it out, check out the quickstart:<p><a href="https://docs.dbos.dev/quickstart?language=java" rel="nofollow">https://docs.dbos.dev/quickstart?language=java</a><p>We'd love to hear what you think! We’ll be in the comments for the rest of the day to answer any questions.
x86 architecture 1 byte opcodes
x86 architecture 1 byte opcodes
Show HN: Apache Fory Rust – 10-20x faster serialization than JSON/Protobuf
Show HN: Apache Fory Rust – 10-20x faster serialization than JSON/Protobuf Serialization framework with some interesting numbers: 10-20x faster on nested objects than json/protobuf.<p><pre><code> Technical approach: compile-time codegen (no reflection), compact binary protocol with meta-packing, little-endian layout optimized for modern CPUs. Unique features that other fast serializers don't have: - Cross-language without IDL files (Rust ↔ Python/Java/Go) - Trait object serialization (Box<dyn Trait>) - Automatic circular reference handling - Schema evolution without coordination Happy to discuss design trade-offs. Benchmarks: https://fory.apache.org/docs/benchmarks/rust</code></pre>
No other tools from this source yet.