دوره مقدماتی React 18
بررسی تغییرات ASP.NET MVC 5 beta1
Jon Galloway: Bleeding edge ASP.NET: See what is new and next for MVC, Web API, SignalR and more
دریافت از اینجا: (^)
دوره React Native دانشگاه هاروارد
معرفی کنترل چارت زیبای NVD3
- گروه بندی سطری و ستونی در چارت
- چارتهای خطی انباشته (cumulative)
- Pie Chart
- تولتیپ بر روی نودهای سریها
- چارتهای پشته ای (Stacked Area)
- چارتهای Discrete Bar
- چارتهای حبابی
- چارتهای گلوله ای (Bullet Chart)
This project is an attempt to build re-usable charts and chart components for d3.js without taking away the power that d3.js gives you. This is a very young collection of components, with the goal of keeping these components very customizeable, staying away from your standard cookie cutter solutions.
Angular Ivy چیست؟
Ivy is a complete rewrite of the compiler (and runtime) in order to:
- 🚀reach better build times (with a more incremental compilation)
- 🔥reach better build sizes (with a generated code more compatible with tree-shaking)
- 🔓unlock new potential features (metaprogramming or higher order components, lazy loading of component instead of modules, a new change detection system not based on zone.js…)
Domain Driven Design: The Good Parts
The greenfield project started out so promising. Instead of devolving into big ball of mud, the team decided to apply domain-driven design principles. Ubiquitous language, proper boundaries, encapsulation, it all made sense.
But along the way, something went completely and utterly wrong. It started with arguments on the proper way of implementing aggregates and entities. Arguments began over project and folder structure. Someone read a blog post that repositories are evil, and ORMs the devil incarnate. Another read that relational databases are last century, we need to store everything as a stream of events. Then came the actor model and frameworks that sounded like someone clearing their throat. Instead of a nice, clean architecture, the team chased the next new approach without ever actually shipping anything.
Beyond the endless technical arguments it causes, domain-driven design can actually produce great software. We have to look past the hype into the true value of DDD, what it can bring to our organizations and how it can enable us to build quality systems. With the advent of microservices, DDD is more important than ever - but only if we can get to the good parts.