Topics /

Web & Frontend

The most popular blog posts about web & frontend on Hacker News. 480 posts.

2018
334

Chrome developer tools to master

With the advent of modern frameworks, ES6 and the increasing risk of security everyday, knowing how to use Chrome developer tools can give you a major boost in productivity and help in easy diagnosis of a website’s performance. This article aims to give an overview of different features available in Chrome developer…

338

OAuth for the Open Web

OAuth has become the de facto standard for authorization and authentication on the web. Nearly every company with an API used by third party developers has implemented OAuth to enable people to build apps on top of it.

340

React v16.6.0: lazy, memo and contextType

This blog site has been archived. Go to react.dev/blog to see the recent posts. Today we’re releasing React 16.6 with a few new convenient features. A form of PureComponent/shouldComponentUpdate for function components, a way to do code splitting using Suspense and an easier way to consume Context from class…

347

Introducing the Apollo GraphQL Platform

We started Apollo in 2016 with the objective of lowering the barriers to making high-quality, modern apps. Since then, we have seen tremendous growth in our community with nearly 500,000 downloads per week and companies like Audi, the New York Times, Airbnb, and CNBC all making strategic commitments to GraphQL. With…

349

Rust and QML: a timely example

A brief recap. The new project Rust Qt Binding Generator can create bindings between Rust code and Qt code. You can use Rust code to power your Qt application. Or in other words, you can use Qt as a cross-platform user interface for your Rust application.

359

The mysterious case of missing URLs and Google's AMP

When I saw a speculative article about Google wanting to “kill” URLs appear in my news feed, I didn’t think too much about it. Trying to hide “ugly” URLs… well, that feels like a natural thing for an app to try and do. Designers of apps often (erroneously) assume that users cannot cope with “technical” things like…