Back

Week 35 - 2020

The weeknote for 8/24 - 8/30.

OSS

denoland/deno

🦕 Deno is a new JavaScript and TypeScript runtime

• Contributions
  • Fix a test case of //cli/flags.rs at #7236.

romefrontend/rome

Rome is a new frontend toolchain.

• Rome is a revolutionary tool or at least it aims to be a revolutionary tool. It supports almost the entire process of frontend development by the only one single cli tool without any external dependencies. It could be the most significant masterpiece of frontend development if it attained what it first promised. This week I tried to use rome check (the linter) in one of my old projects to replace the usage of lynt because lynt now seems unmaintained and I don't want to set up the so combersome typescript-eslint configuration. In it I found this issue. It suggests that rome should use tabs for indentation for the purpose of accessibility. @sebmck accepted the proposal and now rome uses tabs. What I found is a problem there is that rome doesn't provide the way to configure it. We can't choose 2 spaces for indentation 🤔 That's comparably small thing but what I found that I can never agree is that it enforces no-explicit-any rule for TypeScript source code. I agree that any is a bad thing but I sometimes can't find a way to avoid it. The very good part of TypeScript is its so tolerable approach to bad code. TypeScript always gives a way to compile to any JavaScript code no matter how badly typed they are. I believe any JavaScript code can be transformed into TypeScript without changing semantics and that's possible because TypeScript can be so loose in typing. I think that "loose" character of TypeScript is the great strong point of it to promote its adoption. However if you use rome, it enforces no-explicit-any so you can't use any and you can't configure it. That means you can't use rome if your code is "bad". My library capsid needs to use any and I don't know the way to avoid it at the moment. So that means I'm literally unable to use rome at the moment because of this restriction 😬

MyProejct

monoidcc/Tententen

• Finally I was successful at saving images on Huawei Android devices! 🎉 (The commit). The modules I used in the final successful form were react-native-fs, @react-native-community/cameraroll and PermissionsAndroid of react-native. The modules I couldn't use for this purpose were react-native-share (and any other sharing libraries) and react-native-file-provider (unable to compile because it's too old). I also tried <a download /> but it didn't work because it doesn't handle data: uri scheme (The error message says they don't support it).

  I finally understand the correct way to save the image on the device's camera roll. So the next step is finally finish the UI and ship it to App Store and Google Play 👍 However before that I would create some lepont modules to make it easy to reuse the above process in the next similar apps.

  #tententenapp やっとアプリからカメラロール保存出来ただよ pic.twitter.com/bDPv9oEJek

  — Yoshiya Hinosawa (@kt3k) August 27, 2020

Life

Iyo's kitchen

• Iyo-chan was a great chef this week again!

  #kt3kmeal そうめん、天ぷら pic.twitter.com/C53QpkOAEj

  — Yoshiya Hinosawa (@kt3k) August 24, 2020

  🥰 pic.twitter.com/QRC0gwdbTF

  — あずき (@azukimeal) August 26, 2020

  #kt3kmeal 生姜焼、お野菜、みそ汁、とうふ、ご飯 pic.twitter.com/hkThJ56ho6

  — Yoshiya Hinosawa (@kt3k) August 27, 2020

  #kt3kmeal 肉じゃが pic.twitter.com/nzJll6rY08

  — Yoshiya Hinosawa (@kt3k) August 28, 2020

Toshi Yoroizuka

• Iyo-chan and I went to Toshi Yoroizuka in Roppongi Midtown this weekend. Toshi Yoroizuka is a fancy sweet shop in Tokyo. We had special parfaits and they were so delicious 😋

  #kt3kmeal Toshi Yoroizuka パフェ pic.twitter.com/hibbB8hSZK

  — Yoshiya Hinosawa (@kt3k) August 28, 2020

Back

Edit this page