Comments for Silk Blog http://blog.silkapp.com Silk Blog Mon, 23 Jan 2012 10:22:13 +0000 hourly 1 http://wordpress.org/?v=3.0.5 Comment on Silk completes €320,000 ($475,000) funding round led by Atomico by Smooth As Silk (App) Web Sites - semanticweb.com http://feedproxy.google.com/~r/typlab/comments/~3/h-N5Oe0qeOE/ Smooth As Silk (App) Web Sites - semanticweb.com Mon, 23 Jan 2012 10:22:13 +0000 http://blog.silkapp.com/?p=420#comment-6249 [...] make the semantic web more approachable. Investors seem to agree, as the company last year raised $475,000 in a round led by Atomico – funds it’s applying to expanding its team to include more developers and new design talent. [...] [...] make the semantic web more approachable. Investors seem to agree, as the company last year raised $475,000 in a round led by Atomico – funds it’s applying to expanding its team to include more developers and new design talent. [...]

]]> http://blog.silkapp.com/2011/05/silk-completes-funding-round-led-by-atomico/comment-page-1/#comment-6249 Comment on Silk completes €320,000 ($475,000) funding round led by Atomico by Mark Scholten http://feedproxy.google.com/~r/typlab/comments/~3/kFbSoV5y1Y4/ Mark Scholten Mon, 02 Jan 2012 12:50:38 +0000 http://blog.silkapp.com/?p=420#comment-5790 Congrats. I believe that better/more vizualisation of data is surely the way to go! Congrats. I believe that better/more vizualisation of data is surely the way to go!

]]> http://blog.silkapp.com/2011/05/silk-completes-funding-round-led-by-atomico/comment-page-1/#comment-5790 Comment on Testing Javascript by Erik http://feedproxy.google.com/~r/typlab/comments/~3/rF-BxUERRbI/ Erik Mon, 12 Dec 2011 14:00:19 +0000 http://blog.typlab.com/?p=391#comment-5386 @Oliver: I've made an edit to get the code visible at least. We'll look into getting code coloring working in comments again. Thanks for the report! @Oliver: I’ve made an edit to get the code visible at least. We’ll look into getting code coloring working in comments again. Thanks for the report!

]]> http://blog.silkapp.com/2010/02/testing-javascript/comment-page-1/#comment-5386 Comment on Launch of the first public Silk site: The Next Web Index by José Pedro Magalhães http://feedproxy.google.com/~r/typlab/comments/~3/hTJxFnvoltM/ José Pedro Magalhães Wed, 30 Nov 2011 18:14:29 +0000 http://blog.silkapp.com/?p=431#comment-5132 Thought of submitting this to slashdot? Thought of submitting this to slashdot?

]]> http://blog.silkapp.com/2011/11/launch-of-the-first-public-silk-site-the-next-web-index/comment-page-1/#comment-5132 Comment on Launch of the first public Silk site: The Next Web Index by pjw http://feedproxy.google.com/~r/typlab/comments/~3/vZAPYEfA8hg/ pjw Tue, 29 Nov 2011 19:56:41 +0000 http://blog.silkapp.com/?p=431#comment-5115 Congrats, the technolog being built at silk is interesting. Congrats, the technolog being built at silk is interesting.

]]> http://blog.silkapp.com/2011/11/launch-of-the-first-public-silk-site-the-next-web-index/comment-page-1/#comment-5115 Comment on Testing Javascript by Oliver http://feedproxy.google.com/~r/typlab/comments/~3/IOVUq6fOxuo/ Oliver Mon, 21 Nov 2011 10:32:02 +0000 http://blog.typlab.com/?p=391#comment-4979 Is the qunit/quickcheck wrapper code still available? I'm not sure that "::CODECOLORER_BLOCK_13::" is quite it! Is the qunit/quickcheck wrapper code still available? I’m not sure that “::CODECOLORER_BLOCK_13::” is quite it!

]]> http://blog.silkapp.com/2010/02/testing-javascript/comment-page-1/#comment-4979 Comment on Silk completes €320,000 ($475,000) funding round led by Atomico by Ben Gras http://feedproxy.google.com/~r/typlab/comments/~3/AoVpPXruQio/ Ben Gras Thu, 17 Nov 2011 15:51:01 +0000 http://blog.silkapp.com/?p=420#comment-4922 Great job, congratulations and may your business do well! If you ever show up to or organise a social thing I'll visit. Great job, congratulations and may your business do well! If you ever show up to or organise a social thing I’ll visit.

]]> http://blog.silkapp.com/2011/05/silk-completes-funding-round-led-by-atomico/comment-page-1/#comment-4922 Comment on Why we use Haskell by Eklerks http://feedproxy.google.com/~r/typlab/comments/~3/GwuRitkU1eY/ Eklerks Wed, 26 Oct 2011 16:52:14 +0000 http://blog.typlab.com/?p=68#comment-4670 @Andrew Bettison At our company we use Snap -haskell web framework- and it is actually quite easy to create very complex software. We wrote our own connection pool -for the database and the application servers-, (realtime) monitoring software, a proxy server/load-balancer, a special monad in which database transactions are enforced, all kind of concurrent data structures etc. Especially concurrency (with STM) is a breeze. Before that we rolled our own webserver, but Snap does a better job, so we abandoned it. The proxy server is really efficient, it adds, under normal load, a lag of 5 ms to the response of the backend servers. -Same network- Thanks to enumerators, the body of the request is send to the backend servers before we received to whole request from the client. All things you wouldn't dare to do in most of the script languages, for e.g. sake of stability and maintainability, are actually easy in haskell. For web development haskell is a very sound choice. Finding programmers is difficult, but most people with a mathematical background pick it up quickly. @Andrew Bettison

