Stories

Comment by graftcodecom

Comment

Comment by graftcodecom

I would propose slightly different solution, I was doing software development for 30 years learning first patterns from Martin articles and what always felt strange was the fact that we had top 20 programming languages living in kind of silos.

I stride to address that by implementing runtime bridge for Java and .net and it was quite successful but only in niche use cases where somebody badly needed to use jar in .net or other way. One of funny achievement was that we managed to allow our customers use wpf user controls inside Java jframe! And it was living nicely in the UI and was binding events allowing to call methods etc..

That led me to though why if we take unzip library in Java we just add it as dependency via maven but if we call the same remotely or want to use unzip from Nuget we suddenly host it on separate node, write either rest, gRPC, subscribe queue via sdk or use thrift and then we write client for that and call it through those artificial layers up to unzip(string:filename) methods we wanted to call. WHY?

And therefore looking how to broaden our runtimebridge market we tried a crazy idea to allow any tech use any other tech by simple calling their public methods regardless if it’s in memory or remotely.

It took building runtime bridge for 143 tech pairs supporting clr, jvm, python, ruby, php, c++, go, node (js/ts), browsers js/ts etc…

NEXT we made it possible so they can call each other in memory and remotely.

Than we made that strongly typed interface is obtainable via simple package manager call.

And now users can take any module write just public methods and host it on our gateway running in their container/vm/machine and immediately they get api browser with commands for any package manager to get strongly typed client on the fly that always stays up to date.

Whenever anyone uses the module obtained (we call it graft) and calls any method it gets routed via any channel based on runtime config i.e. via env var and it can go http2, WebSocket, tcp/ip, any queue/event bus etc, or in memory!

And the system design is super simple just public methods and classes using them. It fits 1:1 what we see in OOP uml, code is fully decoupled from integration method, so we can change architecture in runtime even extracting logic to microservices from monolith. All services clearly reference their dependencies and get always up to date strongly typed client.

All of that makes AI, understand such system much better, use much less tokens, use much more efficiently context, and makes pull request review much easier!

The team either before or after code is written has much better control through simple OOP design.

It’s still evolving but we already achieved enterprise readiness and have many great POCs including IBM. We support full open telemetry, authentication, standard encryption of underlying channels purely removing the difference from same tech, cross tech, remote or local calls. Now everything feels like local method calls.

You think it would help to solve the issue of reviewing that code? @martinfowler?

Replies graftcodecom · 2026-09-05
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.