Localize Reviews

Pijul Reviews

Localize mentions (3)

• How to handle big translation projects with a Gatsby site ?

  There are definitely i18n solutions to problems like this, but have you looked at an agent based solution such as https://localizejs.com? We used it for a project at work and it’s actually a surprisingly robust way to deal with translation by separating language management from development effort. Source: almost 3 years ago

• On Depression and Founders

  I run a company called Localize (https://localizejs.com). I’d love to speak to anyone with a background like yours for a PM or technical role with us. There’s no experience better than starting and failing at startups/side projects to prepare yourself for a Product Management role. brandon@localizejs.com. - Source: Hacker News / almost 3 years ago

• Ask HN: Who is hiring? (April 2021)

  Localize | https://localizejs.com | REMOTE (US / Canada) | Full-time | Backend & Full Stack Engineers We're hiring Full-Stack Engineers to join our remote-first team. As a core member of our engineering team, you’ll be responsible for implementing new functionality within Localize’s core product, maintaining existing code and functionality, and improving existing systems for maintainability, scalability, and... - Source: Hacker News / about 3 years ago

Pijul mentions (42)

• Version Control Beyond Git

  The feature I think I would most like to see is support for patches as a more first-class object. For example reverts and cherry picks have no real metadata. This leads to conflicts when merging branches that have cherry picks (although they often auto-resolve if they are exactly the same diff) and makes asking "Does $branch contain $patch" basically impossible to answer. https://pijul.org/ greatly improves this... - Source: Hacker News / 6 days ago

• Pijul is a free and open source (GPL2) distributed version control system

  In Pijul, conflicts are not modelled as a "failure to merge", but rather as the standard case. Specifically, conflicts happen between two changes, and are solved by one change. The resolution change solves the conflict between the same two changes, no matter if other changes have been made concurrently. Once solved, conflicts never come back. - from https://pijul.org/. - Source: Hacker News / 3 months ago

• Josh: Just One Single History

  Do not try and bend the spoon, that's impossible. Instead, only try to realize the truth...there is no spoon. Then you will see it is not the spoon that bends, it is only yourself -- what Pijul users say when they overhear git users arguing with each other about monorepos. https://pijul.org/. - Source: Hacker News / 3 months ago

• Introduction to Loro's Rich Text CRDT

  I believe that handling merges like this correctly was a motive for designing pijul: https://pijul.org See the item on the splash page about 'merge correctness'. Unfortunately I wasn't able to find the post detailing the behavior with a bit of searching. - Source: Hacker News / 4 months ago

• Introduction to Loro's Rich Text CRDT

  Darcs [0] patch theory was a predecessor to OTs/CRDTs (and a predecessor to git as well; in some ways it is the "smart" to which git was named "dumb"). When it works and performs well it is still sometimes version control magic. Pijul [1] is an interesting experiment to watch, trying to keep the patch theory flag flying and also trying to bring in updates from OTs and CRDTs as it can. [0] https://darcs.net [1]... - Source: Hacker News / 4 months ago