Відео

Seems like a step in the right direction. I'll definitely try it in my next project

Relying entirely on effect feels limiting in some cases. It would be much more helpful to see an express/adonis-based project gradually transitioning to effect step by step.

If this is an example project for the public, it would be better to use something like Drizzle or some other tool to do the SQL. Personally, I feel that using effect/sql directly defeats a lot of the purpose of Effect which is to keep everything typed correctly, including errors. Just an opinion, nice video :D

2:42:27 for the Scope.extend portion, couldn’t you just wrap each scoped effect in Effect.scoped? Why would that be different than the example? Or is this just showing that it splits scope into separate requirements that would have to be closed with scope.close for each some time in the program?

Is the code anywhere online to be found? I would like to take a closer look at that.

I see all this boilerplate code and my Redux PTSD triggers immediately

95% of this video is about XState and the only time the Effect is used, it is when wrapping one-line code in Effect.sync and immediately running it with Effect.runSync, which is no better than just running the same code directly . I'd wish for a better example that shows where Effect shines. For example a basic error handling and how we can then branch out to a specific error state in XState.

excelent content! thanks!

Hi, another question is why you use imports like import * as Schema from "effect/Schema". I've almost always seen it as import { Schema } from "effect". Is it more of a habit?

Do you plan on making the code examples public? Would be nice if we could follow there

Hi, is there any particular reason why you are using symbols for IDs instead of Branded Types? Great video btw :D

Neat, thanks. And thanks for the zoom 😃

“Real world examples” - a high schooler I kid. Well, only partially. And lovingly.

Great presentation, i want to learn more, but is that LIGHT theme!?

Looking forward to part 2 🤗

Awesome i know nothing of effect

All the DDD parts are really a great bonus

I think I've learned more about how to use Effect Schema from this one video than I ever did from reading documentation and watching all the other videos on Effect that I could find.

awesome stream!

More of this please! This is super helpful for someone trying to pick up Effect and see how it's used in actual applications.

Hello, excellent content to learn a lot about the ecosystem. Will this project be continued?

Wow! This is awesome, the videos on this channel are so informative! Thank you! I'm slowly starting to understand Effect as I watch these videos more and more.

Excelent content

Ideally the IDE font should be at least 1.25 times bigger for comfortable reading for those streaming this on mobile.

can you please make a Real world example, i dont get how to implement this 😢

17:30 -- it is exactly a problem of Effect. You need all requirements, but declare that you need any of them ...

Can you clarify what else I need to watch before this?

I'm sure people running the sound love it when you call them 'yo'. :(

excellent content!

This could work for a small percentage of projects where there is only one super-smart dev, but once you add another (not super-smart) dev in the equation, the onboarding process becomes unsustainable. I tried giving Effect a try, but it does not enforce patterns enough for my liking. It's still wild-west JavaScript, in my opinion (P.S.: Albeit not as bare-bones as vanilla JS, of course).

I rarely comment on UA-cam videos, but I have to say that it helped me a lot in a way that it gives numerous examples and real use cases along with some exercises. I got stumbled into Effect recently and found that it's really interesting, but there're so much stuff that I should get familiar with and the documentation was quite overwhelming at first glance. Now I have a nice reference where I can find some of the best practices when I'm stuck, and it gives me enough confidence to write my own code. For those who felt overwhelmed or got stuck, I highly recommend to clone his workshop repo and take a look at it. By the way I worked as an Android developer few years ago, though I'm backend now, this whole movement that Effect community makes reminds me how Kotlin ecosystem got evolved. One of the most favorable thing was the structured concurrency that coroutine provides. I'm glad that Effect also has those cool stuff and since those concepts were already proven in many other languages, I'm sure that it will gonna draw more attentions as it evolves.

I am 1 hour in and I already have so much more clarity than I did reading the docs. Thanks man!

19:22 Updating/patching long-running workflows in a testable way, and without turning your code into spaghetti, is the most difficult and important problem to solve. For a slight improvement to the single version mechanism shown here, see Temporal's patched and deprecatedPatch functions.

26:19 re. innovation, I see this as more of an obligation than a strategy to win. If you build on the work of predecessors, then you can "repay" this debt to prior innovation by asking new questions and making new mistakes so others can build on your work.

Integration with TRPC and Nextjs would be amazing

27:00 put mysql to its place :throw-in-trash:

The stringly typing of CatchTag shows the drawbacks of a bolted on type system. If you refactor your name of an error these ones are hard to fix…

