plus you feel elm's value as a tool as you use it, not from the line count at the end. how do those frameworks help you track down bugs when making a big change? how do they help you model your problem in a way that weird runtime bugs don't sneak in unexpectedly?
On Thu, Jun 9, 2016, 10:11 Peter Damoc <[email protected]> wrote: > Lines of code are important but are not always the best metric. > > Elm code explodes quickly when it comes to Lines of Code because of > records and type annotations and let notations. > > A lot of that code could be written in a way that would minimize the lines > of code but it hurts readability. > > > > On Thu, Jun 9, 2016 at 4:27 PM, António Ramos <[email protected]> > wrote: > >> I like the idea of elm but the todo mvc example has too many lines of >> compared to some js frameworks like vuejs canjs and others. >> My goal finding other js alternatives is to also code less. >> >> Elm has many good ideas but why should i code more if i can do the same >> with less? >> >> 2016-05-13 17:50 GMT+01:00 Rex van der Spuy <[email protected]>: >> >>> >>>> So what's the use case of ELM? I feel like I am in the middle of >>>> building my deck with hammer and nails and people keep making new tools and >>>> throwing them at me - screws, screwdrivers, staples, staplers, power >>>> drills. I am confused about knowing when to use what. I have so many such >>>> 'design questions' for example - why should i bother with Redis when I can >>>> write and read json files right from my webpage into local storage. Maybe >>>> there is a place where these 'design' decisions are spelled out so we do >>>> not have to reinvent the wheel every time. I would be grateful. >>>> >>>> >>> Hi Stefan, >>> >>> Imagine that you're living in a world without hammers or nails. >>> But, you need to nail two planks together. >>> How do you do it? >>> >>> That's the kind of world the web-development is in now. >>> Nobody has yet invented the hammer or nail of software. >>> And so we find ourselves in the midst of a wild, multi-decades long >>> Cambrian explosion of evolutionary experimentation with tooling. >>> Will the fundamental hammer and nail of software eventually emerge? >>> >>> Elm is in part a back-to-basic attempt to help find an answer. >>> What's the simplest, easiest most reliable and most fun way to build >>> software? >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Elm Discuss" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Elm Discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > There is NO FATE, we are the creators. > blog: http://damoc.ro/ > > -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
