Conversation

Notices

1. Embed this notice
   esmevane, sorry (ironchamber@mastodon.esmevane.com)'s status on Wednesday, 10-Jan-2024 07:55:01 JST esmevane, sorry

   in reply to

   • Marco Rogers

   @polotek I feel like observables were a big "a-ha!" moment for me for some stuff, like wrangling noisy event sources? but I've never seen a codebase built on observables-everywhere-for-everything which wasn't just a weird tough to maintain mess

   • Embed this notice
     Marco Rogers (polotek@social.polotek.net)'s status on Wednesday, 10-Jan-2024 07:55:03 JST Marco Rogers

     in reply to

     Oh, I'll add my favorite hot take too. Observables were a mistake. It's way too complicated in practice. And the costs outweigh the supposed benefits in my experience. It's the only thing I really dislike about the Angular ecosystem.

     I know signals are the new hotness. I haven't really looked into it yet. But it feels like everybody else basically started to realize Observables are not great.

   • Embed this notice
     Marco Rogers (polotek@social.polotek.net)'s status on Wednesday, 10-Jan-2024 07:55:04 JST Marco Rogers

     in reply to

     I'm sort of sold on typescript for large projects as well. It has taken a long time for me to get on board. I can't stand all of the cost and headache that comes with going all in on typescript. It has to come with a lot of benefit in order for it to be net positive. The way I understand that benefit today is different from the way people usually describe it. Maybe I'll find a way to talk about that soon.

   • Embed this notice
     Marco Rogers (polotek@social.polotek.net)'s status on Wednesday, 10-Jan-2024 07:55:05 JST Marco Rogers

     in reply to

     It may also be the case that I just don't know how to hack things anymore. Maybe I've spent so much time working on code that needs to be production quality that it's actually easier for me to work within those constraints than without them.

   • Embed this notice
     Marco Rogers (polotek@social.polotek.net)'s status on Wednesday, 10-Jan-2024 07:55:07 JST Marco Rogers

     in reply to

     It feels good to hack something together in a way that feels easy to get started. But a lot of times, you get to a point where continuing to add features feels harder and harder to do. Because you didn't give yourself any of the structure that would've made it easier. There are many reasons that side projects die and never get "finished". But this is definitely one of them.

   • Embed this notice
     Marco Rogers (polotek@social.polotek.net)'s status on Wednesday, 10-Jan-2024 07:55:08 JST Marco Rogers

     in reply to

     I'm sharing this opinion because I'm thinking about development workflows and what contributes to long term maintainability. I'm using Nest and Angular for a side project. It definitely feels like overkill for something that will probably never see the light of day. But I'm also finding that the structure that comes with these tools is allowing me to get a lot further than I usually do with side projects.

   • Embed this notice
     Marco Rogers (polotek@social.polotek.net)'s status on Wednesday, 10-Jan-2024 07:55:09 JST Marco Rogers

     Been using nest.js recently, and I don't hate it. I don't hate Angular as a frontend framework either. And Nest has similar architecture and design principles. A lot of people are gonna back away from this level of complexity. And I get that. But as a person who has spent the last 10 years building long-lived and successful applications that support teams of hundreds of devs, a good opinionated framework is necessary.