Vasily
Vasily
Переоценил я интеллект Ильи
Maksym
Ilya
Ilya
Не Эйнштейн точно
Vasiliy
что вы Илью хейтите?
Roman
да это Вася как всегда
Vasily
Vasily
А приведение самооценки в равновесие с окружающим миром
EgorBo
Vasily
Roman
Vasily
Vasily
Vasily
Ilya
Нипонял
Вроде же декларировалось что это самый дружелюбный чат🤔
Vasily
Скорее принятие людей такими, какие они есть
Ilya
Vagif
Ну ты же будешь на докладе, можно будет там задать
Ilya
Vagif
Пока что я выслал им вот это, чтобы готовились:
1. The first public release of Akka on JVM was announced in January 2010, and Microsoft Orleans has become known around 2011. Akka .NET port came in early 2014. So both frameworks are about a decade old, and they have been around long enough for retrospective summary.
- What did you learn for yourself as an architect and major contributor of the product? Are there any features left out that you wish the product had? Anything that you no longer find important?
- Both frameworks have strong development communities with apprx. 2.5 million downloads of each core NuGet package. Did the community influence you or change your mind about certain parts of the product? Can you give an example of a community-influenced change or decision?
2. I'd like to forward you a question I was asked recently, which was: "Do you think developers talk less about the actor model these days, it's not so much hype about it?" Since I am using the actor model every day I never thought about it in terms of being hyped or becoming less popular. I don't even know whether developers are more or less interested in using the actor model than 5-10 years ago. What do you think? Perhaps stateful serverless functions in the cloud introduced not so long ago are becoming an alternative to the traditional actor model?
3. Now let's move on to differences between Akka and Orleans, this is what developers often ask about. Questions "which product better suits my needs" are often impossible to answer because even in the scope of a single development team there are many comparison criteria, and giving them different priorities may result in different answers. Learning curve, performance, community and support - these and other factors may affect the choice. Can you help developers trying to choose an actor model with a set of criteria they should bear in mind?
4. Already in 2015 there was a comparison published about Akka and Orleans (https://github.com/akka/akka-meta/blob/master/ComparisonWithOrleans.md)
- The primary focus of Orleans is to simplify distributed computing and allow non-experts to write efficient, scalable and reliable distributed services.
- Akka is a toolkit for building distributed systems, offering the full power but also exposing the inherent complexity of this domain.
I can also quote Anton Moldovan who compared Akka and Orleans with C++ and C# respectively.
Can you please comment on this?
5. Somewhat a difficult question. From what you know about the other framework, can you think about type of applications or services when you think the other framework might be a better choice?
Personal question to Aaron. Being engaged in every aspect of Akka.NET development, you launched in parallel sdkbin.com to, a marketplace for developers. Is there a risk that in the future you will shift your focus to sdkbin at a cost of being one of the main Akka.NET contributors?
Personal question to Sergey. You recently left Microsoft for Temporal that is developing an open source microservice orchestration platform. What are your first impressions about your post-Orleans professional experience, even though it's been rather short period?
Last question. How do you see the next decade of Akka and Orleans?
Vagif
К сожалению буду смотреть в записи 😔
Ну ты напиши свой вопрос, там по ситуации посмотрим. В принципе этих уже должно хватить на 75 минут, плюс вопросы аудитории. Так что если будет время
Ilya
Пока что я выслал им вот это, чтобы готовились:
1. The first public release of Akka on JVM was announced in January 2010, and Microsoft Orleans has become known around 2011. Akka .NET port came in early 2014. So both frameworks are about a decade old, and they have been around long enough for retrospective summary.
- What did you learn for yourself as an architect and major contributor of the product? Are there any features left out that you wish the product had? Anything that you no longer find important?
- Both frameworks have strong development communities with apprx. 2.5 million downloads of each core NuGet package. Did the community influence you or change your mind about certain parts of the product? Can you give an example of a community-influenced change or decision?
2. I'd like to forward you a question I was asked recently, which was: "Do you think developers talk less about the actor model these days, it's not so much hype about it?" Since I am using the actor model every day I never thought about it in terms of being hyped or becoming less popular. I don't even know whether developers are more or less interested in using the actor model than 5-10 years ago. What do you think? Perhaps stateful serverless functions in the cloud introduced not so long ago are becoming an alternative to the traditional actor model?
3. Now let's move on to differences between Akka and Orleans, this is what developers often ask about. Questions "which product better suits my needs" are often impossible to answer because even in the scope of a single development team there are many comparison criteria, and giving them different priorities may result in different answers. Learning curve, performance, community and support - these and other factors may affect the choice. Can you help developers trying to choose an actor model with a set of criteria they should bear in mind?
4. Already in 2015 there was a comparison published about Akka and Orleans (https://github.com/akka/akka-meta/blob/master/ComparisonWithOrleans.md)
- The primary focus of Orleans is to simplify distributed computing and allow non-experts to write efficient, scalable and reliable distributed services.
- Akka is a toolkit for building distributed systems, offering the full power but also exposing the inherent complexity of this domain.
I can also quote Anton Moldovan who compared Akka and Orleans with C++ and C# respectively.
Can you please comment on this?
5. Somewhat a difficult question. From what you know about the other framework, can you think about type of applications or services when you think the other framework might be a better choice?
Personal question to Aaron. Being engaged in every aspect of Akka.NET development, you launched in parallel sdkbin.com to, a marketplace for developers. Is there a risk that in the future you will shift your focus to sdkbin at a cost of being one of the main Akka.NET contributors?
Personal question to Sergey. You recently left Microsoft for Temporal that is developing an open source microservice orchestration platform. What are your first impressions about your post-Orleans professional experience, even though it's been rather short period?
Last question. How do you see the next decade of Akka and Orleans?
Отличное вопросы! Но если будет время, было бы здорово послушать что они думают о нашей дискуссии о том, как делать длительные отказоустойчивые действия. Про ретраи, авто активации акторов и т.д.
Ilya
Мы это обсуждали, это можно немного костыльно сделать и там и там, но хочется услышать, что думают создатели фреймворков
Vagif
Ilya
Ilya
Roman
@VagifAbilov я тоже хочу докинуть вопросы:
- Looking back now, is there something fundamental in design you would have done differently, if you'd have a chance to rebuild it from scratch or break compatibility?
- Did you feel any restrictions coming from language? If so what are they and what language you would use if you could?
Vagif
gsomix
Ilya
Этот чат для баланса?
Denis
А кстати, где почитать про ситуации в которых стоит использовать акторов ?
Denis
по крайней мере как понять что mailbox-ов перестает хватать и пора брать акку
Roman
Короче, когда чувствуешь, что мейлбоксов не хватает)
Vagif
Даже не знаю, с чего начинать. Проще как Роман сказал: как видишь, что не хватает, значит все
Ilya
В основном, горизонтальное масштабирование (особенно в орлеансе)
Roman
мейлбоксов хватает, когда у тебя немного акторов, желательно без циклов в топологии, все живет in memory и это нестрашно похерить
Denis
Окей вроде стало понятнее ))
Vagif
Окей вроде стало понятнее ))
Если пара основных моментов, то это персистенс и распределенность (кластеры). Самое интересное с акторами начинает происходить, когда они начинают хранить стейт
Nikolay
А в F# нельзя задать field с дефолтным значением как в C#?
Ayrat
Ayrat
но можно
Ayrat
через атрибут
Nikolay
Ayrat
там все настолько уебищно, что проще на сишарпе!!1
Nikolay
Я тут сову на глобус натягиваю!
gsomix
Nikolay
using System;
public class C {
int a = 6;
}
Nikolay
Типа так
gsomix
В конструкторе можно задать.
Anatoly
Меня больше индексеры порадовали
Ayrat
Anatoly
s.Chars(0)
gsomix
Nikolay
Vladislav
Ayrat
это метод с аргументом 0
Ayrat
индексер это вот
abc.[1]
Ayrat
Ayrat
s.[0]
Ayrat
Chars это просто метод
Ayrat
кстати это екстенш из кор либы фшарпа
Ayrat
Chars
Ayrat
хз зачем он
Anatoly
Ну райдер его подсказывает
Ayrat
пока ты не сказал, даже не знал о его существовании
Roman
Vladislav
Это определение индексера