PageSourceSearch

https://www.rabbitmq.com/assets/js/786b5326.da509f73.js

js rabbitmq.com collected 2026-09-24 06:04:34 UTC 3,504 bytes, 1 lines download raw bytes

1"use strict";(self.webpackChunkrabbitmq_website=self.webpackChunkrabbitmq_website||[]).push([["10875"],{49620(e,t,a){a.r(t),a.d(t,{assets:()=>l,contentTitle:()=>o,default:()=>h,frontMatter:()=>i,metadata:()=>n,toc:()=>u});var n=a(83453),r=a(74848),s=a(28453);let i={title:"Can you hear the drums, Erlando?",tags:["Programming Languages"],authors:["matthew"]},o,l={authorsImageUrls:[void 0]},u=[];function m(e){let t={p:"p",...(0,s.R)(),...e.components};return(0,r.jsx)(t.p,{children:"Most of us at RabbitMQ HQ have spend time working in a number of functional languages in addition to Erlang, such as Haskell, Scheme, Lisp, OCaml or others. Whilst there is lots to like about Erlang, such as its VM/Emulator, there are inevitably features that we all miss from other languages. In my case, having spent a couple of years working in Haskell before returning to the RabbitMQ fold, all sorts of features are \"missing\", such as laziness, type classes, additional infix operators, the ability to specify precedence of functions, fewer parenthesis, partial application, more consistent standard libraries and do-notation. That's a fair list, and it'll take me a while to get around to implementing them all in Erlang, but here are two for starters."})}function h(e={}){let{wrapper:t}={...(0,s.R)(),...e.components};return t?(0,r.jsx)(t,{...e,children:(0,r.jsx)(m,{...e})}):m(e)}},28453(e,t,a){a.d(t,{R:()=>i,x:()=>o});var n=a(96540);let r={},s=n.createContext(r);function i(e){let t=n.useContext(s);return n.useMemo(function(){return"function"==typeof e?e(t):{...t,...e}},[t,e])}function o(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(r):e.components||r:i(e.components),n.createElement(s.Provider,{value:t},e.children)}},83453(e){e.exports=JSON.parse('{"permalink":"/blog/2011/05/17/can-you-hear-the-drums-erlando","editUrl":"https://github.com/rabbitmq/rabbitmq-website/tree/main/blog/2011-05-17-can-you-hear-the-drums-erlando/index.md","source":"@site/blog/2011-05-17-can-you-hear-the-drums-erlando/index.md","title":"Can you hear the drums, Erlando?","description":"Most of us at RabbitMQ HQ have spend time working in a number of functional languages in addition to Erlang, such as Haskell, Scheme, Lisp, OCaml or others. Whilst there is lots to like about Erlang, such as its VM/Emulator, there are inevitably features that we all miss from other languages. In my case, having spent a couple of years working in Haskell before returning to the RabbitMQ fold, all sorts of features are \\"missing\\", such as laziness, type classes, additional infix operators, the ability to specify precedence of functions, fewer parenthesis, partial application, more consistent standard libraries and do-notation. That\'s a fair list, and it\'ll take me a while to get around to implementing them all in Erlang, but here are two for starters.","date":"2011-05-17T00:00:00.000Z","tags":[{"inline":true,"label":"Programming Languages","permalink":"/blog/tags/programming-languages"}],"readingTime":14.96,"hasTruncateMarker":true,"authors":[{"name":"Matthew Sackman","key":"matthew","page":null}],"frontMatter":{"title":"Can you hear the drums, Erlando?","tags":["Programming Languages"],"authors":["matthew"]},"unlisted":false,"prevItem":{"title":"RabbitMQ 2.5.0 released","permalink":"/blog/2011/06/16/rabbitmq-250-released"},"nextItem":{"title":"Very fast and scalable topic routing - part 2","permalink":"/blog/2011/03/28/very-fast-and-scalable-topic-routing-part-2"}}')}}]);

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.