Quantcast
Channel: angular.org.il
Viewing all 175 articles
Browse latest View live

Announcing Ionic 2.0.0 Final | The Official Ionic Blog


Implementing Angular’s Dependency Injection in React. Understanding Element Injectors. – Minko Gechev’s blog

$
0
0

Recently I’ve been blogging mostly about Angular and it’s not by accident! Angular is an amazing framework, bringing a lot of innovation to the front-end technologies, with a great community behind it. In the same time, the projects that I’m working on have various of different requirements and sometimes I need to consider different options.

Source: Implementing Angular’s Dependency Injection in React. Understanding Element Injectors. – Minko Gechev’s blog

The post Implementing Angular’s Dependency Injection in React. Understanding Element Injectors. – Minko Gechev’s blog appeared first on angular.org.il.

An Introduction to Observables for Angular Developers -Telerik Developer Network

A deep dive on Angular decorators

$
0
0

Decorators are a core concept when developing with Angular 2 and above. There’s also an official TC39 proposal, currently at Stage-2, so expect decorators to become a core language feature soon in JavaScript as well.

Back to Angular, the internal codebase uses decorators extensively and in this post we’re going to look at the different types of decorators, the code they compile to and how they work.

Source: A deep dive on Angular decorators

The post A deep dive on Angular decorators appeared first on angular.org.il.

Making your Angular apps fast by thoughtram

LightSwitch Help Website > Blog – An Angular 2+ Web Application Configuration Wizard

NgUpgrade with the Angular router and ui-router

Cloud Spanner beta brings Google’s globally-distributed database solution to third-party developers | 9to5Google


Managing State in Angular Applications

$
0
0

Managing state is a hard problem. We need to coordinate multiple backends, web workers, and UI components, all of which update the state concurrently. Patterns like Redux make some of this coordination explicit, but they don’t solve the problem completely. It is much broader.

What should we store in memory and what in the URL? What about the local UI state? How do we synchronize the persistent state, the URL, and the state on the server? All these questions have to be answered when designing the state management of our applications.

In this article I will cover six types of state, the typical mistakes we make managing them in Angular applications, and the patterns we should use instead.

Source: Managing State in Angular Applications

The post Managing State in Angular Applications appeared first on angular.org.il.

How to Build and Structure a Node.js MVC Application

Angular-cli – configure your webpack project using the eject functionality

Angular — Advanced Styling Guide (v4+) – Google Developers Experts – Medium

10 Best Practices for Writing Node.js REST APIs | @RisingStack

Building Single Page Applications on ASP.NET Core with JavaScriptServices | .NET Web Development and Tools Blog

Building Beautiful Web Apps With Angular Material – Part I – Barbarian Meets Coding


Introduction to Ionic 2

Writing a Basic Component Test with Angular Testing Utilities – One Hungry Mind

Always Throw Errors In Order To Get A Stack Trace In Promise Chains

Popups, Modals, and Navigation — Using Angular Material (2) Components in your Angular (2) Project – Medium

V8 JavaScript Engine: High-performance ES2015 and beyond

$
0
0

Over the last couple of months the V8 team focused on bringing the performance of newly added ES2015 and other even more recent JavaScript features on par with their transpiled ES5 counterparts.

Motivation

Before we go into the details of the various improvements, we should first consider why performance of ES2015+ features matter despite the widespread usage of Babel in modern web development:

  1. First of all there are new ES2015 features that are only polyfilled on demand, for example the Object.assign builtin. When Babel transpiles object spread properties (which are heavily used by many React and Redux applications), it relies on Object.assign instead of an ES5 equivalent if the VM supports it.
  2. Polyfilling ES2015 features typically increases code size, which contributes significantly to the current web performance crisis, especially on mobile devices common in emerging markets. So the cost of just delivering, parsing and compiling the code can be fairly high, even before you get to the actual execution cost.
  3. And last but not least, the client side JavaScript is only one of the environments that relies on the V8 engine. There’s also Node.js for server side applications and tools, where developers don’t need to transpile to ES5 code, but can directly use the features supported by the relevant V8 version in the target Node.js release.

Source: V8 JavaScript Engine: High-performance ES2015 and beyond

The post V8 JavaScript Engine: High-performance ES2015 and beyond appeared first on angular.org.il.

Viewing all 175 articles
Browse latest View live




Latest Images