The last few years have been difficult for the jQuery UI and jQuery Mobile projects. The projects have suffered from lack of resources and funding and loss of contributors due to a variety of factors. These combined factors have nearly stopped development on both projects. To remedy this situation they have decided to make some changes in the projects’ teams in addition to how they work.
It's easy to get into a heated discussion about frameworks, what type of class names make the most sense, which optimization techniques are most important, or what part of your code base is should be responsible for styling. Those are great discussions that guide our industry.
But what is more important? The naming convention you chose or if your user can actually book a flight?
The critical vulnerabilities found in Intel and other CPUs represent a significant security risk. Because the flaw is so low level, the usual protections that web developers are used to don't apply. Even sandboxed JavaScript code can be used to exploit the vulnerabilities known as Meltdown and Spectre.
Tinder recently swiped right on the web. Their new responsive Progressive Web App is available to 100% of users on desktop and mobile, employing techniques for JavaScript performance optimization, Service Workers for network resilience and Push Notifications for chat engagement. Today we’ll walk through some of their web perf learnings.
The statistics from GitHub over the past 3 years showed a compelling rise in the number of projects that uses JavaScript static typing. Be it TypeScript, Python, PHP, AtScript or Flow, developers are showing more interest in embracing static plugins over dynamic.
Promises are a nice addition to JavaScript, but they don't come without a cost. They allow you to write your code more structured than with plain callbacks, but, like with every abstraction, you have to understand them or they will bite you.