As a developer I approach new platform features with a healthy amount of skepticism. You don’t have to look too far into this blog’s archives to find me complaining about the Apple Watch, web components, and plenty of other trendy technologies. The latest of these trendy technologies seems to be progressive web apps, which the greater web community — most notably Google — has been pushing heavily
I am done using outdated and non-standard module solutions. I have been waiting a long time for ES6 modules and I want as much ES6 as I can get...today! I want all of this without having to choose, or without being forced to choose, one specific packaging registry over another. So, let me get straight to the point. I believe when starting a new front-end development (i.e. a SPA or native browser a
A few weeks ago, HTML5 became an official W3C Recommendation. I took advantage of this event to discuss 5 interesting but now obsolete features on SitePoint. The problem is that the W3C specifications are only one side of the same coin. Starting from this version of HTML, developers and browser vendors can choose between two different flavors of the same markup language: the specifications develop
Web components are the new hotness. And now that a complete web components implementation landed in Chrome 36, we finally have stable, unprefixed, unflagged version to try out. But, although web components are certainly something to be excited about, and a technology worth experimenting with, that doesn't mean that they're ready to use in your production applications — because for most application
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く