At our company we use Snap -haskell web framework- and it is actually quite easy to create very complex software. We wrote our own connection pool -for the database and the application servers-, (realtime) monitoring software, a proxy server/load-balancer, a special monad in which database transactions are enforced, all kind of concurrent data structures etc. Especially concurrency (with STM) is a breeze.

Before that we rolled our own webserver, but Snap does a better job, so we abandoned it.

The proxy server is really efficient, it adds, under normal load, a lag of 5 ms to the response of the backend servers. -Same network- Thanks to enumerators, the body of the request is send to the backend servers before we received to whole request from the client.

All things you wouldn’t dare to do in most of the script languages, for e.g. sake of stability and maintainability, are actually easy in haskell.

For web development haskell is a very sound choice. Finding programmers is difficult, but most people with a mathematical background pick it up quickly.

]]> http://blog.silkapp.com/2009/09/why-we-use-haskell/comment-page-1/#comment-4670 Comment on Why we use Haskell by Erik http://feedproxy.google.com/~r/typlab/comments/~3/NvGSNRG7qjg/ Erik Tue, 11 Oct 2011 22:04:20 +0000 http://blog.typlab.com/?p=68#comment-4345 @Mac: We never seriously considered Scala. We do think it's an interesting and worthwhile language. Like F#, a functional language on a platform with lots of libraries has lots of potential. They're not pure, though, which gives us a lot. As an example, Haskell is the only language so far where STM works. @Mac: We never seriously considered Scala. We do think it’s an interesting and worthwhile language. Like F#, a functional language on a platform with lots of libraries has lots of potential. They’re not pure, though, which gives us a lot. As an example, Haskell is the only language so far where STM works.

]]> http://blog.silkapp.com/2009/09/why-we-use-haskell/comment-page-1/#comment-4345 Comment on Why we use Haskell by Mac http://feedproxy.google.com/~r/typlab/comments/~3/Qjwee1LvoSE/ Mac Tue, 11 Oct 2011 16:07:39 +0000 http://blog.typlab.com/?p=68#comment-4328 Did you ever consider Scala? If yes why did you choose Haskel, was it because you were already familiar with it or there are some advantages? Thanks for the insightful post and good luck! Did you ever consider Scala? If yes why did you choose Haskel, was it because you were already familiar with it or there are some advantages? Thanks for the insightful post and good luck!

]]> http://blog.silkapp.com/2009/09/why-we-use-haskell/comment-page-1/#comment-4328 Comment on Haskell data types and XML by Maurice http://feedproxy.google.com/~r/typlab/comments/~3/YVvDmof5nww/ Maurice Mon, 18 Jul 2011 11:33:15 +0000 http://blog.typlab.com/?p=15#comment-3413 Hi Sebas, thanks your your reply. Sorry, you just tickled my curiosity. Could you provide some details about what graph-database you used and what the simple-sparql language is you use, and why you have made these choices? I would love to learn more about what is pragmatic and 'gangbaar'[nl] these days. kind regards Hi Sebas, thanks your your reply.

