Even translations are community driven :)
Disclosure: I'm just a reader of P&C, who found the comic not so long ago and fell in love with it!
383 karma · joined January 16, 2016
Even translations are community driven :)
Disclosure: I'm just a reader of P&C, who found the comic not so long ago and fell in love with it!
Gitkube thread on HN: https://news.ycombinator.com/item?id=16574893
(I'm talking about the old desktop client, not the new electron based one)
To me it seems like, in that case, he chose postgres since he could sync the data and use a custom schema over it, with proper types and indexes.
Don't get me wrong, I do agree fossil is adding some new cards to the table. I just think it would be better implemented as extensions to git than a new system made from scratch.
Where I could learn the most was in code examples. They provided me new concepts I could poke, modify the values, and see the output, and hopefully after some time I would be able to understand how to use it.
There's a trend that everyone should understand how to code, and python is used as the língua franca for beginners, so providing a lot of examples helps people that do not intend to work as a developer understand new concepts. First you read about it, then you play with it for a while, and finally you'll get how to use it (and when to) in the future.
If anything, graphql apis would be easier to maintain in the long run, since clients asks for what they want. New clients could ask for the new data, without breaking the responses for old clients.
Why is it better to give all the power to the ISP? You're losing your ability to choose if what you need isn't included in a pack.
(this is a serious question, but I'm unable to phrase it this late in a way that doesn't sound like I'm trying to provoke you)
And the prices (AFAIK) are also totally handled with smart contracts, so even if it's just you, you can still claim the price.
What else would you use to notify interested people and be able to receive feedback at the same time?
What features/integrations make sense for a proxy with systemd? I'd assume it's only a unit that comes with the package, but that "-Ws" makes me wonder if there're deeper integrations.
Things become a mess in no time, tooling changes constantly, and maintaining legacy code while developing new parts with current best practices helps you build a Frankenstein in no time.
(and don't even mention about coffee, or it'll make me start ranting about the move from coffee to es6 and now TS!)