Ok let's stop writing UT and see what happens. Wait... we've already tried that, and we know the result pretty well:1. In dynamic languages, simple type mismatches, wrong variable names etc. are now caught in "top level system level test". Yes these are bugs that should have been caught by a compiler had we had one. 2. There's no documentation as to how something should work, or what functionality
This is really neat. Though in practice if you are using this kind of thing I'm pretty sure you will want to combine it with atlasing (i.e. construct an atlas of glyphs via render to texture). That's because it's a waste of time to rerasterize glyphs in the FS every frame (which appears to be 200+ lines) instead of caching the results and reducing the per-frame work to a 5-line FS that just blits.
The question I have: what's the advertisers' next move after iOS 9 drops?Feels like there are a few possibilities: - Nothing: the impact of users who install these plugins is minor. - They sue Apple. Feels like a short game. - Try and game the system: multiple domains to serve trackers and ads, etc. - They adjust their technology stack to serve fewer ads and reduce page bloat. - They put up paywal
This is absolutely a NIGHTMARE for new developers. People come into the language, and there are what seems like an infinite number of "the only right" ways to do something, all of vary degrees of complexity/usefulness, and all claiming that they are god's gift to computer science.That last part is the part that is most frustrating to me, and it isn't unique to javascript. Google, facebook, yahoo,
I think this quote speaks volumes - "WebAssembly has so far been a joint effort among Google, Microsoft, Mozilla, and a few other folks." Sometimes I think maybe, just maybe the W3C and other web standards groups finally have some wind behind their sails.It may have taken a while, but with all these individuals and organizations cooperating in an open space, we may finally advance yet again into a
The other major issue is backwards compatibility. Ruby and Python have large API surfaces on both the C API and scripting language sides, with many libraries making use of obscure language features. If any single one of those features doesn't work, the library won't. Witness how tough the Python3 migration has been.I talked with the Unladen Swallow guys sometime after the project was canceled. The
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く