Week 36 - 2020
The weeknote for 8/31 - 9/6.
OSS
denoland/deno
🦕 Deno is a new JavaScript and TypeScript runtime
-
Contributions
-
https://github.com/denoland/deno/pull/7314
Found an issue #7308 and solved it in #7314. I first realized in it that
decodeURIComponent
doesn't parse query (search) param correctly, but we need to.replace(/+/g, ' ')
before applying it 🤔
-
-
Applications
- This week I found a deno application, GitHub Profile Trophy. This is written in Deno using vercel-deno builder and therefore deployed to vercel. I think this app is significant in the sense that the author used deno for trying to invent something new in software space, not just reinvent something already existed out there.
開発しました。GitHubを利用している方、是非、個人開発や学習のモチベーション維持に。
— ryo-ma (@Skeinin) August 30, 2020
🏆 GitHubのプロフィールをイケイケにするトロフィー(活動実績)が表示できるサービスの開発および公開した話 https://t.co/RhN2ZBtwgO #Qiita #駆け出しエンジニア #個人開発
romefrontend/rome
Rome is a new frontend toolchain.
- Last week I wrote that rome was disappointing because it didn't provide the modification ability of lint rules and enforces the hard tabs to all users. That changed this week. Now those are simply configurable! 🎉 See #1163.
curl/curl
-
Curl now supports MQTT by default. It's very interesting to see such old software still developing dynamically.
curl: MQTT support is now enabled by default. No longer considered "experimental".https://t.co/c0kOffRXnK
— Daniel Stenberg (@bagder) August 31, 2020
tc39/proposal-decorators
-
To my surprise, @littledan started again a new draft of decorators proposal. This time he simplified it very much and maybe it's the simplest to the users, the decorator authors, and the implementors of the engines. It's very similar to python's decorator. Especially the semantics and the way to evaluate decorators is very very similar to python.
I've never expected this new version happens because decorators proposal have been already defeated 4 times and there seemed no reasonably way to continue it anymore. I was really surprised his undefeatable mind 😵
I'm also very surprised the simplicity of this version of the proposal. This one obviously lacks the feature to "add" new properties to the prototype of the class, and that's the point of this version. We can modify only the decorated methods, not able to modfiy arbitrary property of the prototype. That simpifies the implementation of both engines and transpilers. Thus it's named "simplified" decorators.
The evaluation of the decorator happens after the evaluations of the other elements. That's basically the same as the python version. So this proposal, in my view, is the same in most aspects as the python's version. The idea of decorators were derived from python's decorators, and we tweak it a little to align it to the Object.defineProperty's signature. That caused the problem in the evaluation of order of class elements and decorators, and the 1st decorators were rejected. The 2nd decorators addressed that evaluation order problem, but it became too complicated. The transpilation of the 2nd decorators were totally huge and at the level of suffering the web ecosystem. Then it was rejected. The 3rd proposal, static decorators, tried to address that complexity, but it introduced totally new syntax elements and that caused the traspilation very difficult. Then it was rejected. The 4th decorator shed lights to how to implement field decorators, but didn't address the previous issues at all, and it was rejected. After such very long detour, we finally try to simply mimic the python's decorator. I found it's a very interesting story.
MyProejct
kt3k/generator-lepont-bridge
- Created a yeoman geneartor for a lepont bridge, generator-lepont-bridge. You can generate a scaffold of lepont bridge, and easily start the development of a new bridge (A lepont bridge is a plugin of lepont which handles some specific function of react native and bridges between react native and webview).
kt3k/lepont-platform
- Using the above generator, I created a new lepont plugin, lepont-platform. lepont-platform provides the function of accessing the platform information from the webview.
kt3k/shuho
-
Switched the css theme of Shuho (this weekly report website) from new.css to sakura.css. I also tries ridge.css and Marx. Sakura was by far the best among these classless css frameworks and now my best favourite classless css framework!
やっぱり sakura の方が圧倒的に良いので、sakura に変えよう・・・
— Yoshiya Hinosawa (@kt3k) August 31, 2020
← marx
→ sakura pic.twitter.com/oQprrXqsul
Life
Iyo's kitchen
-
This week's Iyo's kitchen!
#kt3kmeal 豚モヤシ、ひじき、梅干し、卵焼き、麦みそ汁と雑穀ごはん pic.twitter.com/6edUilGgld
— Yoshiya Hinosawa (@kt3k) August 31, 2020#kt3kmeal ラタトゥイユ、ジョンソンヴィルソーセージ、他 pic.twitter.com/ln1mJK1GMr
— Yoshiya Hinosawa (@kt3k) September 1, 2020肉豆腐の下準備完了!
— あずき (@okomekirai) September 3, 2020
味がしみてないのでまた一晩寝かせます😴
煮物は崩れてしまうのが嫌なので、最低限火にかけてあとはアルミホイルで蓋をして余熱で煮込み、一晩冷蔵庫に入れて次の日食べる派です🍳 pic.twitter.com/oI2hb9Yd7eたまごやき綺麗にできました🍳 pic.twitter.com/yxVH4vMa43
— あずき (@okomekirai) August 31, 2020
Weekend
-
Went to Tiffany's Cafe in Harajuku on Saturday together with Iyo-chan.
ティファニーカフェきゃわ🥰 pic.twitter.com/oetGoIeA7R
— あずき (@okomekirai) September 5, 2020