harry lachenmayer

Co-founder @PicnicHQ, previously @boilerroomtv

[SIP @spottedinprod]

picnic · launch screen
by @jackrogers777

[harry lachenmayer @lachenmayer]

Xcode 16's best feature by far: you can now use folders instead of groups for organising your code!

No more merge conflicts in your project files! 🤩

Impossible to describe to anyone who is not an iOS developer how much time we have all wasted messing around with those files...

[Adam Wiggins @_adamwiggins_]

Wow, just wow. @localfirstconf was a big success—I'm still reeling from the experience.
​
A few takeaways:
​
We had several demos of super-fast UIs. Each one was strangely shocking: we’re used to “fast” in non-game software meaning <200ms. @overtone_app, https://t.co/wU5FNijHBj, and of course @linear do paints on the next frame (at 60fps that’s <16ms). I can’t wait for a future where we can expect this from more software.
​
Seeing so many frameworks ( @jazz_tools, @dxos_org, @powersync_, ...) and end-user apps ( @AnytypeLabs, @GoodnotesApp, ...) describe their technical architectures made it clear there’s a lot of convergence on core patterns. In his opening talk, @martinkl suggested we might be ready for an IETF protocol standard for local-first sync in the next few years. I was skeptical at first but after seeing these similarities it feels within reach!
​
One of our goals for the conf was to bring together people who come to local-first from many different directions: technical, design, business, academic, and more. Some are focused on developer experience or saving money on their out-of-control cloud provider bills. Others care about privacy or long-term philosophical goals. But despite this variety, the community feels harmonious in shared values.
​
My favorite thing was talking to the "local-first curious" attendees, many of whom had only heard of the term recently. One of these compared the energy of this community to React circa 2013, which seems like a good signal.
​
Still plenty of unsolved problems including identity/auth, partial sync, data migrations, and economic model. But also seeing that lots of people in the community are making great progress in these areas. It’s a wide-open frontier!
​
Grateful for everyone who helped make this happen ❤️

[localfirst.fm Podcast @localfirstfm]

Introducing localfirst⁠.fm – a podcast about local-first software development.

In this first episode @pvh explains what local-first is and why application developers should care about.

https://t.co/KpZc6vt2Pk

[harry lachenmayer @lachenmayer]

@tldraw @geoffreylitt here we go, ha!

[Margelo @margelo_com]

WishList Update: We finished our implementation of the platform-native Scroll View component and can now use smooth scrolling and bounce events - awesome work @janicduplessis! ⛹️‍♂️
Just a little bit of fine-tuning and we'll be able to launch WishList this summer. Stay tuned! 👀🚀

[Johannes Schickling @schickling]

Is anyone building an iOS app based on a combination of SwiftUI/AppKit for the UI and JS/TS for "business logic" (e.g. re-used from a web app) via some kind of Swift &lt;&gt; JS bridge?

I guess this is similar to how React Native works except the React part.

[harry lachenmayer @lachenmayer]

@ImRestrepo @ShopifyEng @appjsconf Yes please! :)

[harry lachenmayer @lachenmayer]

@RNLmeetup @axeldelafosse hype!

[Computer Facts @computerfact]

most people have forgotten or perhaps never realized how radical it is that on the web by default you can select and copy text

[Holly Herndon @hollyherndon]

I spoke to @pseudo__nymph of Document Journal about
@hollyplus_, @David_Rudnick idea of"digital prime" and optimistic approaches to IP and human artistry in the AI art era.

Thanks for such a thoughtful piece, it is fun and important to nerd out on this topic!!! 🥰

[Paul Frazee ✌️ @pfrazee]

You know, a Node on Rails sounds pretty good right now. NextJS is great but for the right project, handing me a ton of opinionated tooling for a larger app sounds pretty good https://t.co/lcZhzRf9o4

[Casey Muratori @cmuratori]

It is not just that the state of software is abysmal, that it rarely works, and that when it does it requires vast amounts of resources to perform simple tasks incredibly slowly. It's also that when it fails, even the simple task of reporting an error proves far too much.

[Jefferson 🦀🐍 @jeff_dev_]

When someone asks me how to get into software engineering.

#softwaredevelopment #webdev #100DaysOfCode

[harry lachenmayer @lachenmayer]

Vimeo is such a tragic case of a beautiful product getting completely screwed by "the market"...

More context here: https://t.co/ktIr9wmDBX

[Jason Scott @textfiles]

Entirely unintentionally, Vimeo has set up a spectacular art project, reminiscent of Chris Burden's Samson - the more popular a video becomes, the more it will bankrupt its creator/uploader.

Death by Attention

[rae mac @okdistribute]

I find it ironic that the US designed a very resilient mobile information network in the interest of national security and now a single programmer could accidentally introduce a bug into iMessage or AWS and cripple communications for millions of people

[Geoffrey Litt @geoffreylitt]

Overall, feels like there's a deep realization in these projects that handcrafting network communication is a pretty low-level activity. Fun to imagine a future where humans just aren't doing that very much for normal apps

[harry lachenmayer @lachenmayer]

@lks_kln 😬😬😬

[Raytraced Aesthetics 🔺🟢💎 @RaytracedVibes]

FISH33.POV

By: Mike Miller (POV-Ray, 1994)

[harry lachenmayer @lachenmayer]

@ericniebler Yes - this is my preferred form of technical interview, by far! Usually let them screenshare to get a feel for whether they can explain high-level design decisions or just get bogged down by explaining what each file does (as opposed to why it exists).