303 karma · joined August 31, 2007
(Well, good luck writing one in Xcode, for that matter.)
Coming from more of test-driven development background, I found that tinkering in the REPL was similar to what I would usually do with unit tests, but without the ability to easily build up a test suite that would prevent regressions in future.
I think part of the mystique of it is that the authors kind of faded into the background after publishing it. I've never been able to find a follow-up paper from them.
I get that it has no concept of who I am when I search, but some kind of localisation based on IP address could maybe help?
Also, it feels a little disingenuous to say Google is not a search company, it's an advertising company. DDG's revenue is also built on ads. Is it fair to say they are also not an advertising company, not a search company?
This is oversimplified to a painful degree.
I don't think Kotlin is performant enough for Flutter though.
It's almost impossible for most people working in soulful / desirable / economic powerhouse locations to get a mortgage on a property there, so you see lots of wealthy investors take up the properties there and rent-seek to make themselves even richer.
That's before we even mention the children factor.
This isn't exhaustive. What about the case where both patches A and B are worked on independently, and both depend on an original version of the codebase, let's call it P for parent.
A and B both diverge from P and therefore require a merge, or in git, a rebase. Over my years as a developer this scenario has caused approximately 90% of the issues with git. How does Pijul tackle it?