500KB seems to be the bundle size, how much RAM does the client use?
At https://www.linen.dev/s/linen Page open: Firefox: 18.5MB Chrome: 12.1MB After browsing: Firefox: 27.14MB Chrome: 11.7MB
Linen.dev: A 500 kb Slack alternative
81–90 of 219 posts
Re: Linen.dev: A 500 kb Slack alternative
#82Earlier quoted context omitted.
It appears that they used Webpack, which I found interesting given other alternatives.
The UI package appears to use Rollup. And this looks like the PR for the icons update: https://github.com/Linen-dev/linen.dev/pull/1001
Re: Linen.dev: A 500 kb Slack alternative
#83Earlier quoted context omitted.
At https://www.linen.dev/s/linen Page open: Firefox: 18.5MB Chrome: 12.1MB After browsing: Firefox: 27.14MB Chrome: 11.7MB
You must probably be using 16-bit computer because on my x86_64 system Firefox's about:processes tab shows 45-65 Mb of RAM usage after opening this page and scrolling. And Firefox's builtin tools tend to show smaller number than real usage: htop shows use of 85 Mb of PSS (proportional set size, that properly accounts for pages shared between processes).
Doing a heap snapshot will give you a better view of the page memory usage in isolation, without involving the browser itself.
Re: Linen.dev: A 500 kb Slack alternative
#84Earlier quoted context omitted.
We do have a paid offering. Basically it's free on Linen's domain for public communities and we let you host on your domain like: https://archive.pulumi.com/ https://linen.prefect.io/ https://slack-chats.kotlinlang.org/
And you guarantee in writing that this pricing structure will never change?
Initial and middle Investors kept passing the pie to the next bigger fool and the last bigger fool is now stuck with a very expensive web property desperate to recoup the investment let alone a 10x return.
Sounds like a Bitcoin food chain.
And then - aggressive monitization, price hikes staff cuts, SLAs adjustments etc.
Re: Linen.dev: A 500 kb Slack alternative
#85Earlier quoted context omitted.
And you guarantee in writing that this pricing structure will never change?
VC game will get crazy. Most VC backed products will have their end day like Twitter has almost. Initial and middle Investors kept passing the pie to the next bigger fool and the last bigger fool is now stuck with a very expensive web property desperate to recoup the investment let alone a 10x return. Sounds like a Bitcoin food chain. And then - aggressive monitization, price hikes staff cuts, SLAs adjustments etc.
Re: Linen.dev: A 500 kb Slack alternative
#86Not 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…
The intro community discussion page at https://www.linen.dev/s/linen does need to load 20+ javascript files for some reason to show the latest messages.
Whereas messages still show up even if javascript is entirely blocked, just starting from the beginning in 10/2022 (?).
So I'm not quite sure if it's as optimized as it can be.
Re: Linen.dev: A 500 kb Slack alternative
#87It's usually a call you need to make based on what you're shipping, but at the very least, it'll ensure you don't blow up your performance because something slipped by.
Finally, looking at the components of your bundle if you haven't already is well worth it. Like the people over at Linen noticed, they were shipping a ton of icons they were never using. This is happening all over the internet, and it's a real drag on the network, parsing, and executing phases in a browser. If you benchmark, you'll see significant differences when you trim things back.
If you have customers using lower powered devices, this is even more crucial.
Re: Linen.dev: A 500 kb Slack alternative
#88Not 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…
Re: Linen.dev: A 500 kb Slack alternative
#89We actively evaluated Linen in launching our community. Although, we went with discourse as we are going for a forum type community platform but Linen certainly has fantastic potential. One very minor friction point with Linen was, it needs to be a bit transparent about their pricing for business tier. I don't think "contact us" pricing strategy is the perfect fit Linen's target audience.
For anyone interested in HN-type forums (with lots of other features we've built)
Re: Linen.dev: A 500 kb Slack alternative
#90the Show HN: https://news.ycombinator.com/item?id=33248488 and there was another thread last year for their main domain https://news.ycombinator.com/item?id=31494908 I wish all the locked away Slack communities would use Linen[1] because there are so many nuggets of bug-fixery buried in Slack that will age off or never be found in the horrors of Slack search 1: I really wish they'd just stop using Slack entirely sinc…
Tell me more about Zulip?
I haven't used it yet, but in general excited by projects like Linen and Zulip. I hate Slack and Discord (I love the web, deep links, and indexability/searchability)