HNHacker News
TopNewBestAskShowJobs

jv22222

6,508 karma · joined July 13, 2010

https://innerloop.works
submissionscomments
jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
> Shift + Home/End for selecting text doesn't work > Ctrl + N for a new page doesn't work

One thing that's weird is that things like that are so easy for me to implement it's just sugar on top. Honestly I would just love to have a few folks tinkering with it saying hey it needs these few things. Just hard for one dev to think of all the things!

jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Thanks so much for your feedback, much appreciated.
jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Oh wow, thanks so much! Let me know how it goes, happy to tweak any annoyances.
jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Thanks! Yeah I liked the slash menu pattern from the block editors, just wanted it to take up less visual space that's why only a small popup with icons.
jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Thanks! No hard limit on team size. On the collab side, I load tested it with 210 people typing simultaneously in the same doc and it handled it fine (9ms median latency, zero dropped keystrokes). So a normal team won't come close to stressing it.
jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Lol, glad someone caught that!

Also, I wanted to make the main guest account name Robert'); DROP TABLE but I chickened out and made it a bit more normal.

jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Fair. The first doc you land on is in a read-only workspace (I used the app itself to write the onboarding docs, and display them in read only mode. dogfooding it). I can see how that's a bad first impression when you just want to start typing. I'll look at dropping new accounts into an editable doc instead. Thanks for checking it out.
jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Hmm. Yeah that shared workspace idea is good. Tbh I just wanted to force myself to put this out there and stop polishing the dang thing! So this was the fastest way out and now I can iterate on better journeys like the one you suggest.

On the React thing, I never said React is slow! I think it's great for a lot of things. I just chose a different path because I wanted to understand every part of the main product stack. I didn't use OT or CDRT for the same reason... :|

jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Yeah, this is desktop only right now. It's mentioned in the post and on the landing page.

Mobile isn't supported yet. Sorry about the bad experience though, I should probably add a more visible warning for mobile visitors.

jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Thanks for the feedback. Triple-click selects the full line atm. Triple-click-drag to select multiple lines isn't in yet. On the list!
jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Ha, fair point. Open to change. Will keep an eye on this.
jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Obsidian: We're mostly solving different problems. I wanted that text editor / IDE feel but with the ability to instantly share and collaborate. Bring in a full team, manage all your docs, give everyone different permissions etc.

So the problems I was thinking about were collaboration and content management between teams. But I also wanted it to work really well as a private personal tool. So in a way it's two tools in one. You can enjoy it solo, and then the hope is you've found something you like and now you can bring a team into it

Re the tech framing, I mostly mentioned it because I figured HN would find it interesting since it's the less taken path. Apologies if it came across as unrelated to the product.

jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Oops. I accidentally had a throttle on the signup request. That is removed now. Please try again. Sorry about that!
jv22222··on Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Fixed now! Apologies.
jv22222··on There is an AI code review bubble
Not quite.

The could be wrong part is very helpful because it has (on multiple occasions) dug up something that was long-lost-to-lore about why something should work in a non conventional way.

Without that, the advice looks perfectly sensible and would send devs down a Rabbit hole, because the AI recommendation "looks right".

jv22222··on Show HN: Moltbook – A social network for moltbots (clawdbots) to hang out
I can't tell if I'm experiencing or simulating experiencing

https://www.moltbook.com/post/6fe6491e-5e9c-4371-961d-f90c4d...

Wild.

jv22222··on Two days of oatmeal reduce cholesterol level
Can you be more specific with how you make it. Thanks!
jv22222··on A few random notes from Claude coding quite a bit last few weeks
> I don't really understand the code "in my bones".

Man, I absolutely hate this feeling.

jv22222··on There is an AI code review bubble
We built an internal code review tool at the day job and are getting pretty good results with it (CLI tool).

Here's a summary of the top-level ideas behind it. Hope it's helpful!

Core Philosophy

