3 ms·

I'm sorry for being blunt, but if you are mistaking a database server being down (or CDN issues, or faulty backend code, or...) with the frontend code misbehavi

I'm sorry for being blunt, but if you are mistaking a database server being down (or CDN issues, or faulty backend code, or...) with the frontend code misbehaving then either you are very ignorant to how "computers" work or you are being (very) intellectually disonest. Don't do that. For the record: yes, as much as it may sound bold or marketing-y, the statement is mostly true. You can have runtime errors if you write a bad regex though. After almost 3 years working full-time with Elm on a daily basis, I have not faced a single runtime error. And by the way, this is coming from someone who moved away from Elm for the same reasons mentioned throughout this thread, so I'm definitely not an "Elm fan boy", but I do vouch for this programmer's statement.

gregopet 4y ago
I'm not ignorant of the difference, but at the end of the day, what's the difference? It was definitely Elm throwing that error and they certainly weren't adding "well, for the frontend part anyway, you're out of luck for the rest, lol". And even if we stay on the frontend, I've been doing web development for a long long time and I've seen some weird things. Are you telling me that Elm will catch the user's local storage becoming full? An AJAX URL being blacklisted? Chromium playing tricks with your DOM because it found a field entitled "username"? You have to catch all these things, like in every other language. Sure, the mechanism may differ; you may have Java style mandatory exceptions, or Go style error status that you can check. It may be done reasonably better than with competing languages. But there are no magic bullets and I don't appreciate being mislead that there are, and _certainly_ not with a holier than thou attitude. I'm not saying Elm is bad, I was merely recounting a personal anecdote that for better or for worse prevented me from experiencing Elm.

gregopet 4y ago

I'm not ignorant of the difference, but at the end of the day, what's the difference? It was definitely Elm throwing that error and they certainly weren't adding "well, for the frontend part anyway, you're out of luck for the rest, lol". And even if we stay on the frontend, I've been doing web development for a long long time and I've seen some weird things. Are you telling me that Elm will catch the user's local storage becoming full? An AJAX URL being blacklisted? Chromium playing tricks with your DOM because it found a field entitled "username"? You have to catch all these things, like in every other language. Sure, the mechanism may differ; you may have Java style mandatory exceptions, or Go style error status that you can check. It may be done reasonably better than with competing languages. But there are no magic bullets and I don't appreciate being mislead that there are, and _certainly_ not with a holier than thou attitude. I'm not saying Elm is bad, I was merely recounting a personal anecdote that for better or for worse prevented me from experiencing Elm.