How big is the backend bundle?
Linen.dev: A 500 kb Slack alternative
161–170 of 219 posts
Re: Linen.dev: A 500 kb Slack alternative
#162Not enough discussion here of the parts under "Our Optimization Strategies", which was the most interesting to me. Assorted reactions: > We found that react-icons had an issue that lead to everything being imported. This meant that we were including every single react-icon in our package whether we need it or not. Kudos to the Linen team for proactively finding this - I have a feeling tons of projects blindly trust t…
> tree-shaking
Always fascinated when I hear that JS term for what's essentially dead code elimination.
Re: Linen.dev: A 500 kb Slack alternative
#163Not enough discussion here of the parts under "Our Optimization Strategies", which was the most interesting to me. Assorted reactions: > We found that react-icons had an issue that lead to everything being imported. This meant that we were including every single react-icon in our package whether we need it or not. Kudos to the Linen team for proactively finding this - I have a feeling tons of projects blindly trust t…
With icons, I've stopped using icon libraries a while back and now import just the SVG code that I need. I'm a big fan of Hero Icons[1] and they offer a way to quickly copy JSX or SVG code to the clipboard to faciliate this workflow. [1]: https://heroicons.com/
If we're listing icons, I use these ones: https://ionic.io/ionicons/
They provide a full framework but you can also download SVGs.
Re: Linen.dev: A 500 kb Slack alternative
#164Earlier quoted context omitted.
They are positively fixated on being "google searchable" in a way that is really bizarre.
It's because a lot of projects - not just open source (hell, my laptop manufacturer is now linking to their Discord for support) - have moved their support to Discord, and finding anything on Discord is a huge pain, even if their indexer decides to work that day.
There's a different problem I'm not sure if they've addressed, namely that Google chooses what it wants to index and finds relevant, meaning it's not certain your data will be indexed.
Re: Linen.dev: A 500 kb Slack alternative
#165Not enough discussion here of the parts under "Our Optimization Strategies", which was the most interesting to me. Assorted reactions: > We found that react-icons had an issue that lead to everything being imported. This meant that we were including every single react-icon in our package whether we need it or not. Kudos to the Linen team for proactively finding this - I have a feeling tons of projects blindly trust t…
> tree-shaking Always fascinated when I hear that JS term for what's essentially dead code elimination.
As far as I understand it, that's because it's different. Dead code elimination analyses the code and removes paths that can't be executed.
Tree shaking only looks at the imports and removes code that isn't imported from the bundle. If code is imported but not executed, then tree shaking won't remove this code, even though it is dead code.
Using a different term is reasonable to avoid confusion, in this case.
Re: Linen.dev: A 500 kb Slack alternative
#166Earlier quoted context omitted.
It's because a lot of projects - not just open source (hell, my laptop manufacturer is now linking to their Discord for support) - have moved their support to Discord, and finding anything on Discord is a huge pain, even if their indexer decides to work that day.
There's a different problem I'm not sure if they've addressed, namely that Google chooses what it wants to index and finds relevant, meaning it's not certain your data will be indexed.
I think that's more down to "Google" being a stand-in for any search engine. Had they written "indexable" the intent would have been less clear.
Re: Linen.dev: A 500 kb Slack alternative
#167Not enough discussion here of the parts under "Our Optimization Strategies", which was the most interesting to me. Assorted reactions: > We found that react-icons had an issue that lead to everything being imported. This meant that we were including every single react-icon in our package whether we need it or not. Kudos to the Linen team for proactively finding this - I have a feeling tons of projects blindly trust t…
With icons, I've stopped using icon libraries a while back and now import just the SVG code that I need. I'm a big fan of Hero Icons[1] and they offer a way to quickly copy JSX or SVG code to the clipboard to faciliate this workflow. [1]: https://heroicons.com/
Icones is my go to https://icones.js.org/
Re: Linen.dev: A 500 kb Slack alternative
#168Not enough discussion here of the parts under "Our Optimization Strategies", which was the most interesting to me. Assorted reactions: > We found that react-icons had an issue that lead to everything being imported. This meant that we were including every single react-icon in our package whether we need it or not. Kudos to the Linen team for proactively finding this - I have a feeling tons of projects blindly trust t…
With icons, I've stopped using icon libraries a while back and now import just the SVG code that I need. I'm a big fan of Hero Icons[1] and they offer a way to quickly copy JSX or SVG code to the clipboard to faciliate this workflow. [1]: https://heroicons.com/
ditto for https://iconduck.com/
Re: Linen.dev: A 500 kb Slack alternative
#169Commendable, but I am sure there are alternatives that ran on machines with less than 500KB of memory.
Slack is mostly IRC with persisted history and threads.
Re: Linen.dev: A 500 kb Slack alternative
#170I don't understand. Is this just the frontend or backend?