Kitemaker VS Linear

When we built Kitemaker [0] we elected to not use CRDTs. We built our sync engine after reading the blog article Figma wrote about they didn't need CRDTs because they have the server arbitrating any conflicts. We ended up taking the same approach. It's worked out very well for us though in a tool like our "last one in wins" generally works fine and doesn't lead to a lot of surprises. For documents, we had to do... - Source: Hacker News / about 2 months ago

There is no one-size-fits-all approach to writing descriptions, so you need to figure out what works best for you and your team. However, seeing real-world examples might inspire you to find new ways to write them. Here are some examples from descriptions we have written for Kitemaker. - Source: dev.to / over 1 year ago

Kitemaker.co - Collaborate through all phases of the product development process and keep track of work across Slack, Discord, Figma, and Github. Unlimited users, unlimited spaces. Free plan up to 250 work items. - Source: dev.to / over 1 year ago

At Kitemaker, we recently made the leap to Recoil.js for our React state management needs. Before using Recoil, Kitemaker used a simple state management solution built upon useReducer(). We built Kitemaker to be super fast, responding to every user interaction instantly. However, in organizations with lots of data, we sometimes had a difficult time achieving this due to unnecessary re-renders. Kitemaker has a sync... - Source: dev.to / over 1 year ago

Definitely feel your pain. We did a full OT implementation for our startup [0] and it was a beast. We based it on Slate.js which has a nice concept of operations that maps nicely to OT, but it was still a lot of work to get it working well (and there are still rough edges we try to improve all of the time). We did base it on Postgres in the backend so really looking forward to what the Supabase team comes up with... - Source: Hacker News / over 1 year ago

My current company is using Basecamp. I don't like it; it feels very disorganized, with work scattered across many message boards, chats, kanban boards, etc. Instead of Agile, it uses Shape Up (https://basecamp.com/shapeup), which has a "no backlog" philosophy (https://basecamp.com/shapeup/2.1-chapter-07#no-backlogs). In this system, I feel like most customer-originated work simply gets ignored and forgotten =/... - Source: Hacker News / 13 days ago

Linear — Issue tracker with a streamlined interface. Free for unlimited members, up to 10MB file upload size, 250 issues (excluding Archive). - Source: dev.to / 3 months ago

This is the approach I use in most of my hobby projects. It's simpler, and faster and there are no loading screens. In my kindle-clippings-manager (https://github.com/karlosos/kindle_clippings_webapp) uses its sync engine to store the data in Web Storage. With optimistic updates, it feels like an offline app. You can read more about the sync engine here: - Source: Hacker News / 4 months ago

Https://linear.app/ He's the CEO "of" Linear, not a linear CEO :). - Source: Hacker News / 4 months ago

I can recommend Linear[0] No affiliation. Simply, I really like how it works, and its a great interface as well. Really gets out of your way, has solid integrations and a good API for building your own [0]: https://linear.app/. - Source: Hacker News / 7 months ago