I know that it's common to have namespace collisions, but their logo is so similar to Reason magazine's. https://reason.com/
Reason: A new interface to OCaml
51–60 of 294 posts
Re: Reason: A new interface to OCaml
#52I know that it's common to have namespace collisions, but their logo is so similar to Reason magazine's. https://reason.com/
Re: Reason: A new interface to OCaml
#53Earlier quoted context omitted.
I was curious why it doesn't scroll. Barely works but gives a CPU spike and just jumps around between pages...
Chrome and Safari both worked for me. Common reports about Firefox, so I disabled the gif. Can you let me know if it works now?
Re: Reason: A new interface to OCaml
#54Re: Reason: A new interface to OCaml
#55Website fries the CPU (FF).
Sounds like FF can't handle gifs, but Chrome/Safari do a good job. I've disabled the gif on the main page just to be friendly to FF while I figure out a better approach. Thanks for the report.
Is there any interactive functionality that your website offers that would justify extraordinary demands or does it simply display some text and images?
Re: Reason: A new interface to OCaml
#56Re: Reason: A new interface to OCaml
#57Re: Reason: A new interface to OCaml
#58I know that it's common to have namespace collisions, but their logo is so similar to Reason magazine's. https://reason.com/
There's also a DAW called Reason: https://en.wikipedia.org/wiki/Reason_%28software%29
Re: Reason: A new interface to OCaml
#59This page is completely unusable due to lag. From the other comments it seems this is FF specific. One would think FB would have the resources to test new pages at least on common browsers before publishing. Edit: The fix came quickly though.
Re: Reason: A new interface to OCaml
#60This page is completely unusable due to lag. From the other comments it seems this is FF specific. One would think FB would have the resources to test new pages at least on common browsers before publishing. Edit: The fix came quickly though.
While not cool, that's a pleasant surprise to see something made-first for FF! Glad to see people still fighting against browser mono-culture. Disclaimer: This post was written in Chrome.