I think it's going to be the UI to manage your data as that will bring higher value to existing users. I'll make that surface in HTML which will enable porting to be easier.
6,510 karma · joined July 13, 2010
I need to decide between building a UI editor for moments, memories and meetings OR the port to windows/linux work.
What do you think I should work on first? (Asking everyone actually!)
https://innerloop.works/breadcrumb
What a rookie mistake!
https://innerloop.test/breadcrumb (for reference)
I guess I'll do a Show HN too but I really wanted a few more users before that but yolo.
Lightspeed is a websocket server.
Livewire talks to the server over normal HTTP requests and for anything pushed from the server it uses Laravel Echo. Lightspeed is a Pusher-compatible server so you'd point Echo at it like you would Reverb.
The thing Lightspeed adds is letting the browser send messages back into Laravel over that same socket, with auth on each one. Livewire doesn't do that its actions are still HTTP.
For most applications Livewire would be the goto. Lightspeed is kind of a high speed specialist option for building real time apps like you might do with node.js for exmaple.
Comforting a toddler/child often requires bending the truth and is pretty essential imho.
YMMV.
> 6.90 CHF - locks your Mac's keyboard, trackpad and mouse and shows a black screen while you clean. Free 7-day trial.
> 4.90 CHF - opens macOS's color loupe on any pixel on screen and instantly copies its HEX, RGB or HSL code to the clipboard. History of your last 8 colors, with a real magnifier that zooms into pixels. Free 7-day trial.
That's weird that the more techy thing is cheaper.
'comon now, let's not throw out the baby with the bath water.
That's a bit of an scorched earth extreme response imho.
This gives the end user all the customization they need and gives a company like obsidian the capability to have a little bit of secret source in today’s day and age.
That's the most irritating part.
Creating products with AI is like creating a tightly packed ball of wool. Then, to try to understand what happened you have to somehow pick a strand and pull it out to have a look. Very difficult with tightly packed wool.
I've run some experiments in the past month that get me closer to being able to work with this opaque bundle.
It's the main thing I think about every day, how to solve this problem.
I was very lucky to get a chance to interview him on our podcast back in 2010 [1]. He of course was very funny and insightful.
So kind of him to even come on our unknown show.
I used to love listening to him in early No Agenda [2] talking about his takes on all sorts of worldly things especially fine dining, spices, and all the famous people he'd had run-ins with.
[1] https://techzinglive.com/episode/6bc8086b/50-tz-interview-th...
You should be able to fix this by playing with the mic speech floor. It happens when to much ambient stuff slurps in.
It's actually gaslighting you, you don't say that many ums and ahs ;)
So, making a real time collaborative tool from scratch there was a lot of deep work in things like sockets, queues, memory structures, etc. That's just what needed attention.
Right now I'm building a memory app for AI.
So far I haven't spent much time looking at code on the swift side of things. But I have spent a lot of time up front working on domain driven design, screaming architecture, and module based design.
I think with AI the polish is in deep QA, design taste, running trace logs and constantly asking it to do html diagrams of the architecture and such.
ngl I miss "knowing what's going on" at the code level, but it feels like not a good use of my time to go into those weeds.
When I look at the code it seems well structured due to screaming architecture, and module based design.
My brain feels equally as exercised (in fact more so as I am not as good at agentic coding as I was at real coding)
But now I'm making highly polished Mac OS apps and I really like that move from JS.
I feel... conflicted.