Categories
JavaScript Web Development Year in Review

JavaScript in 2017: The Year of Stabilization

If 2016 was the year of JavaScript fatigue, 2017 was the year of JavaScript stability. No major framework wars. No revolutionary new tools that forced everyone to rewrite everything. Just steady iteration, performance improvements, and maturation of existing technologies.

This is less exciting than previous years, but more productive. The JavaScript ecosystem is growing up.

The Framework Landscape Settled

The big three frameworks solidified their positions:

React – Still dominant, especially in the U.S. React 16 shipped with Fiber, proving Facebook can execute large rewrites without breaking the ecosystem.

Categories
CSS Frontend Web Development

CSS Grid Is Finally Ready (And It’s About Time)

CSS Grid just shipped in Chrome, Firefox, and Safari within weeks of each other. After years of spec work and browser implementation, we finally have a proper layout system for the web. No more floats-as-layout. No more clearfix hacks. No more flexbox contortions.

This should be a huge moment. But here's the uncomfortable truth: most developers won't use Grid for months or years, because unlearning decades of CSS hacks is harder than learning Grid itself.

What Grid Actually Does

CSS Grid lets you define two-dimensional layouts—rows and columns—explicitly. Place items in specific grid cells, span multiple cells, create gaps, and it just works.

.container {
  display: grid;
  grid-template-columns: 200px 1fr 200px;
  grid-template-rows: auto 1fr auto;
  gap: 20px;
  height: 100vh;
}

.header {
  grid-column: 1 / -1; /* span all columns */
}

.sidebar {
  grid-column: 1;
  grid-row: 2;
}

.main {
  grid-column: 2;
  grid-row: 2;
}

This is what we should have had in 1998. Instead, we've spent 20 years stacking hacks on hacks because CSS wasn't designed for application layouts.

Categories
JavaScript Web Development Year in Review

JavaScript in 2016: The Consolidation Year

Last year's prediction was that 2016 would focus on consolidation over innovation. Looking back, that's exactly what happened. React solidified position, Angular 2 shipped, tooling matured, and new frameworks emerged without fragmenting ecosystem completely.

2016 wasn't "everything changed again." It was "things settled."

Framework Landscape Solidified

Categories
Mobile PWA Web Development

Progressive Web Apps: Real World Results

Progressive Web Apps launched as concept a year ago. Now we have case studies: Flipkart (India), AliExpress (China), Washington Post (US) all report significant metric improvements after building PWAs. The data suggests PWAs work—but the adoption pattern is interesting.

PWAs are succeeding most where app stores create most friction.

The Results Are In

Categories
Frameworks JavaScript Web Development

Vue.js 2.0: The Framework That Came From Nowhere

Vue.js 2.0 is in development and coming this year. What started as Evan You's personal project in 2014 has become a legitimate third option alongside React and Angular. Vue's growth, especially in Asia, proves a framework can succeed outside the Facebook/Google ecosystem.

The question is whether Vue's "progressive framework" philosophy is genuinely better or just different.

The Progressive Framework Pitch

Categories
HTTP Performance Web Development

HTTP/2 is Here and It Changes Everything (Theoretically)

HTTP/2 is shipping in browsers and servers throughout 2016. The protocol brings multiplexing, server push, and binary framing—fundamental changes that supposedly invalidate HTTP/1.1 optimization practices like domain sharding and sprite sheets.

Reality is messier. Not all browsers support it. Not all servers either. And some HTTP/1.1 optimizations still help. The transition period is awkward.

What HTTP/2 Changes

Categories
Frameworks JavaScript Web Development

JavaScript Frameworks in 2016: A New Hope

Two years ago, choosing a JavaScript framework felt like Russian roulette. Would it survive? Would it change completely? Would something better emerge next month? Starting 2016, those questions feel answerable. The landscape has stabilized enough to make informed choices.

This isn't declaring winners—it's acknowledging that viable options exist and the churn has slowed.

The Big Three Emerging

Categories
JavaScript Web Development Year in Review

JavaScript in 2015: The Maturation Year

Last year's post was titled "JavaScript in 2014: The Year Everything Changed (Again)." This year feels different. Not "everything changed again"—more "things settled into place." ES2015 shipped, React matured, patterns emerged. This was JavaScript growing up.

ES2015: From Experimental to Standard

ES2015 (ES6) finalized in June. But unlike most standards, developers had been using it for months via Babel. The finalization formalized what was already practice.

The shift from "experimental features" to "standard language" matters psychologically. Teams that resisted transpiling because ES6 felt unstable are now adopting it. Babel moved from optional to essential infrastructure.

Categories
APIs Backend Web Development

GraphQL: The REST API Alternative You Haven’t Heard Of

Facebook released GraphQL to open source this week. It's their internal data query language, used in production for years, now available for everyone. The pitch: instead of REST endpoints with fixed responses, clients query for exactly what they need.

This is radically different from REST, and if it catches on, it changes how we think about APIs entirely.

What GraphQL Is

Categories
CSS JavaScript Web Development

CSS-in-JS: Heresy or the Future?

The React community is experimenting with writing CSS in JavaScript—inline styles defined as objects, styling colocated with components, no separate stylesheets. This violates web development orthodoxy so completely that the reaction ranges from "interesting" to "what heresy is this?"

After building with CSS-in-JS approaches, I think the heresy might be onto something. But the trade-offs are real.

The Traditional Separation