Видео

Thank you, do not think this will be possible for life sciences(Nucleotide,Genomic, Teritary Protein Structure etc) or physics(HLC) scenario....believe it's limited in its scope

nice! thanks for sharing, definitely archiving this one for later reference

I had to use a CountDownLatch in the FiberImpl to make a proper wait until the thread joins because even with the Thread.sleep the main thread was still exiting early.

Please use high contrast next time.

Scala needs ohne killer Feature to survive. Maybe full wasm and wasi support?

​ @kitlangton // 4. Companion Object Idioms // - constructors / higher-arity combinators // - example using Coord May I know know where can I find the content of this topic??? Any RUclips links and gists?

i watched it twice, but it seems to be more about zio rather than the idea of functional effect systems and an introduction for functional beginners .

Thank you.....

Great concept-will take a couple of impressions to get it, but I like the idea. Some real innovation! Honestly I’m in favor of anything to help push forward the effectful functional model. Granted this is a first release, so I would expect everything to be optimized yet, but do you have any baseline benchmarks?

Thank you......lot of errors in scientific papers!!!!!!! [ reproducability,!!! what happen to the 3R's ]

Thank you, however, it sounds like returning to "MapReduce" scenario, in big data space using more of a concurrency/parallel processing paradigms for [bioinformatics, cheminformatics, and for deeper scientific computing scenario[from datasets form sites such as LHC, FCC and similar sites around globe etc], however, still few confusing statements such as is it a OnPremise or Cloud computing?, consider these are two different scenario and "regional" means more of a cloud computing, most scientist or research professional prefer the prior than the later...also would like state aware of academic credentials of both parties, and still would suggest folks without inter disciplinary lower level knowledge, skills and talents are not ideal folks to be associated with levels of development(POC), even though they might possess Phds in their respective fields, since most platforms available out there does not fulfill needs [Blast, NCBI, SNP, Galaxy etc] most deeper research professionals and scientific folks even in 2024...., though the story of Big Data from 2008....something like that, and functional programming is like 1940....something like that and the rest thought process should be able figure out....

nice I love scala-cli

16:04 "The rust language was designed for synchronous code" - really? I think rust was designed for programming with threads rather than with async/await. Another thing that makes async/await complicated for rust is that it does not have a standard async runtime nor does it require an async runtime.

is it still posible to signup?

Sum types and subtyping are similar right?

Make sure to subscribe to our designated Durable Computing channel, where we talk more about Golem 💪 www.youtube.com/@DurableComputing

Nice demo, congratulations on the 1.0 launch! During the demo Daniel says that it's impossible to update the worker under certain conditions: namely when interface changes (though it seems like in the demo only the implementation was changed?). That brings a more general questions of how to evolve worker states: e.g. how to migrate the state from test2 to test22 atomically during update? And is there a shortcut for common cases, e.g. adding a new field with default value to the State class?

amazing interview indeed

Great trolling, none of these are trully a problems of Rust, those are issues with Scala.

Too good to be true?

John, here it Goes

I'm learning SCALA right now. Why does it need WASM?

Since Java got lambdas and streams, Scala does provide very few advantages. And tones of complications.

Scala is great language. Thank you for supporting

very nice detailed explanation for beginners

Its a must watch, thanks for this session

Why the fight when you can use Loom inside the ZIO or Kyo or Cats Effect one of these days !! 👍😎 ... This requires a heavy rewrite of these tools but it's possible or at least more productive than fighting 😅😇

Great video Yisrael ❤

Nice, I was waiting for next vide ;-=

It's no Clojure... I have had no end of issues with Scala and backwards compatibility. Even just simple version changes w/libraries. Not with Clojure. I like Scala, but I love Clojure.

If you have multiple instances, the STM cannot solve the transaction problem, right?

Hey John, really cool and comprehensive subject, thanks for your contributions to the Scala community and to helping improve engineers. I would have a suggestion for a topic for your open-source series, which would be open-sourcing a commercial project.

she got a glimpse into the Matrix sqeeze the people but not so much that they'll break

Difficult to follow due to the ambient room reverb. It's generally better to use a mic.

39:10 Isn't Scala.JS very much integrated in Scala?

34:10 scala-cli is probably much better than cargo

i am learn a lot from scala to understand rust

Dependency Injection Attacks [19:26] 😂🤣😂🤣

Scala value prop (for me at least): write reliable concurrent code on the JVM, easily.

This is great! I like seeing things process.

Excellent stuff, Nabil. I appreciate seeing the progression of the DSL and how it reached its awesome current state.

What you describe with "you say what you want to do" is actually a command on CQRS, as I said you can apply your Flows as an abstraction that behind the scenes use CQRS + ES (each flow step is one command that generates 1 to n events)

Some comments related with your comments on event sourcing: - you never retry events, you retry a command (and if the command fails 0 events are generated), events are always facts that happened in the past and hence there is no need to retry anything (commands are actions that produce events) - I do agree in most cases it's true using ES is accidental complexity and that is a new paradigm, but I dont agree that makes you change ALL your application. If you follow DDD it will only affect a part of your application, normally a bounded context where CQRS + ES is justified - Also you don't mention that once you have the events stored is super easy to reply them and create new views or feed other aggregates, in a super natural way compared with a traditional "store snapshot" approach with CRUD - Kafka is not a good fit for event sourcing as it doesn't have optimistic locks, I saw super good implementations using Postgres, event sourcing is NOT event streaming, it's a style of how you store your events - The example of the shopping cart is actually a good fit for event sourcing, for example when you need information for analytics it's super easy to replay all events from our users and create different views, but if you read from transactional tables you miss lot of information relevant for data science models - I actually think you can apply durable computing on top of event sourcing, they are compatible things solving different concerns, event sourcing is used to reflect business (it's linked to domain) where durable computing is about fixing non-functional issues like failures, hardware retries, etc. You can apply both together

Really enjoying this series - thank you both, Nabil and John!

Probably the most convoluted implementation of tic tac toe I've ever seen 😅

Thanks Daniel, great session!

Here he goes! 💪💪

Pragmatist here: Correct me if I am wrong but as far as I can tell Scala has the following to learn from Rust: 1) It has to learn to work with out the JVM (or any kind of run-time system). Requiring the JVM implies bloat and poor performance. That excludes use of Scala from much of the work I do. 2) It has to learn to work without a garbage collector. A garbage collector introduces unpredictability in performance. It also excludes use of Scala from much of the work I do. 3) It has to learn to run in only kilobytes of code space on micro-controllers and the like. 4) It has to learn that maths is great and all, but maths is limited. Maths does not have a solution for the many body problem, for example. As for monoids, I had them surgically removed as a child.

Scott Wlaschin - Designing with capabilities ruclips.net/video/RqlnWv6NZos/видео.html