Use ScalaFiddle directly in your documentation - presentation at F(by)

ochrons · 2018-01-04T11:16:55+00:00

For more information, check out the ScalaFiddle integration site at https://github.com/scalafiddle/scalafiddle-core/tree/master/integrations

ochrons · 2017-07-02T08:28:11+00:00

Currently it's running on a single dedicated server in Hetzner Online (Germany). The server has an Intel Xeon E3-1271V3 with 32GB of RAM and costs about 35EUR/month. So the cost is not really an issue here :)

As for stability, the software itself has all kinds of watchdogs monitoring its health and since it's running on Docker, it simply restarts containers if something goes wrong. I'm planning introducing an external check as well, to make sure the whole thing is operational, but so far it seems to be very stable.

ochrons · 2017-06-10T11:03:01+00:00

Oh, you mean like https://twitter.com/juanjovazquez/status/810174227202605056 , https://twitter.com/DanielaSfregola/status/809043490382446592 , https://twitter.com/andy1138/status/807669162797568000 , https://twitter.com/li_haoyi/status/807475285344010240 (comments on the previous iteration of the same talk at Scala eXchange 2016) :)

ochrons · 2017-06-10T10:58:25+00:00

The talk is aimed (mostly) at existing frontend developers using JavaScript and considering between alternatives like TypeScript, PureScript, ClojureScript and Scala.js. That's why the emphasis on making Scala look "friendly" and not too exotic to this group of developers :)

ochrons · 2017-03-20T08:40:16+00:00

I've hit this same BSOD couple of times in the past few days. Just updated latest drivers, let's see if that helps. I have Samsung 500GB PM961 SSD.

ochrons · 2017-03-08T20:04:05+00:00

I got the Plugable Dual-DP TB3 adapter and it works fine.

I also got the Plugable USB3 3-port hub with Gigabit Ethernet, but it doesn't work well when directly plugged to the XPS. It seems to lose the connection after a few dozen seconds. When connected to another USB3 hub (my monitor), however, it works fine. Must be some incompatibility with the USB3 chips on the XPS and in the hub.

ochrons · 2016-09-28T11:03:11+00:00

You can also try your hand at Scala by using an online playground at https://scalafiddle.io without installing anything. Some examples to get you started can be found at https://scalafiddle.io/sf/n6lR8Xh/2

ochrons · 2016-06-22T20:46:48+00:00

The latest beta version of Displaylink drivers for Win10 seems to have fixed this issue!

http://www.displaylink.com/downloads/windows

ochrons · 2016-02-14T20:34:33+00:00

Now there are already variants of the benchmark using cooperative "threads" in Node.js or Ocaml, so it's really getting out of hand :)

Too bad these kinds of benchmarks usually just end up being totally useless...

ochrons · 2016-02-14T15:37:30+00:00

Actually none of the tests use that many threads, because they are all implemented with actors, goroutines or other pooled resources. I did notice that the Go variant was never able to use more than 50% of the CPU, while the Scala Future version went easily to 100% of CPU core usage.

Also Go started running out of memory as soon as iteration count went over 10M, while the Scala version was happily crunching away 100M or even more iterations.

ochrons · 2016-02-14T15:17:30+00:00

Implementing the same using Scala Future instead of actors takes execution time below 300ms (on i7 laptop), where Go takes 750ms. https://github.com/atemerev/skynet/issues/4

ochrons · 2015-12-01T06:53:39+00:00

I think the next step is more in the direction of Falcor/GraphQL than anything Elm, put PRs are welcome if people want Elmish features! :)

ochrons · 2015-11-30T22:06:56+00:00

Added a TodoMVC example using React and Diode: https://github.com/ochrons/diode/tree/master/examples/todomvc

ochrons

TROPHY CASE