Papercups VS Sapper

The best language for the task at hand, when presented with time constraints, is the one that you already know well. OP said in the article that they authored Papercups [1]. Adopting Elixir for a websocket-push service makes a lot of sense, then. However, why don't you learn Elixir, some OTP, and then reconsider that question? You could be missing out.

[1] https://github.com/papercups-io/papercups

https://github.com/papercups-io/papercups - 5.2k stars, uses Phoenix 1.6

Papercups

Phoneix - Elixir

We're a live message tool and it is basically what Elixir is built for https://github.com/papercups-io/papercups.

The Elixir community has been great and incredibly friendly. I originally was worried about the size of the community but that hasn't been an issue the community has been super helpful. I also think the annual stackoverflow usage surveys are very misleading because most of the community's questions get asked in ElixirForum and not on Stackoverflow.

Phoneix is the web framework of Elixir which is very similar to Rails but minus a lot of the magic has been very helpful for our productivity as well.

If I had to built another service that is websocket heavy I would definitely use Elixir. Even if it was a standard crud app I would still most likely choose Elixir.

Interestingly, the features page goes straight to github. With a list of features... followed by screenshots. So I found it!

https://github.com/papercups-io/papercups/wiki/Features

Yeah I agree, we're planning on updating the landing page to include a lot more screenshots/videos/demos :)

In the meantime, here are some screenshots from our GitHub wiki: https://github.com/papercups-io/papercups/wiki/Features

And our demo page: https://app.papercups.io/demo

I maintain the Papercups project, which is an open source customer messaging tool: https://github.com/papercups-io/papercups

Thanks for building this! Love this version I think this would work great for making and fixing bugs. I think automated tests and chores as a category would actually be great to add to this.

For our open source project (https://github.com/papercups-io/papercups). We participated in hacktoberfest recently and one problem we ran into is people submitting low quality PRs. Which ends up taking up way more time to review than to merge.

I would love to be able to filter by users who have merged multiple issues or some sort of quality bar for our bounties. Obviously since you are just starting out your users won't have too many issues merged. You might be able to work around this by finding the number of Github issues an author have merged previously to any projects that is greater than x number of stars. This way you might be able to bootstrap some credibility of the authors. Then maybe a contributor can gate on only allowing some reputable contributors.

One inspiration I would recommend is taking a look at how 99designs has different tiers of designers you can have a bounty for your design. If you could build 99design for open project that would be amazing. Best of Luck!

An open source live chat tool for customer support https://github.com/papercups-io/papercups

We launched on August and have been steadily getting some traction and building a little community in our Slack channel

I built my first simple blog site in 2020 using Svelte and Sapper. The blog posts were powered by markdown files stored in the repository, and it was a great starting point.

Sapper

pancake which has very scarce documentation and is in thorough experimentation(at the time of writing). Since it has been created by Rich Harris, you can rest assured that it might probably never get documentation or a stable release just like our fallen soldier sapper (a moment of silence in remembrance)

SvelteKit can be considered the successor to Sapper or NextJS for Svelte. It is packed with tons of cool features, like server side rendering, routing, and code splitting.

So after using Sapper for some time, I decided to move my website to SvelteKit. I remember saying that I would not move to SvelteKit till they hit version 1 but the framework looks too promising. It had features which I needed and those features weren't in Sapper.

By that time, we had some troubles with virtual dom itself in our custom rich text editor that we based on slate - it was getting a bit laggy when creating huge financial documents (they usually have enormous tables and a lot of infographics) -so we were already thinking about other options and that’s where svelte comes into the light - especially sapper which was de facto default framework to be used with svelte at that time (SvelteKit wasn’t even announced).

Sapper is a framework for building web applications of all sizes, with a beautiful development experience and flexible filesystem-based routing. It is the predecessor of Sveltekit.

Sapper - ecossistema Svelte

Lol I won’t, and to answer your question, it’s built using sapper: https://sapper.svelte.dev

I maintain a Svelte Starter Kit and all I had to do between several updates is change the layout file names, simplify the hooks, and convert the config file extensions. If you're learning Svelte in 2021, you shouldn't miss learning it, as it's "the missing CLI" and the svelte team's favoured project structure, to build full-stack server rendered and static sites, with File/Folder based routing, focus on server-less with adapters, API routes, and good baked-in conventions and constructs to support common web app needs. It's a successor to Sapper which served the aforementioned needs, with exception of adapters, which is special/unique(with no officially provided parallels in Next.js/Nuxt ecosystems yet) way to make vendor-agnostic, server-less first deployment concern a seamlessly integrated part of the framework.