Sorry, you just tickled my curiosity. Could you provide some details about what graph-database you used and what the simple-sparql language is you use, and why you have made these choices?
I would love to learn more about what is pragmatic and ‘gangbaar’[nl] these days.

kind regards

]]> http://blog.silkapp.com/2009/09/haskell-data-types-and-xml/comment-page-1/#comment-3413 Comment on Haskell data types and XML by Sebas http://feedproxy.google.com/~r/typlab/comments/~3/4P8FQWlT7UM/ Sebas Mon, 11 Jul 2011 15:44:03 +0000 http://blog.typlab.com/?p=15#comment-3325 Hi Maurice, You are right, this post is a bit dated, we don't use XML anymore as the storage for assertions. We use a separate graph-database now that encodes the semantic information, structured similar to RDF. We don't use SPARQL itself, but a similar much simpler query language. Hi Maurice,

You are right, this post is a bit dated, we don’t use XML anymore as the storage for assertions. We use a separate graph-database now that encodes the semantic information, structured similar to RDF. We don’t use SPARQL itself, but a similar much simpler query language.

]]> http://blog.silkapp.com/2009/09/haskell-data-types-and-xml/comment-page-1/#comment-3325 Comment on Haskell data types and XML by Maurice http://feedproxy.google.com/~r/typlab/comments/~3/YK75KLFUXDk/ Maurice Sun, 10 Jul 2011 20:32:48 +0000 http://blog.typlab.com/?p=15#comment-3315 hi sebas and erik, Great work going on at silk! I have seen your silkapp appeared om the TNW.com website. Yet these articles are very dated. So what's up? The question: The data you are crunching are assertions in nature. So why use an XML database and not using a tripplestore using RDF? XML needs a strict data model, if new assertions are made, different from the specification in your internal datamodel, it would be more difficult to insert new data, and relate this data to existing assertions in your database. I know the strictness of XML is easy to use with; you get what you asked for because the system 'knows' that to expect. Yet this would make it very labor intensive task to insert new data and unexpected assertions beyond your wildest dreams, offering the user a whole lot more then the data in the datamodel specification. For example the user can be offered more assertions from the databases in the linkeddata cloud. The drawback of this, I guess, it is harder to create a neat user interface, and overwhelming the end-user with the richness. Well, please leave a note about your thoughts using RDF and SPARQL services. kind regards hi sebas and erik,
Great work going on at silk! I have seen your silkapp appeared om the TNW.com website.
Yet these articles are very dated. So what’s up?

The question: The data you are crunching are assertions in nature. So why use an XML database and not using a tripplestore using RDF?

XML needs a strict data model, if new assertions are made, different from the specification in your internal datamodel, it would be more difficult to insert new data, and relate this data to existing assertions in your database.
I know the strictness of XML is easy to use with; you get what you asked for because the system ‘knows’ that to expect.
Yet this would make it very labor intensive task to insert new data and unexpected assertions beyond your wildest dreams, offering the user a whole lot more then the data in the datamodel specification. For example the user can be offered more assertions from the databases in the linkeddata cloud. The drawback of this, I guess, it is harder to create a neat user interface, and overwhelming the end-user with the richness.
Well, please leave a note about your thoughts using RDF and SPARQL services.

kind regards

]]> http://blog.silkapp.com/2009/09/haskell-data-types-and-xml/comment-page-1/#comment-3315 Comment on Reinventing XSLT in pure Javascript by From XSLT to Javascript, via Combinators, Monads and Arrows http://feedproxy.google.com/~r/typlab/comments/~3/-yn-9-rSk7Q/ From XSLT to Javascript, via Combinators, Monads and Arrows Sat, 04 Jun 2011 19:55:24 +0000 http://blog.typlab.com/?p=188#comment-2815 [...] A really thought provoking article from this Amsterdam-based startup. Warning: some knowledge of functional programming recommended. [...] [...] A really thought provoking article from this Amsterdam-based startup. Warning: some knowledge of functional programming recommended. [...]

]]> http://blog.silkapp.com/2009/12/reinventing-xslt-in-pure-javascript/comment-page-1/#comment-2815 Comment on Why we use Haskell by Nick van der Veeken http://feedproxy.google.com/~r/typlab/comments/~3/enNz2SammGU/ Nick van der Veeken Tue, 24 May 2011 23:40:17 +0000 http://blog.typlab.com/?p=68#comment-2655 Just came back from a tech talk on Scala by the inventor himself, Martin Odersky. He proudly explained how Twitter, LinkedIn and many other large-on-the-net companies use Scala for their backend and how for Twitter this meant saying goodbye to the fail whale that Ruby had brought them. Just saying: It's proven technology. Porting code from Haskell to Scala should be easy, since you are working functionally already. But anyhow, happy coding ;-) Just came back from a tech talk on Scala by the inventor himself, Martin Odersky. He proudly explained how Twitter, LinkedIn and many other large-on-the-net companies use Scala for their backend and how for Twitter this meant saying goodbye to the fail whale that Ruby had brought them. Just saying: It’s proven technology.

