• 1 Post
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle


  • The problem is that C is a prehistoric language and don’t have any of the complex types for example. So, in a modern language you create a String. That string will have a length, and some well defined properties (like encoding and such). With C you have a char * , which is just a pointer to the memory that contains bytes, and hopefully is null terminated. The null termination is defined, but not enforced. Any encoding is whatever the developer had in mind. So the compiler just don’t have the information to make any decisions. In rust you know exactly how long something lives, if something try to use it after that, the compiler can tell you. With C, all lifetimes lives in the developers head, and the compiler have no way of knowing. So, all these typing and properties of modern languages, are basically the implementation of your suggestion.









  • They explain a bit more about what that means here: https://kagifeedback.org/d/2808-reconsider-your-partnership-with-brave/75

    TL;DR They use multiple sources for search results besides their own indexer, the most obvious one is Google. To lessen dependence on one single search provider they have been adding other sources, one of them is now Brave. That is the whole thing.

    On Dec 26, Kagi started including search results from Brave search index, after we previously added Mojeek and Yandex earlier in the year. Brave has a public search api and we currently implemented it for about 10% of queries as a first test (same as any other API we use, there is no mutual development or anything of the sorts). This was announced in our Dec 28 public changelog. Approximately a week later on Jan 5 after several posts on social media about ‘Brave partnership’ the situation escalated.]

    So, if you do not like to use Google in the first place, I don’t really understand why lessening the dependence on google would be a bad thing?