Minko just smashed React by showing the Ivy instructions and the react compiler output side by side ๐
Yes, Angular has done a lot of optimizations since v9 with Ivy (we're on v18)
#angular
๐ฅ See how to leverage the features of different Angular versions to enhance your projects!
In our free ebook,
๐"The Ultimate Guide to Angular Evolution," ๐https://t.co/kv2d6lFGLA,
we explore the transformations of Angular from version 14 onwards and ๐ how they can improve your work efficiency.
๐จโ๐ป Mateusz Dobrowolski, the principal author of the ebook, describes each new feature, the challenges it addresses, and the benefits it brings.
After reading, you will understand:
๐ The benefits that updating versions brings.
๐ Which version and features best meet the needs of your project.
๐ Whether the lack of a certain feature is holding you back from progress.
๐ In the end, Google Developer Experts such as @AlisaDuncan, @connieleung404, @puppo9, Artur Androsovych, @abampakos, @uvbrain, @puppo92, @AlisaDuncan, @StefanvHaas, @connieleung404, @DecodedFrontend,@webdave_de, and Balram Chavan offer insights and predictions about what the future holds for Angular.
Don't wait! Download our free ebook and start working smarter, not harder. โก๏ธ https://t.co/kv2d6lFGLA
๐ช๐ต๐ ๐ฑ๐ผ๐ฒ๐ ๐๐ผ๐ผ๐ด๐น๐ฒ ๐ฟ๐ฒ๐ฐ๐ผ๐บ๐บ๐ฒ๐ป๐ฑ ๐ ๐ผ๐ฑ๐๐น๐ฎ๐ฟ ๐ ๐ผ๐ป๐ผ๐น๐ถ๐๐ต๐ ๐ถ๐ป๐๐๐ฒ๐ฎ๐ฑ ๐ผ๐ณ ๐ ๐ถ๐ฐ๐ฟ๐ผ๐๐ฒ๐ฟ๐๐ถ๐ฐ๐ฒ๐?
In the last decade, we have seen a massive trend of using microservices everywhere. We were building systems for a few hundred or thousand users and wanted to know how to make a system for millions of users. This was over-engineering and needed to be corrected. Why it was wrong? Because the development lasted long and we created incredibly complex systems, hard to maintain. This is especially true for startups that must go fast and stay simple.
A recent paper by authors from Google found that most of their developers split binaries for one of the following reasons: it improves performance, fault tolerance, and abstraction boundaries and allows for flexible rollouts.
Yet, splitting applications into microservices has its challenges:
๐ธ ๐๐ ๐ต๐๐ฟ๐๐ ๐ฝ๐ฒ๐ฟ๐ณ๐ผ๐ฟ๐บ๐ฎ๐ป๐ฐ๐ฒ. The overhead of serializing data and sending it across the network is increasingly becoming a bottleneck
๐ธ ๐๐ ๐ต๐๐ฟ๐๐ ๐ฐ๐ผ๐ฟ๐ฟ๐ฒ๐ฐ๐๐ป๐ฒ๐๐. It is incredibly challenging to reason about the interactions between every deployed version of every microservice.
๐ธ ๐๐ ๐๐ฎ๐ธ๐ฒ๐ ๐๐ผ๐ฟ๐ธ ๐๐ผ ๐บ๐ฎ๐ป๐ฎ๐ด๐ฒ. Rather than having a single bi-nary to build, test, and deploy, developers must manage ๐ different binaries, each on their release schedule.
๐ธ ๐๐ ๐ณ๐ฟ๐ฒ๐ฒ๐๐ฒ๐ ๐๐ฃ๐๐. Once a microservice establishes an API, it becomes easier to change by breaking the other services that consume the API.
So, they proposed the following approach:
๐ญ. ๐ช๐ฟ๐ถ๐๐ฒ ๐บ๐ผ๐ป๐ผ๐น๐ถ๐๐ต๐ถ๐ฐ ๐ฎ๐ฝ๐ฝ๐น๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป๐ that are modularized into logically distinct components. A component is a long-lived agent, similar to an actor.
๐ฎ. ๐๐ฒ๐๐ฒ๐ฟ๐ฎ๐ด๐ฒ ๐ฎ ๐ฟ๐๐ป๐๐ถ๐บ๐ฒ ๐๐ผ ๐ฑ๐๐ป๐ฎ๐บ๐ถ๐ฐ๐ฎ๐น๐น๐ and automatically assign logistical components to physical processes based on execution characteristics. So, if both components are in the same OS process, they are called regular method calls, but if they are co-located, calls are executed as RPCs over the network. Runtime decides whether these modules should be collocated or moved to different machines (and scaled, etc.).
๐ฏ. ๐๐ฒ๐ฝ๐น๐ผ๐ ๐ฎ๐ฝ๐ฝ๐น๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป๐ ๐ฎ๐๐ผ๐บ๐ถ๐ฐ๐ฎ๐น๐น๐, preventing different versions of an application from interacting.
This approach consists of two main parts: a programming model with abstraction that allows developers to write modularized applications and a runtime for building, deploying, and optimizing these applications. They claim that it reduces application latency by up to 15x and costs by up to 9x by simplifying application management and deployment.
If you want to check the framework implementing the approach from the paper, check https:// serviceweaver. dev/.
What do you think about this approach? Does it look like EJBs or CORBA?
#microservices
Hey #flutter devs
Me and @Yash_khattar73 are making ModularUI #opensource
ModularUI is the first ever consistent library of pre-built beautiful customizable and consistent @FlutterDev widgets inspired by material-tailwind/shadcnโจ
Checkout the GitHub - https://t.co/KYEnc7Smq7
Angular Dependency Injection Visualization is coming to Angular Devtools ๐ฅ๐
Debugging DI issues the hard way will be a thing of the past!
https://t.co/YtuGPa11Wi
#angular
๐คฉ [1/4] Coming soon in @ChromeDevTools - You can overrides API response (Fetch/XHR) and more!
Imagine you can mock APIs in frontend without waiting for the backend changes!
Not only that...
Check out the code below.
This pattern lets you use User interchangeably as a type and a user, same as a class or enum might.
Is this heresy? Or awesome?
(I think maybe the latter)
๐จ CSS tip(3):
`height: 100vh`
is a common way to make your app fit the whole window. It won't do a good job on mobile though ๐ฌ
`height: 100dvh`
works way better!
๐ฑ See the difference on your phone:
https://t.co/t7KR7WGsQ6
๐ป Play with the demo:
https://t.co/nSq1PuCu0p
One of the things that helps me improve as a developer is polishing my own code. First version of the solution is often hacky but working. Then, once I understand the big picture, I give myself a code review to clean up any hackery. Rinse and repeat this process...
Built-In Control Flow RFC allows us to easily manage the flow of our templates with easy to use new syntax ๐
It gets inspiration from @sveltejs ๐
Here's a before and after how it looks like ๐
#angular#svelte
Here are some common #Angular performance issues:
- HostListeners on document or window
- Forgetting trackBy on *ngFor
- Not using OnPush
- Deep-cloning objects
- Running too much in the inner zone
- Not unsubscribing from observables
Have a great evening!๐ค๐๐๐
Angular powers SpaceX to throw rockets ๐ in space ๐
I think that's amazing! ๐คฉ
Maybe it's frontpage is not built with Angular but every internal app is ๐คทโโ๏ธ
https://t.co/qMIaWO3Yau
#angular