Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The JavaScript Problem

haskell.org

Post reply on HN
Print view View original

1–10 of 183 posts

Re: The JavaScript Problem

#2

Post by jnbiche »

I'm surprised that Elm is not mentioned:

http://elm-lang.org/edit/examples/Reactive/ZipCodes.elm

True, it's not Haskell, but it's clearly highly-influenced by Haskell. Besides, they mention Fay, which isn't Haskell, either.

If the Haskell wiki didn't require a log-in and registration that requires special, personal permission, I'd add it myself.

Re: The JavaScript Problem

#3

Post by strager »

jnbiche wrote: post #2

I'm surprised that Elm is not mentioned: http://elm-lang.org/edit/examples/Reactive/ZipCodes.elm True, it's not Haskell, but it's clearly highly-influenced by Haskell. Besides, they mention Fay, which isn't Haskell, either. If the Haskell wiki didn't require a log-in and registration that requires special, personal permission, I'd add it myself.

It's a wiki. You are free to add this information. =]

Re: The JavaScript Problem

#4

Post by WoodenChair »

Pretty strange to mention TypeScript and not Dart... which solves a lot of his criticisms and is arguably more popular. I respect the functional guys a great deal but the use of Haskell for front-end dev is realistically going to only be an interesting option for those already using it for the backend. It has nothing to do with the merits of the solution and everything to do with people's comfort zones.

Re: The JavaScript Problem

#5

Post by jnbiche »

strager wrote: post #3
jnbiche wrote: post #2

I'm surprised that Elm is not mentioned: http://elm-lang.org/edit/examples/Reactive/ZipCodes.elm True, it's not Haskell, but it's clearly highly-influenced by Haskell. Besides, they mention Fay, which isn't Haskell, either. If the Haskell wiki didn't require a log-in and registration that requires special, personal permission, I'd add it myself.

It's a wiki. You are free to add this information. =]

Did you not read my last sentence? I'm actually not free to add the information. There's a special registration process that requires human intervention.

If the Haskell Wiki didn't require me to e-mail somebody personally and ask for permission to register, I'd be much more inclined to provide a one-of edit. By the time this person gets back to me (he's probably in Europe), I'll have neither the time nor inclination to make a one-time edit to a wiki that I've only visited on a handful of occasions.

I gnome-edit wikis all the time -- at least the ones with user-friendly sign-ups. Was the Haskell Wiki so beset by viagra spammers that it had to institute a human-mediated registration process? Maybe it was, but the downside is that then people like me are less likely to register for one-off edits.

Re: The JavaScript Problem

#6

Post by dfkf »

WoodenChair wrote: post #4

Pretty strange to mention TypeScript and not Dart... which solves a lot of his criticisms and is arguably more popular. I respect the functional guys a great deal but the use of Haskell for front-end dev is realistically going to only be an interesting option for those already using it for the backend. It has nothing to do with the merits of the solution and everything to do with people's comfort zones.

The page is about JS. TS is a superset of JS, and Dart is an entirely different language.

Re: The JavaScript Problem

#7

Post by jbdeboer »

dfkf wrote: post #6
WoodenChair wrote: post #4

Pretty strange to mention TypeScript and not Dart... which solves a lot of his criticisms and is arguably more popular. I respect the functional guys a great deal but the use of Haskell for front-end dev is realistically going to only be an interesting option for those already using it for the backend. It has nothing to do with the merits of the solution and everything to do with people's comfort zones.

The page is about JS. TS is a superset of JS, and Dart is an entirely different language.

The article starts with the assertion "We need Javascript". Adding Dart to the mix makes that assertion less obvious.

Re: The JavaScript Problem

#8

Post by dpratt »

I'm going to chime in to the chorus of "Why wasn't X mentioned" and throw out Scala.js.

It would seem that Scala solves quite a few of the article's complaints about Javascript, and in a manner that is accessible and usable for the masses. I love Haskell as much as the next guy, but I'd rather use Scala if i need to get stuff done.

Re: The JavaScript Problem

#10

Post by girvo »

I've been trying to convince my workmates to try something other than pure JS (with Angular), but am not having much luck. TypeScript seems to have the most buy-in, but most of the guys in the office aren't convinced of the benefits of a proper type system, the just see it as more work for them for little upside. Any ideas?
Post reply on HN