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

The New Haskell.org

haskell.org

Post reply on HN
Print view View original

91–100 of 110 posts

Re: The New Haskell.org

#91

Post by pilgrim689 »

hristov wrote: post #77

It looks good, but they have to get rid of the out of focus photo. Photos that are entirely out of focus are really annoying and give a lot of people headaches. Usually out of focus areas should be used to bring the eye to an object in the photo that is in focus. But if such an object does not exist, then the eye wanders and tries to adjust itself to focus (the eye has its own focusing mechanism). But of course it ca…

I agree... I didn't even realize there was a videos section between the "Try it" and the "Features" section until I read your comment.

Re: The New Haskell.org

#92

Post by grey-area »

dmit wrote: post #65
grey-area wrote: post #33

Earlier quoted context omitted.

Presumably the idea is that you can prevent your site having broken internal links by constructing links with data types and checking the links when creating them at compile time. You could actually do something similar in most languages, even dynamic ones, so I don't see what is specific to haskell about it, e.g. rails has link_to and friends which require you to have a route set up in order to link to it (though no…

Let's be fair here, while you can detect invalid internal links in dynamic languages at runtime, the end result is basically the same for the user - a 404 or a 503 are equally bad in this case. That's the advantage of compiled languages over dynamic ones in these kinds of scenarios: you sacrifice immediate feedback during development to gain a guarantee from the compiler that all invariants you embedded in the applic…

Users of dynamic languages tend to use tests to check for errors that stronger types might catch (like broken links), but I agree having a formal guarantee is a slight advantage, though not specific to Haskell. Golang for example could easily provide similar checking.

The linked website is beautifully done, and the language does look interesting, I just find the hyperbole about static types making websites magically secure a little over-egged - it's still easy to mess up security or create subtle bugs even if you have strong guarantees about some parts of your code at compile time provided by types.

Re: The New Haskell.org

#93

Post by andrewchambers »

scottjad wrote: post #35

This redesign appears to take the position: the first page on haskell.org is for people who are brand new to the language, not for people who are already learning the language or currently use the language. I don't like that choice. I think the page should be trying to be the most useful for users of the language with a link to an About or Getting Started page that is geared toward new users. To me, a user of the lan…

Obviously they want to stop any thoughts that haskell is a dated language, and they want to hook new people in at a faster rate.

Veteran users don't need any more encouragement.

Re: The New Haskell.org

#94

Post by runeks »

chrisdotcode wrote: post #14

This new, awesome site is using the framework Yesod[0], which is kinda like the Rails of the Haskell world, only it can do rad stuff like prevent XSS and 404s at compile time . Yes, you read that right. [0] http://www.yesodweb.com/

How does it prevent XSS?

Re: The New Haskell.org

#95

Post by QuixoticChris »

runeks wrote: post #94
chrisdotcode wrote: post #14

This new, awesome site is using the framework Yesod[0], which is kinda like the Rails of the Haskell world, only it can do rad stuff like prevent XSS and 404s at compile time . Yes, you read that right. [0] http://www.yesodweb.com/

How does it prevent XSS?

2. XSS injection. Any html coming back from a form will be efficiently sanitized just once on arrival. Unsanitized strings will be sanitized before being displayed.

http://www.yesodweb.com/page/about

I suspect this is accomplished through safe vs. unsafe types. Imagine the only function from `unsafe___` to `safe___` is the escape function, and all functions giving text back in responses is require to be of type `safe___`.

Re: The New Haskell.org

#96

Post by ghc »

bonn1 wrote: post #8

Out of curiosity: Who has written Haskell & deployed to production in the last 24h and if yes for what kind of app?

I have, for data-flow analysis software.

Haskell gets used in the oddest places, where one of two things is true:

    1. Nothing else works (with reasonable LOC *and* performance)
    2. The safety of an advanced type system is required
I'm not optimistic about Haskell appearing anywhere else for the time being, so I think it will stay an "exotic" language for awhile longer.

Re: The New Haskell.org

#99

Post by chrisdone »

shaunxcode wrote: post #98

Small thing but the favicon should be updated to look crisp on retina displays.

Huh, thanks for noticing. I have a retina display but on Linux Chrome and Firefox both ignore any kind of global font size settings for their tabs, so the icons are tiny and look crisp, didn't realise. That kind of thing bugs me too. The rest of the layout itself should be retina-friendly, though, as I developed it like that.

Re: The New Haskell.org

#100

Post by chrisdone »

iopq wrote: post #67

λ do line > л mueval-core: Imports.hs: removeLink: does not exist (No such file or directory) ExitFailure 1 What did I do wrong?

You did nothing wrong, the hundreds of active users due to announcement buzz is a little outside the scope of the sandbox's capabilities, it has some race condition under heavy load. We considered spending time optimizing this in anticipating of the announcement, but more pressing issues took priority. Re-running the line should work.
Post reply on HN