What an awesome presentation. The kid rocks

react-query + @effect/rpc + nextjs when?

🎯 Key points for quick navigation: 00:00:04 *🎥 Introduction to the Stream and Project Overview* - Discussing the idea to stream the project in public, - Introducing Contentlayer, a tool built by Johannes Schickling, and explaining why it needs to be reimagined. 00:02:22 *🚀 Project Setup and Initial Goals* - Overview of the setup for the project, starting from a basic, stripped-down version, - Highlighting the focus on improving build performance and exploring Contentlayer's current functionality. 00:04:10 *📜 Deep Dive into Contentlayer's Functionality* - Explanation of Contentlayer’s role as a content SDK, validating and transforming static assets, - Discussion on the structure of documents in Contentlayer and how they map to website content. 00:07:20 *🧩 Document Types and User Experience* - Description of how document types are defined and used in Contentlayer, - Insight into the user experience with MDX and Markdown, and the process of generating and validating documents. 00:12:26 *🛠️ Challenges and Missed Opportunities in Contentlayer* - Discussion on potential improvements, including adding support for multiple sources, - Exploration of how effect schema could enhance Contentlayer’s document specification and validation. 00:16:43 *⚙️ Reimagining Contentlayer with Effect* - Ideas for integrating deeply parallel processing and more flexible document sourcing, - Thoughts on leveraging Effect Schema and making Contentlayer more concurrent and extensible. 00:19:24 *🔍 Contentlayer Caching and Further Enhancements* - Overview of Contentlayer’s caching mechanism and suggestions for making it more modular, - Discussion of how to use Effect's key-value store for more efficient caching in the reimagined tool. 00:21:37 *💻 Transition to Coding and Implementation* - Wrapping up the discussion on Contentlayer’s current state and moving on to code implementation, - Initial thoughts on preserving the positive aspects of the user experience in the new version. 00:27:10 *🔄 Schema Design Discussion* - Discussing whether fields should always be treated as a struct or a different schema type, - Consideration of the flexibility and benefits of struct-like fields in schema design. 00:30:26 *🧩 Computed Fields and Schema Transformation* - Exploring how computed fields could be incorporated into a schema, - The possibility of using schema transformations to simplify field definition. 00:34:41 *📄 Content Layer Document Type Handling* - Discussion on how content layer processes document types and retains schema information, - Deciding the best approach to typing fields in a content layer to maintain clarity and utility. 00:40:02 *🔍 Invariance, Covariance, and Contravariance Explanation* - Explanation of type variance concepts and their application in TypeScript, - Discussing the impact of type variance on function assignability and type safety. 00:47:22 *📝 Computed Fields Implementation Strategy* - Deliberating the order of execution for computed fields and the potential need for sequential vs. parallel processing, - Considerations for allowing user control over the context available during field computation. 01:01:06 *🧠 Type Restrictions & Schema Design* - Discussing how to restrict the effect returned by `resolve` to the schema's return type. - Considerations on merging fields and computed fields in the document type. 01:05:19 *🔄 Schema Transformation & Field Handling* - Exploring ways to handle field transformations within a schema. - Considerations on how to avoid field name collisions using TypeScript generics. 01:10:09 *🚧 Handling Duplicated Fields in Computed Fields* - Creating a check mechanism for duplicated field names within computed fields. - Discussing the use of conditional types to manage key distribution and collision. 01:22:09 *🗂️ Document Source Metadata & Type Display* - Adding metadata about document sources and ensuring this is visible in the type display. - Considering user experience when interacting with document types in the content layer. 01:29:30 *🛠️ API Design & User Experience* - Finalizing thoughts on API design and the importance of user experience in effect libraries. - Discussing the potential for a class-based API for better type opacity and optimization.

I wonder how it compares with express in terms of performance? (Im not a BE dev btw) For a backend framework it looks really cool.. I just wished the js ecosystem focused on fixing existing popular frameworks than building new ones every 2 years For fullstack frameworks I'd still go with Nuxt (check it out first before replying)

Love contentLayer, can't wait to see what happens with it. P.S. I also repeatedly highlight text when talking about it, it's good to know I'm not alone.

Good stuff as always Also you can simplify the check for common keys by doing `keyof (T | U)`

Thanks a lot for these videos!

Such an enlightening discussion! More of this please! Also, couldn't find the docs for Effect Cluster. Is it still in the making? Or maybe I missed finding it?

Thank you for this series! Please keep the amazing content coming :)