Matthew de Detrich (@mdedetrich) profile picture
Joined August 2016
Photo by Matthew de Detrich (@mdedetrich)Photo by Matthew de Detrich (@mdedetrich)Photo by Matthew de Detrich (@mdedetrich)
It's an irony that most programmers have the patience to learn giant Java frameworks but would not spend time to learn ownership in Rust, laziness in Haskell or compositionality in OCaml or Scala ..
Rust is NOT a hard language. Most people just don't have the patience to learn ownership properly.
8
13
4
162
10,170
Matthew de Detrich retweeted
Apache Pekko 1.1.0 has been released. There has been quite a lot of changes so best to read the changelog at pekko.apache.org/docs/pekko/… Thanks everyone for the hard work that was done in making this release!
11
27
918
Good article on why I will never consider writing Go. You can use simple tools to solve simple problems. I don't want to solve simple problems. The reason why go is evolving the way its described is because you sooner or later hit a barrier of what you can do with "simple" language. Go scales super well with people, it doesn't scale with domain complexity. With more complex problems and domain you need richer and richer abstractions to tame that complexity. You can't build those abstractions in a simple language. You could say "just focus on business problems!". But I do. And I still need abstractions. If I build accounting system, I cannot just throw bunch of integers together and call it a day. I need to model accounts, ledgers, charts of accounts, type of accounts, movements between accounts, enforce accounting equation, enforce non-zero amounts and do myriad of other things. I cannot do that without abstractions. I cannot do that with go. At least not with the standards I expect. valyala.medium.com/go-evolve…
1
7
3
53
4,674
Greatest scene & writing of all time #MontyPython
610
7,573
897
36,078
3,107,682
Matthew de Detrich retweeted
Apache Pekko has graduated from Apache Incubator and is now a TLP (Top Level Project) lists.apache.org/thread/grl5… Thanks to everyone who participated and helped make this happen.
46
3
108
9,625
We have seen a release of each of 4 (sic!) supported major #Scala versions. Scala is alive and kicking!
#ScalaCLI v1.2.0 is out now! Major updates include: • Support for Scala 3.4.0, 3.3.3, 2.13.13 & 2.12.19 (we've been busy!) • Scala Next (3.4.0) is now the default • The LTS tag now points to Scala 3.3.3 • Remapping EsModule imports at link time with Scala.js is a breeze now👇
1
3
1
21
2,250
Matthew de Detrich retweeted
This looks like the most intuitive validation and newtype library I have seen in Scala!
NEOTYPE — A High-Speed Tour
1
7
40
2,286
Matthew de Detrich retweeted
Apache Pekko 1.0.3-M1 is released! Ordinarily I wouldn't make an announcement for a patch release but this one is special because the major headline change is the capability to migrate from Akka to Pekko clusters as a rolling upgrade (see cwiki.apache.org/confluence/…).
1
4
19
858
Word
I talk to a disappointingly large amount of people that cannot comprehend that I can work on something for the joy of it and not any long term financial play.
10
232
Matthew de Detrich retweeted
#Slick 3.5.0-RC1 is out! github.com/slick/slick/relea… Slick is an advanced, comprehensive database access library for #Scala with strongly-typed, highly composable APIs. Version 3.5.0 adds support for Scala 3, batch inserts, and other improvements and bug fixes.
8
22
1,148
Big Scala Hiring at SwissBorg! TL;DR: Seeking 6 Senior Scala Developers. 60-95k/year + perks. Fully remote in Europe. - Looking for 6 Scala Developers to join 3 teams: DIY Investment, Identity, Loyalty. - Seeking Senior I candidates, expectations aligned with Etsy Career Ladder. We are ok with slightly less or more experienced candidates. - Salary: 60-95k/year + bi-yearly bonus + 25 days of PTO + all bank holidays (based on the country of residence) + training + upcoming VSOP program. - Hiring remotely in EU time zones (excluding some countries due to legal reasons). - We’re a 200-employee wealth management platform focused on crypto, aiming to simplify advanced investment products for everyone. Looking for candidates with an interest in the crypto market. - - Our backend is entirely in Scala (>1M LOC) and we are strongly committed to the language. Application process: intro call, tech challenge, tech interview, culture-fit interview, final interview. I’m more than happy to answer any questions you might have! I’m an engineer myself and not a hiring manager here but I should have a lot of answers jobs.lever.co/swissborg/3ee0… Other adjacent roles we are looking for - Data Engineer - Senior QA Engineer - Senior SRE jobs.lever.co/swissborg
5
22
1
64
9,167
Matthew de Detrich retweeted
Event Sourcing and Message Streaming are NOT the same things. Kafka is NOT suitable for Event Sourcing. Kafka is suitable for Message Streaming. There are important reasons why these two different things require *different storage mechanics*. I'm going to simplify this by naming the two different kinds of storage: 1. Event Sourcing requires a *database* to serve as an *event journal*. Events stored for Event Sourcing must be written in a way that enables future reads to quickly assemble small(er) streams of events that belong to the single Aggregate that originally emitted them. This requires a random access index. 2. Message Streaming requires storage that is essentially a *flat file* that logs message elements. The message elements are individually written in sequential order and later read in sequential order. This requires one first-to-last sequential index. Based on these two fundamental points, I now break this down further into details: 3. Now, beyond Aggregate sub-streams, all events of an Event Sourced domain model are generally consumed as a totally-ordered stream of events in the *time* order that they were originally emitted by Aggregates. To do so *also* requires a sequential index. Thus, an Event Sourcing *database* must support *two* kinds of indexes. 4. Kafka is *NOT* suitable for an Event Sourcing *database*. What is the name of the concept under which *messages* are *logged*? It's a *topic*. Kafka is a message log that can have many topics. Kafka has *one single index*, which is the sequence number of the *totally ordered stream of messages*. 5. Therefore, after writing messages into a Kafka topic, they cannot be read randomly because the random access index doesn’t exist. Kafka was not designed for this. 6. With Kafka, if you need to read the small(er) streams of events originally emitted by single Aggregate instances, you would have to scan an entire topic from the first message to the last message to ensure you didn’t miss reading all events in one of the individual Aggregate streams. This would cause O(N) read time--reads become slower as every new message is written to the topic. You have 1 billion total events and you need to read any 5 of those as an individual Aggregate event stream? "Ain't-gonna-happen." For the really stubborn people who think they can outsmart physics, I'll add a few more points: 7. "I know, I know! I'll use a different topic for each Aggregate instance!" That's okay if Kafka was designed to support millions to billions to trillions of topics under a single broker. It wasn't. 8. "I know, I know! I'll use a K-Table to maintain snapshots of each Aggregate instance so I can read them quickly!" Reconstituting the state of an Aggregate must take priority over consuming a totally ordered stream of all events. If you try this, your K-Table snapshots will be only eventually consistent with the *real current Aggregate state*--the Aggregate can't reliably read it's own state. The End.
15
112
5
550
51,519
Matthew de Detrich retweeted
Scala Native running on @playdate by @panic. No GC, pointer trouble in the FFI part, still rough around the edges, but I'm happy to have reached this point after a month of trying!
5
12
1
82
9,436
Matthew de Detrich retweeted
I started a blog. In the first installment I write of some of my memories of Niklaus Wirth. odersky.github.io/blog/2024-…
9
91
12
476
44,683
Matthew de Detrich retweeted
Scala 3 is the best programming language of today. I've been professionally programming in C, C++, VB, PHP, JavaScript, TypeScript, Java, Scala, Haskell and Rust. I've used Python, Ruby, Go, Kotlin, Swift and OCaml recreationally. None is even close.
This Post is from an account that no longer exists. Learn more
3
19
4
83
8,044
Matthew de Detrich retweeted
Replying to @yasyapro
Hi, I'm using pekko at $work with Jdk 11,17 and now jdk 21, and you can contributes to pekko and akka too.
1
1
4
310
Matthew de Detrich retweeted
Apache Pekko Persistence R2DBC 1.0.0 with Scala 3.3 support has been released, see pekko.apache.org/download.ht… and pekko.apache.org/docs/pekko-… for more details.
3
11
806
Matthew de Detrich retweeted
Apache Pekko Persistence DynamoDB 1.0.0 has been released, see pekko.apache.org/download.ht… for more details.
6
10
890