amzans

31 ms·

271.
High Performance Arrow and Task in Scala(github.com)
2 points by amzans 9y ago|0 comments
272.
Jonas Boner: Bla-Bla Microservices Bla-Bla(jonasboner.com)
2 points by amzans 9y ago|0 comments
273.
Timeless programming tools(flyingmachinestudios.com)
2 points by amzans 9y ago|0 comments
274.
Clojure is not for geniuses(adambard.com)
1 points by amzans 9y ago|0 comments
275.
The Sacred Art of Concurrent and Parallel Programming(braveclojure.com)
1 points by amzans 9y ago|0 comments
276.
by amzans 9y ago
I can very much relate to the pain points and benefits mentioned in the example. Last year we had a project in which we had to take a stream of data that needed to be verified with several calls to an external system before being partitione
277.
Akka Streams: A Motivating Example(blog.colinbreck.com)
1 points by amzans 9y ago|1 comments
278.
Be More Productive by Not Finishing Your Work(blog.colinbreck.com)
2 points by amzans 9y ago|0 comments
279.
There is No Now(queue.acm.org)
1 points by amzans 9y ago|0 comments
280.
Calling Blocking Code: There Is No Free Lunch(blog.colinbreck.com)
2 points by amzans 9y ago|0 comments
281.
Scala's Future.successful: Do Not Block Your Future Success(blog.colinbreck.com)
1 points by amzans 9y ago|0 comments
282.
Handling Overload (2016)(ferd.ca)
34 points by amzans 9y ago|0 comments
283.
Lessons Learned While Working on Large-Scale Server Software(ferd.ca)
2 points by amzans 9y ago|0 comments
284.
by amzans 9y ago
I agree, we haven't found a general solution to building concurrent programs without the downsides that most of the existing models incur. The Actor model doesn't remove the burden to handle edge cases from the programmer, and dep
285.
The Architecture of the Next CERN Accelerator Logging Service(databricks.com)
1 points by amzans 9y ago|0 comments
286.
Real-Time Streaming ETL with Structured Streaming in Apache Spark(databricks.com)
1 points by amzans 9y ago|0 comments
287.
How to Get Startup Ideas: The Meat Grinder Approach(tylertringas.com)
2 points by amzans 9y ago|0 comments
288.
What is a reactive microservice?(oreilly.com)
1 points by amzans 9y ago|0 comments
289.
Message Passing and the Actor Model(dist-prog-book.com)
223 points by amzans 9y ago|85 comments
290.
What “accept interfaces, return structs” means in Go(medium.com)
2 points by amzans 9y ago|0 comments
291.
Beyond algorithms: Optimizing the search experience(oreilly.com)
2 points by amzans 9y ago|0 comments
292.
Tiny Hacks(docs.google.com)
1 points by amzans 9y ago|0 comments
293.
The art of searching(youtube.com)
1 points by amzans 9y ago|0 comments
294.
Implementing functional languages: a tutorial(microsoft.com)
2 points by amzans 9y ago|0 comments
295.
by amzans 9y ago
The main advantage that I’ve seen when writing and reading functional instead of procedural/imperative code, is that the intention is usually clear. We have a list of numbers that we want to square and add up, instead of the more mecha
296.
by amzans 9y ago
It's great to see projects like this on HN. Congrats man, well done!
297.
Comparing Akka Streams, Actors and Futures(jobs.zalando.com)
1 points by amzans 9y ago|0 comments
298.
Scala 3: first Dotty milestone release(scala-lang.org)
1 points by amzans 9y ago|0 comments
299.
Scaling to 11+ million users on AWS(highscalability.com)
5 points by amzans 9y ago|0 comments
300.
Machine Learning for Artists(ml4a.github.io)
3 points by amzans 9y ago|0 comments

More ›