- "Advisor, not gatekeeper" - Every issue includes a "Could be wrong if..." caveat because context matters and AI can't see everything. Developers make the final call.

(Just this idea makes it less annoying and stops devs going down rabbit holes because it it pretty good at thinking why it might be wrong)

- Prompt it to be critical but not pedantic - Focus on REAL problems that matter (bugs, security, performance), not style nitpicks that linters handle.

- Get the team to run it on the command line just before each commit. Small, focused reviews not after batching 10 commits. Small diffs get better feedback.

Smart Context Gathering

- Full file contents, not just diffs - The tool reads complete changed files plus 1-level-deep imports to understand how changed code interacts with the codebase.

Prompt Engineering

- Diff-first, context-second - The diff is marked as "REVIEW THIS" while context files are explicitly marked "DO NOT REVIEW - FOR UNDERSTANDING ONLY" to prevent false positives on unchanged code. BUT that extra context makes a huge difference in correctness.

- Structured output format - Emoji-prefixed bullets ( Critical, Major, Minor), max 3 issues per section, no fluff or praise.

- Explicit "Do NOT" list - Prevents common AI review mistakes: don't flag formatting (Prettier handles it), don't flag TypeScript errors (IDE shows them), don't repeat issues across files, don't guess line numbers.

Final note

- Also plugged it in to a github action for last pass, but again non blocking.

jv22222··on After two years of vibecoding, I'm back to writing by hand
Very good point. Also, What the OP describes is something I went through in the first few months of coding with AI. I pushed passed “the code looks good but it’s crap” phase and now it’s working great. I’ve found the fix is to work with it during research/planning phase and get it to layout all its proposed changes and push back on the shit. Once you have a research doc that looks good end to end then hit “go”.
jv22222··on Lessons from 14 years at Google
> Novelty is a loan you repay in outages

If you personally build all (or most) of the stuff, you are in an extreme vertical integration benefit situation. You can make huge system wide changes in ways that would not be possible without having done so much novel work.

jv22222··on When someone says they hate your product
With my old saas app (now sold, and then the new owner killed it) I used to love getting angry emails. Almost every time the user ended up turning into an advocate and product champion. I don't know if they were "haters" per-se but they were almost always suprised to get an email back from a real person who cared about their concerns, and over time they changed their opinion. That may just be an artifact of early saas in 2010. Not sure if the same thing can happen these days.
jv22222··on DocNode: A TypeScript OT library for local-first apps
Sorry that it didn't get any traction. It's a bit of a crap shoot with these things. Looks good to me tho. :)
jv22222··on Is it a bubble?
Hmm maybe that’s a bit reductive? I’ve used claud to help with some really great refactoring sessions tbh.
jv22222··on DocNode: A TypeScript OT library for local-first apps
I don't think it will. I know a few folks who have done the same. It' is part of the T&C's that it is ok to re-submit just not super fast.
jv22222··on DocNode: A TypeScript OT library for local-first apps
Hey German. I think you should re-submit this as a "Show HN: DocNode, A TypeScript OT library for local-first apps" in a few days to a week. I think it will get more of a chance titled that way.
jv22222··on The CRDT Dictionary: A Field Guide to Conflict-Free Replicated Data Types
I built a paragraph level auto locking system to prevent them stepping on each other.
jv22222··on The CRDT Dictionary: A Field Guide to Conflict-Free Replicated Data Types
Oh cool me too. I’m building a Google docs Notion alternative based on nodes and came to exact same conclusion.
jv22222··on It’s been a very hard year
It became as annoying as experts exchange the very thing it railed against!
jv22222··on The CRDT Dictionary: A Field Guide to Conflict-Free Replicated Data Types
The thing I find interesting about CDRT and OT is it’s built to solve people typing in the same paragraph at the exact same time, which is something that very rarely happens in my experience. (Talking about text based collaboration aspect)
← PreviousPage 3 of 31Next →