仕事で WebRTCYou signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Releasing Prettier 1.0
This post was written by vjeux and edited by jlongster. We officially announced prettier over two months ago as a way to solve the problem of wasting time formatting your code. It started as an experiment but it clearly resonated with a lot of people, amassing ~7000 GitHub stars and over 100,000 monthly npm downloads in just two months. In case you don't know, prettier is a JavaScript formatter th
How I learn any front-end framework
You decided to learn x framework, You open youtube or any search engine you prefer to search for any tutorials related to this “x” framework and suddenly after 30 min you scream “Eureka”, I think this framework is similar to my previous framework and you are right you don’t have to learn it from scratch, In this post I will show to you my experience to learn frontend frameworks and how those frame
Moving Airbnb Search to React
In early 2015, the Airbnb Engineering team decided to embrace React as its canonical front-end view framework. We’ve since built a significant amount of tooling around React to make it as pleasant an environment to develop in as possible, and we’ve contributed a lot of these tools back to the open source community. Unfortunately, because our search page was written using a largely unmaintained fra
JavaScript isn’t just JavaScript
2016 was the year of “JavaScript fatigue”. The idea that JavaScript has become too fractured and entrenched in tools. It’s now harder than ever for a developer to get a project started, let alone finished. On a surface level it makes a lot of sense. The last several years have seen a massive shift in the way front-end development works. Frameworks, bundlers, transpilers; even a massive update to t
Dear JavaScript,
This article has been moved to: http://thejameskyle.com/dear-javascript.html. “Dear JavaScript,” is published by Jamie Kyle.
Avoiding a JavaScript Monoculture — SitePoint
This article was peer reviewed by Tom Greco, Dan Prince and Mallory van Achterberg. Thanks to all of SitePoint’s peer reviewers for making SitePoint content the best it can be! JavaScript, as a language, has some fundamental shortcomings — I think the majority of us agree on that much. But everyone has a different opinion on what precisely the shortcomings are. Christoffer Petterson recently wrote
JavaScript fatigue fatigue
Enough with the fatigue – tips against feeling overwhelmed: Don’t try to know everything – it’s impossible in modern web development. Given that there is always more to know, it doesn’t matter that much what you learn (unless you have a specific need). Go for depth in areas you love. Go for breadth and on-demand learning in areas you are merely interested in or think you should know more about. Wa
Javascript Fatigue
A few days ago, I met up with a friend & peer over coffee. Saul: “How’s it going?” Me: “Fatigued.” Saul: “Family?” Me: “No, Javascript.” More accurately, I meant React and the Javascript ecosystem that comes with it. For starters, consider that Pete Hunt asked why React is overwhelming for beginners: There is a major problem in the React community that cripples beginners and hinders experts alike.
2016 will be the year of concurrency on the web
Since 2009 JavaScript programming on the web has a way to write concurrent programs using shared-nothing threads: Web Workers. But beyond some specialized use cases (e.g. Google Photos uses them for running some filters that need a lot of CPU) they haven’t seen any mainstream adoption. This will change in 2016. The 2 main reasons are: Virtual DOM has given us a programming model on the web that wo
JavaScript Frameworks and Mobile Performance
Critics of frameworks tend to totally miss the value that they provide for people. Google’s Paul Lewis recently wrote The Cost of Frameworks, analyzing the performance implications of using JavaScript frameworks on mobile devices. Here’s Paul’s list of why people use frameworks: Frameworks are fun to use. Frameworks make it quicker to build an MVP. Frameworks work around lumps / bugs in the platfo
JavaScriptの情報の仕入れ方 - mizchi's blog
ぼくのフロントエンドの情報収集ソース | Yuhiisk みたけど多すぎて逆に機能不全になると思う。 自分が主に見てるのは次の2つ。 efclのはてなブックマーク JSer infoのazuさんのはてブ。 Echo JS - JavaScript News Hacker News のJS版みたいなもの これを読み流すんじゃなくて、LDRで一件一件丁寧にみてる。日本語圏で再生産され続ける情報に意味があるもの少ないので、上流とまとめだけみればよい。
Not forcing super in derived class's constructor?
TLDR: If this is used without super (which should be statically analyzable), let it refer to Object.create(new.target.prototype). Otherwise, let super creates what it refers to. I know the reason to force super in derived class's constructor is to make sure this refers to the exotic object the base class might allocate. But I bet in real world, extending base classes who only create ordinary objec
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Prettier for CSS · Issue #2532 · stylelint/stylelint
Rename your project to avoid confusion with ECMA standard · Issue #784 · standard/standard
Domain error
Awards in Open Source
Learn Vanilla JavaScript Before Fancy Frameworks
What is Javascript Fatigue? + How It’s Evolved Over Time
Ember.js 2.0 Celebrated for Backwards Compatibility