oDot

Indeed! Please check out this project I made to basically make the server an extension of the front end by having it reply to client side ui messages:

https://github.com/weedonandscott/omnimessage

I work in Gleam on my software and it's a treat. I use the FFI for JS libraries all the time.

Yes.

https://nestful.app used to be TS + Vue but it's almost entirely Gleam now, with Lustre used for state management and only the views being Vue templates. Those will also be migrated away for a fully Lustre solution.

Blog posts:

https://blog.nestful.app/s/the-tech-behind-nestful

I moved to Gleam with all of my projects and am not going back. The language is fantastic but really the most impactful are the coding paradigms that it enables, especially the actor model and especially on the front end (The Elm Architecture)

I was talking just about the look of it, and not the interactivity. UX's familiarity bar is much higher than than the UI one.

Edit: And even for UX -- I am confident in saying we did not reach max usability yet. Some people (me included) are willing to take the risk of (some) unfamiliarity for potential innovation

Interestingly, I am looking for the exact opposite -- I don't want my products looking anything like other websites.

The democratization of skill-learning is splendid, but boy is it hard to find a non cookie-cutter designer these days.

If you know anyone ..

Ofek (at) nestful dot app

Thanks for the heads up about paperlater!

AI is indeed a crucial part in solving the two most difficult challenges -- typesetting and curation, although we'll probably do things that don't scale for a little while before fully automating.

You got it exactly right, curation and typesetting are the most challenging aspects of it. Experimenting with different solutions...

Typesetting is a challenge so broadsheet vs tabloid is undetermined, but whatever it will be it will be delivered to the door. The newspaper paper is a crucial part, I believe.

Not yet, but we'll need beta testers. If you're interested and in a large metro area please reach out to ofek [at] nestful [dot] app mentioning said metro.

This is especially timely, as I'm currently building a service that let's you receive your RSS feed as a physical newspaper.

Many times this sort of meta information reveals much more than expected

Via Gleam's discord:

https://discord.gg/Fm8Pwmy

There's some good stuff there

I wouldn't say I agree with those circumstances, but even if they did indicate a match with Next.js, they are not worth the reduction in productivity and maintainability that comes with it.

I use Gleam's Lustre and am not looking back. Elm's founder had a really good case study keynote that Next.js is basically the opposite of:

https://www.youtube.com/watch?v=sl1UQXgtepE

The whole line of Tanstack products is very well made yet poorly designed at the same time. I don't know if it's inherited from React by trying (and succeeding) to be a seamless React experience or if it's part of their own philosophy, but most of the tools make it very easy to mix state everywhere in your app which is just bad.

Really people should just move to Gleam and Lustre or Elm, even if it means I'll have much fewer clients paying good money to untangle state issues...

Can someone explain AMDs motivation in opening what is traditionally (tightly) closed firmware?

I have a Zephyrus G16 with a 370 and can confirm it would fail to sleep on Linux 6.12.

Upgraded to 6.15 and sleep seems to work well now.

I use NixOS

I have been looking for a designer for Nestful[0] for a while now, and although I could find very talented designers, they all look to be doing the same kind of thing.

You mentioned originality but to me it all looks like whatever the current trend is on repeat. I know that this may be a result of client demands but in the end it makes it very hard to judge if the designer can communicate and introduce design flare unique to Nestful, or if they are just very talented on executing preexisting ideas.

[0]: https://nestful.app

There's a disconnect somewhere in the industry, because as I writer I can guarantee you one of the things readers get most annoyed with is on the nose dialogue.

My screenplays are heavily influenced by Japanese Anime (which I have researched to a great degree[0]). Some animes have _a lot_ of that kind of dialogue. Sometimes it's just bad writing, but other times it is actually extremely useful.

The times where it is useful are crucial to make a film or show, especially live-action, feel like anime. Thought processes like those presented in the article make it seem like all on-the-nose dialogue is bad and in turn, make my job much harder.

[0]: https://www.youtube.com/watch?v=igz7TmsE1Mk

Please recommend some games

Hi there, I'm a fellow filmmaker building my own tools and would love to hear your thoughts and needs. If you'd like (and anyone reading this), please email

Studios at weedonandscott dot com

It also compiles to Javascript, which runs in a lot of places (to say the least). For WebAssembly, see my other comment about Porffor

I use it in production[0] and it's a delight so far. When Porffor[1] is ready you could compile to WASM through JS for self-contained binaries!

[0]: https://blog.nestful.app/p/why-i-rewrote-nestful-in-gleam

[1]: https://porffor.dev/

You're describing Gleam

https://gleam.run

Yes, exactly right. We offer our own paid sync if users would like to save the hassle

It serves more use cases than you might think, especially with CRDTs. Nestful is a tree structure and uses Yjs for sync. Permissions can be done in the file system level.

Yes, I agree this is not an end-all be all solution, but the tradeoff is often worth it.

For the desktop version just watching the directory for changes is enough to achieve that. Nestful is not aware the files are syncing, it just reads files as they are.

I run an offline-first app[0] that has a sync mechanism (over Yjs). To solve server longevity we just sell you a lifetime license of the app and allow for file-based sync.

While I agree with the sentiment of the article most users do not even know what a server is, much less capable of self-hosting. Syncing a folder over Dropbox or Google Drive, though, is simple enough.

[0]: https://nestful.app

Yes. The best way to avoid trouble is build redundancies to it, rather than refine the troublesome part to no end

But aren't app stores are too saturated to the point where it's not much easier to discover apps compared to websites?

Thank you