Developing for the browser platform is so difficult because it's all so dynamic and unpredictable. Elm is SO strongly and statically typed that it is literally impossible to get a runtime exception in elm.
It makes development SO fast, because I know that as long as my code compiles, it will probably behave exactly as I expect it will in every major browser.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
I mean it's not like I don't test code before I ship it, if that's what you're asking, but what I mean is that when I do run it I don't end up spending a lot of time debugging.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
Elm.
Developing for the browser platform is so difficult because it's all so dynamic and unpredictable. Elm is SO strongly and statically typed that it is literally impossible to get a runtime exception in elm.
It makes development SO fast, because I know that as long as my code compiles, it will probably behave exactly as I expect it will in every major browser.
I am probably going to stir up a give of bees, but can you really trust any technology, that level of trust is dangerous.
I mean it's not like I don't test code before I ship it, if that's what you're asking, but what I mean is that when I do run it I don't end up spending a lot of time debugging.
I had the same thoughts about typescript I can relate. Anyways, I'm feeling a bit unwell and maybe have a negative attitude today, excuse me.
Oh, I'm sorry! Get to feeling better!