Porting code from Haskell to Scala should be easy, since you are working functionally already.

But anyhow, happy coding ;-)

]]> http://blog.silkapp.com/2009/09/why-we-use-haskell/comment-page-1/#comment-2655 Comment on How I Learned to Stop Worrying and Love Web Development Again by F http://feedproxy.google.com/~r/typlab/comments/~3/ppQV8A_Mq6A/ F Wed, 04 May 2011 16:39:47 +0000 http://blog.typlab.com/?p=152#comment-2426 I envy you I envy you

]]> http://blog.silkapp.com/2009/10/love-web-development-again/comment-page-1/#comment-2426 Comment on Why we use Haskell by Erik http://feedproxy.google.com/~r/typlab/comments/~3/NnpQ9Yteq_4/ Erik Mon, 02 May 2011 09:33:43 +0000 http://blog.typlab.com/?p=68#comment-2404 @Matt: We were already familiar with Haskell, I think that influenced our choice the most. But another reason is that OCaml, F# and Scala are impure by default, which removes one of the advantages of Haskell and prohibits some techniques (e.g. STM). I also think Haskell's community is larger at the moment, though with Scala and F# you have the benefit of existing Java and .NET libraries. @Matt: We were already familiar with Haskell, I think that influenced our choice the most. But another reason is that OCaml, F# and Scala are impure by default, which removes one of the advantages of Haskell and prohibits some techniques (e.g. STM). I also think Haskell’s community is larger at the moment, though with Scala and F# you have the benefit of existing Java and .NET libraries.

]]> http://blog.silkapp.com/2009/09/why-we-use-haskell/comment-page-1/#comment-2404 Comment on Why we use Haskell by Erik http://feedproxy.google.com/~r/typlab/comments/~3/Rqthbe1OYlE/ Erik Mon, 02 May 2011 09:30:28 +0000 http://blog.typlab.com/?p=68#comment-2403 @Chad: We use Happstack. See <a href="http://www.reddit.com/r/haskell/comments/gzdtf/filter_and_visualize_data_in_seconds_with_silk/c1rjz0v" rel="nofollow">Sebas' answer on reddit</a> for more details. @Chad: We use Happstack. See Sebas’ answer on reddit for more details.

]]> http://blog.silkapp.com/2009/09/why-we-use-haskell/comment-page-1/#comment-2403 Comment on Why we use Haskell by Andrew Bettison http://feedproxy.google.com/~r/typlab/comments/~3/g88sxXDOeqM/ Andrew Bettison Fri, 29 Apr 2011 23:00:46 +0000 http://blog.typlab.com/?p=68#comment-2380 You are early adopters, and you will suffer for it, so you have my best wishes and condolences at the same time. I think that in the long run, pure functional languages like Haskell will be our way out of the software complexity "crisis" (and into the next one :-), so your decision is progressive and deserves respect. You are early adopters, and you will suffer for it, so you have my best wishes and condolences at the same time. I think that in the long run, pure functional languages like Haskell will be our way out of the software complexity “crisis” (and into the next one :-), so your decision is progressive and deserves respect.

]]> http://blog.silkapp.com/2009/09/why-we-use-haskell/comment-page-1/#comment-2380 Comment on Why we use Haskell by Clint Moore http://feedproxy.google.com/~r/typlab/comments/~3/GQMxby--BNM/ Clint Moore Fri, 29 Apr 2011 17:21:32 +0000 http://blog.typlab.com/?p=68#comment-2376 From one startup who has committed to going with haskell to another, we wish you the best of luck. From one startup who has committed to going with haskell to another, we wish you the best of luck.

]]> http://blog.silkapp.com/2009/09/why-we-use-haskell/comment-page-1/#comment-2376