Post

I don't think it's just contexts' fault. I think it's also too much boilerplate that's needed to achieve basic stuff and LiveView not being part of the framework + its design with views and components being two different things. It's still the best stack on the planet if you asked me πŸ™ƒ (1/2)

George Millo@georgemillo.bsky.social

Did contexts kill Phoenix? New blog post: arrowsmithlabs.com/blog/did-con...

Its just a tiring debate for the team lol. Before contexts: "We need structure! We need Patterns! How do we use phoenix??" After contexts: "This structure is too much!" Internal debate has been "we can't architect people's projects! People need to think! Modules and Functions is it!"

OO people expect/want more options for organization. FP/Lispy people don't want it. Third weird group want it and don't want it. IMO there are good educational and subjective experience arguments out there and maybe if we made generators easier/more obvious to replace. But hard to know!

πŸ‘Modules πŸ‘Functions Name them w/e you want! Could do it all in top level files if you wanted! one giant file! folder per module! w/e you want its just :"Elixir.Module.Name".function