kevsim

They eat six square meals a day!

I'll leave now...

They've got underlines for me at least

Yeah and Soniox is another similar as well, but I checked and neither is available in the AppStore

This is commonly referred to as "the boolean trap". You'll find lots of articles about it.

To use to write coding agents or for coding agents to write code in?

Exactly. If they just lay people off, that's just cost cutting, and potentially seen as a bad sign. If they're saying they're laying people off because they're replacing them with AI, then they're innovative!

Last I checked Miro also uses Pixi so that's another quality infinite canvas app.

How is the Anthropic stuff on Bedrock in general? We're using OpenAI stuff on Azure right now and it's frustrating how slowly stuff gets rolled out in our region(s).

The main reason I tend to reach for grid is responsiveness. Makes it way easier to change the layout at different screen sizes.

FWIW Ladybird is also built by people with actual browser engine experience

Render most of the frontend server-side and just use JavaScript for the dynamic bits only, I guess? I personally haven't done it like this since the advent of SPAs, but I'm guessing lots of things are still built like this.

What makes node inherently unsuitable for finance software?

Why do these apps require screen recording permissions to work? Just curious.

Guessing it reads some credentials out of environment variables. The client side example shows the server issuing a token so I guess it's only the server that has/needs the credentials.

When we built Kitemaker [0] we elected to not use CRDTs. We built our sync engine after reading the blog article Figma wrote about they didn't need CRDTs because they have the server arbitrating any conflicts. We ended up taking the same approach. It's worked out very well for us though in a tool like our "last one in wins" generally works fine and doesn't lead to a lot of surprises.

For documents, we had to do something more sophisticated. At the time we built our collaborative text editing, the prevailing opinions were that CRDTs were inferior for text editing so we ended up going with Operational Transforms. That took a LOT of work to get right and is still problematic from time to time. If we had it to do all over again now, we'd definitely challenge that decision (and may do so in the future anyway even though we have a system that works).

0: https://kitemaker.co

Slack seems to be surviving thus far at least

And now it says "Yup". That was pretty quick!

As a fresh-out-of-university engineer in the earlier 2000s, I had a ton of fun working at Nokia and the sheer number of devices was actually part of that. It was a blast having a stack of all of the weird and whacky devices on your desk at any time. I remember visiting some sort of internal museum in Finland at some point where you could basically see all of the devices they'd ever made. Mind blowing.

Of course getting to the software we were working on to actually run on the things was a different matter...

I think it's mainly the intensity of the sessions. You've got someone on the other end of a call so you don't really chill and take it easy. Creates some urgency to get the thing done and you're just a bit fried by the end.

In our 100% remote startup, VSCode live share and Slack Huddles is how we work through the really tough stuff together.

We should probably do it more often than we do, but there is a real fatigue after an hour or two.

Yep, that's what tons of houses outside of the immediate city center of Boston look like.

I believe here in Norway it's about 50% of devs that are in the technical unions.

Is this Rama solution similar to the kind of thing you can get with Kafka with KTables?

If so I'd be curious how they've solved making it in anyway operational less complex to manage then a database. It's been a few years since I've run Kafka but it used to kind of be a beast.

I would also think it'd be an incredibly expensive way to train a model.

If people seeing your frontend code is a security risk, I've got some bad news for you...

Sounds like you're incurring lots of risk - risk that the company won't really want to keep you around.

After relocating from the US to Scandinavia, people here are always give me crap for having worked in a cubicle farm. And I always tell them I'd go back to that layout in a second compared the open landscape nightmare we have everywhere here.

I'm pretty sure if you have to commit wire fraud to build your business, you can't really claim to be that great an entrepreneur.

Congrats on the launch! For teams that are using something like customer.io, how does this fit into the picture? Is it a replacement or a companion?

And to nerd out a bit - how was working with Lexical? We chose Slate.js for our editor in Kitemaker.co but it's not as actively maintained as it once was.

We used Webflow for our company's landing page for a while but for our uses it was more "slow code" than "no code". To get the layouts we wanted you still had to understand the quirks and intricacies of flex/grid so it was just a clunkier interface than writing code.

That being said, it got us up and running quickly at a time where we didn't have much time to spend on that stuff. I think it's a reasonable progression to start out with something like a no code tool and switch to code when you've got the time/people.