Kitemaker VS Translate

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 / 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

I live in Shanghai and for years I used the webpage translate.google.cn but one day Google decided to retire the Chinese service and now this redirects to the Hong Kong page. What's the problem with taht you may ask, well let me tell you. It doesn't take you to the translate page, it takes you to the HK Google search and when you click then it actually takes you to translate.google.hk that extra step is annoying. Source: 11 months ago

Today, at minimum 10 hours ago translate.google.cn became inaccessible, I found this based on an automated test accessing it failing. It redirects to a normal Google search. translate.google.hk still accessible. Source: over 1 year ago

Yeah, I think so. Despite their search engine being blocked in China, Google has 4 offices on the mainland. Google Translate is not blocked in China (the .cn one I mean). I wonder what else they do there. I hope they have not restarted work on Dragonfly). I just can't trust them. Source: almost 2 years ago

Try to see if you can go to translate.google.cn in a browser. Source: over 2 years ago

Not much to comment. Yes, they killed it – website got blocked (in case you didn't know, translate.google.cn was available the whole time, too). What the other guy said about reinstalling languages is probably about on-the-phone translation, which is a totally different. Source: over 2 years ago