The techs and popular frameworks are changing so fast in browser land that tooling hasn’t had time to solidify. So everybody stitches together their own custom build process despite the heroic efforts of folks like Parcel and Create Elm App. I lasted approximately 2 hrs with CEA before ejecting and customizing.
Still, I’d rather be doing web front end than desktop or native front end. Mainly because of Elm... I don’t ever want to have to learn another UI framework’s weird abstractions.
But yeah, server side is good too. I like writing APIs.
Yeah I really enjoy Elm, but its sparked my interest in learning Haskell, and the reason I didn't jump into that before was because is less easy to create a web UI front end... however now I don't know if that is really a set back for me haha.
Do you have a boilerplate you like to start with for Elm apps to get you going now? Or do you still mainly try to copy a new one for each new project?
I was using a starter template, but the author since stopped maintaining it. The most recent thing I used was Create Elm App. Big win with that is that it sets up debugging for you. So you can see the state of the model after each message and go back to examine a previous state. I knew it was out there, but I had never used it before.
I did have to modify CEA builds to turn off things I didn't want. For instance, this app will be internal and requires a live API, so it does not make sense to use a service worker / PWA. (I can see the caching resulting in support calls.) There's no configuration to turn it off, so I had to eject and change some build scripts. (I made notes because Future Me will forget what exactly to do.)
I will probably continue to use CEA going forward because it does so many thing right.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The techs and popular frameworks are changing so fast in browser land that tooling hasn’t had time to solidify. So everybody stitches together their own custom build process despite the heroic efforts of folks like Parcel and Create Elm App. I lasted approximately 2 hrs with CEA before ejecting and customizing.
Still, I’d rather be doing web front end than desktop or native front end. Mainly because of Elm... I don’t ever want to have to learn another UI framework’s weird abstractions.
But yeah, server side is good too. I like writing APIs.
Yeah I really enjoy Elm, but its sparked my interest in learning Haskell, and the reason I didn't jump into that before was because is less easy to create a web UI front end... however now I don't know if that is really a set back for me haha.
Do you have a boilerplate you like to start with for Elm apps to get you going now? Or do you still mainly try to copy a new one for each new project?
I was using a starter template, but the author since stopped maintaining it. The most recent thing I used was Create Elm App. Big win with that is that it sets up debugging for you. So you can see the state of the model after each message and go back to examine a previous state. I knew it was out there, but I had never used it before.
I did have to modify CEA builds to turn off things I didn't want. For instance, this app will be internal and requires a live API, so it does not make sense to use a service worker / PWA. (I can see the caching resulting in support calls.) There's no configuration to turn it off, so I had to eject and change some build scripts. (I made notes because Future Me will forget what exactly to do.)
I will probably continue to use CEA going forward because it does so many thing right.