There is no disputing the fact Steve Jobs was a highly accomplished man. While he did not do it alone, he was instrumental in turning Apple around and making it the most valuable company in the world. He saw what nobody else could see at Apple and he knew what kind of people he needed to make it happen. Even years after his death, Apple shows no signs of slowing down and continues to hold more money than most first-world government treasuries.
Fresh off the heels of the controversial documentary series Struggle Street comes SBS’s latest foray into niche and insightful documentaries: Kebab Kings. There is nothing Australians love more than a kebab. If you have ever gone out on a Friday or Saturday night drinking, there is a good chance you have found yourself gracing the interior of a kebab store at 2am in the morning. They put cameras in a couple of busy kebab stores they call “Australia’s busiest” and recorded what happened in the month before Christmas.
One of my favourite and lesser known additions to CSS is position: sticky which essentially allows you to create an element that snaps at a specified position of the page to the top of the screen. At present, support for position: sticky is relatively non-existent according to caniuse. The desktop browsers that currently have this implemented are Firefox and Safari. But thankfully there are some great polyfills out there for this, the one I have found to be the more performant polyfill is by the Filament Group.
When it comes to building a web application, nothing causes more confusion than working out how to structure it (besides what to name things, of course). In the beginning, it is easy enough to just throw all of your code into the root of the src directory without a care in the world. But as the complexity of your application grows and subsequently its size, this approach fails. I have been working on a large-scale Aurelia application for about 6 months now and have a structure that has allowed me to move quickly without worrying about clutter or where to put everything.
When it comes to a modern web application, there is a high chance you will be working with a form or three. Fortunately Aurelia gives us straightforward and flexible ways of working with form elements and data. Below are some common scenarios in which you might find yourself working with forms in Aurelia. All relatively straightforward, using concepts you are probably already familiar with from other frameworks like Angular. Checkboxes I have seen a little bit of confusion when it comes to working with checkbox elements in Aurelia. Once you understand what each role the binding behaviours play, you realise it is all quite straight forward.
When it comes to raising money, there are not many apps that can attract as much capital and interest as Uber can. A Techcrunch story suggests Uber are looking to raise another $1 billion funding round (yes, that is one billion dollars). A mere 3 months ago, Uber raised a $1b round and they’re set to do it again. This would place their valuation between $60 billion and $70 billion respectively.
You are already aware of the fact React.js is fast, but did you know there is a way to speed up the rendering of React components even more? Say hello to my little friend PureRenderMixin The PureRenderMixin does a shallow comparison on our props and state values. It compares the existing value of prop or state to new values. Behind the scenes the PureRenderMixin is extending the lifecycle method shouldComponentUpdate. It determines if the render method is callable and your component will re-render.
One source of confusion when working with AJAX requests and Aurelia is whether you should use the aurelia-http-client or aurelia-fetch-client both achieve similar things. However at the time of writing this no official documentation that exists for using the Fetch Client or explains how to use it. I have been using the Fetch client since it debuted and realised others wanting to migrate to the Fetch client might find this post useful.
So you’ve decided it’s time to join the future and port your existing Angular application to Aurelia. Your first port of call was probably the documentation and chances are you probably got confused, because Aurelia lacks the concept of a “directive” – don’t be discouraged my friend, there is light at the end of the tunnel. The concept of directives do exist in Aurelia, however they go by the names: Custom Attribute and Custom Element. In Angular 1.x, a directive can both be a custom attribute and a custom element. It is a confusing concept that fortunately has been removed in Angular 2.
It seems anything remotely written in or affiliated with Javascript gets compared with Angular these days. AngularJS vs React.js AngularJS vs Node.js AngularJS vs Ember.js AngularJS vs Microwave AngularJS vs PHP AngularJS vs jQuery AngularJS vs Bear Grylls AngularJS vs AngularJS One thing I see being compared a lot is Angular and Meteor. Whoa. Hold on just a second there. Let us all just take a step back here for a moment. Angular and Meteor are not the same. They’re not even in the same league. Angular is a roller derby and Meteor is the stadium. While Angular can be used inside of Meteor and Meteor can be used in place of Angular, they are not the same.