1 of 35

Why I like Rich Harris

(5min)

baseballyama

2 of 35

Rich Harris の好きなところ

(5 min)

baseballyama

3 of 35

Who I am

Yuichiro Yamashita / baseballyama

  • Software Engineer@Flyle
    • Flyle is SaaS company that provides product management platform
    • One of major worldwide competitor is ProductBoard

  • Team member of @sveltejs since 2022
    • I’m working for Svelte core and ESLint
    • I’ll contribute for Svelte 4 in earnest 😆

4 of 35

Who is Rich Harris

5 of 35

Who is Rich Harris

  • Rich Harris is an Emmy award-winning visual journalist
  • Creator of
    • Rollup
    • Svelte
    • SvelteKit
  • employee of Vercel

6 of 35

Why I like Rich Harris

7 of 35

8 of 35

Why I like Rich Harris

I shared with the rest of Svelte core team and which Conduitry not everyone and software development to share is we just hate complexity.

I for one, I feel like I have a very low threshold and I get bored easily and eyes glaze over a lot of times when I’m learning a new technology.

It’s the reason that I haven’t yet got around to learning any language other than JavaScript and TypeScript is because I don’t think I’m smart enough to learn how to use a lot of the things that people use in software.

If you have that instinctive reaction like “no this is too much, this is too complex, this is unnecessary, this doesn’t feel right”, then I think you will naturally end up rejecting designs that that involve unnecessary complexity. The trick is to make things simple as they can be but no simpler because sometimes it’s possible to make things too simple and then lose flexibility and power in the process.

If I have one piece of advice for software developers it’s like develop the ability/sense of taste that says “no this is too complex”, we need to rethink this because it is very easy to like complexly creep into software and once is there, you will not get rid of it.

9 of 35

Why I like Rich Harris

私はConduitryを含むSvelteのコアチームの少なくとも一部と複雑さを嫌うという考えを共有しています。

私自身、閾値が非常に低く、すぐに飽きてしまい、何度も新しい技術を学ぶことを挫折しました。

私がJavaScriptとTypeScript以外の言語をまだ学んでいないのは、自分がソフトウェアで使われている多くのものの使い方を学べるほど賢くないからです。

もしあなたが「これはやりすぎだ、複雑すぎる、不要だ、しっくりこない」という本能的な反応を持っているなら、不要な複雑さを伴うデザインは自然に拒否することになると思います。シンプルになりすぎると、柔軟性やパワーが失われてしまうこともありますが。

ソフトウェア開発者へのアドバイスとして、「これは複雑すぎる」というセンスを磨くことです。ソフトウェアに複雑なものを忍び込ませるのはとても簡単で、一度忍び込んだら抜け出せませんから。

10 of 35

Why I like Rich Harris

  • We just have complexity
    • Only one way to do things
    • The way should be refined

11 of 35

Only one way to do things

12 of 35

Only one way to do things

{:elif ...} is terse without helping the developer.

Code is read many more times than it is written. And we only want one way to do things if at all possible. Wanting another compiler option to select which syntax should be allowed in a given codebase demonstrates why supporting both is a bad idea. wiwa reacted with t

13 of 35

Only one way to do things

{:elif ...}は、開発者の助けになることなく、簡潔です。

コードは書いた回数よりも何度も読まれるものです。そして、私たちは可能な限り一つの方法で物事を進めたいのです。あるコードベースでどの構文が許されるかを選択するために別のコンパイラオプションを望むことは、両方をサポートすることがなぜ悪い考えであるかを示しています。

14 of 35

The way should be refined

15 of 35

The way should be refined

16 of 35

Wrap Up

I really sympathized with Svelte way to do things.

Therefore I started to contribute to Svelte.

17 of 35

Status of Svelte in Japan

(5 min)

baseballyama

18 of 35

日本におけるSvelteの状況

(5min)

baseballyama

19 of 35

Meta Information

20 of 35

Community Size

Over 500 members are there

21 of 35

22 of 35

Visitor Volume of Japanese Documentation Site (2023 JAN)

Svelte

React

23 of 35

Visitor Volume of Japanese Documentation Site (2023 JAN)

発表後の追記 :

Svelteのサイトへのアクセス数が少ないのは、そもそもサイトを何度も見ることなくコーディングできる、という観点もあるのではないか、という意見を頂きました。

確かにそれもあるかもしれません。1度ドキュメントを読んだら直感的に理解できるので、以降は自然とコーディングできる。

24 of 35

25 of 35

Case Examples in Japan

(Web Application)

26 of 35

Ateam LifeDesign Inc. (Parent company is Listed company)

Using Svelte and SvelteKit

They decided using Svelte and SvelteKit in terms of learning cost.

For them, even designers can implement a markup section is important.

27 of 35

nextbeat Co., Ltd.

Using Svelte and SvelteKit in their core product

They decided using Svelte and SvelteKit in terms of learning cost and less code.

And they are organizing Svelte study group eagerly.

28 of 35

NIFTY Corporation (Listed company)

Using Svelte and SvelteKit in their internal tools / small products

They decided using Svelte and SvelteKit in terms of learning cost.�NIFTY is ISP company, therefore engineers don’t have much knowledge about frontend. �Svelte / SvelteKit is resolved this knowledge issue.

29 of 35

Case Examples in Japan

(Others)

30 of 35

note inc. (Listed company)

Frontend App spliting by Next.js + Svelte

They develop shared UI component by Svelte instead of Web Components in terms of Bundle size and SSR.

31 of 35

Flyle (My Company😆)

Form UI is written in Svelte

This UI is run on our customer’s website. Therefore less bundle size, less memory, less CPU usage is important.

32 of 35

And more and more companies use Svelte / SvelteKit!

Listed Companies / Parent company is Listed companies

Private Companies

And more and more…

33 of 35

Special Thanks

To create this presentation, I got many support to gather information.

  • tomoam / Svelte Japan core member�Twitter : @tomoam_mat
  • takenokoroid / Software engineer at NIFTY.�Twitter : @takenokoroid

And all Svelte Japan comunity members!�Many members gave me information!�(https://discord.com/channels/777141291800723468/1074984555578146846)

34 of 35

Referenced Information

I researched information on 18th FEB.

35 of 35

Svelte Search Volume

in Japan

Svelte Search Volume

in Japan