On the other hand, that one same engine would then be under near-full control of a single company (Google), with all the disadvantages a monopoly usually brings.
I'm not the founder nor Kagi employee, just a customer, but
> Can you describe or offer any insight into the "significant IP" that you need to protect and defend?
The novel IP is having implemented and still implementing the browser APIs necessary for both Firefox and Chromium extensions to work in a Safari (Webkit)-based browser. See [1] for the significant progress.
> What threats from a larger company are you primarily concerned about?
Integrating said functionality themselves to offer another viable iOS browser, which Kagi is currently the only [2] offerer of (or another viable macOS/future Linux/Windows browser, although more than one exist there already).
[2] Unless the EU steps up, all iOS browsers will continue to have to be Webkit-based with minimal, lackluster extension support. Not viable for anything beyond the most basic of use cases.
Regarding your first paragraph, I've even talked with people who go out of their way to actively _avoid_ said product after encountering AI-generated advertising.
So that'll probably continue to have an effect for as long as average people with good eyes can still distinguish "AI"/generative media from "real"/traditional footage.
I have observed this as well, and we've already seen some pushback when major brands use AI in their creative. I wonder if we're entering an era where AI will actually taint a brand.
As has been stated above, I’m guessing in this specific example it would’ve been due to the rather strict labor laws, which I’m not going to comment my opinion on, just to clarify/explain: Here (Germany), you can basically not fire someone if your company has >10 full-time employees, and they’re not actively misbehaving (or under trainee/probationary status). Yep, this statement means exactly what it reads.
So I’m guessing that’s the reason for this “passive firing” method.
In addition to that, chezmoi templating can be used to fill in environment variables like secret keys, you just need to unlock rbw or whatever other password manager it is that you use.
I have some that I export in my shell config, and this setup allows me to have the repo in a public place and not worry about who finds it.
That’s right, it will still be pixelfied text. We could run ocr on the images then convert to text, but that’s an entirely new can of worms. Make a feature request issue on GitHub if you’re interested,
It's existed for months by now, and has been usable for nearly as long. I'd say you can decide if you need extra fluff like native apps or further "polishing" at this point.
As someone familiar with Helix, I’m curious. Could you elaborate on this?
Because I’m not disagreeing with your point, I’m actually not getting it in the first place. How does jumping around affect your selection count? Which motion(s) are you performing that larger quantities of text are getting "selected" in the first place?
I can’t speak for helix because I haven’t tried it, but I did spend a few weeks trying to get used to Kakoune before giving up and going back to vim.
The issue is that moving around would leave behind a trail of breadcrumbs. Sometimes these were visible cursors but other times they were invisible. Either way, I found myself being frequently surprised by the editor when it made changes I was not expecting.
Perhaps it’s something I could get used to with more time but it left me constantly perplexed and annoyed. I think ultimately what gets me is that in vim I can type a motion key and vim executes the motion and then returns to to a “null state” whereas with motion-action editors any time I key in a motion to jump somewhere I am now in the middle of the “motion-action” sequence and the editor is awaiting an action key to which it will eagerly respond. This to me feels very wrong, similar to the feeling I get when Siri is continuing to listen for more commands after invoking the command I asked for. Having to dismiss Siri all the time annoys the hell out of me.
Kakoune has a similar “dismiss key” which I remember pressing all the time out of habit, even when it was unnecessary, because the editor left me with this constant feeling of “unstable footing.”
While I'm aware this is a case of "you're holding it wrong" – !translate <phrase> should do the trick.
And that's not an excuse for not having better detection for when an info box should exist, because they do have them, especially for, but not limited to the WolframAlpha integration stuff. (For example, a friend and fellow user was awed when searching "internet speed test" and saw it integrated, no idea if Google has that too though).
Other than that, make sure your region/locale is set correctly (I'm not getting the metric petaton, for example), and for everything else, they have an excellent feedback forum for suggestions/bug reports.
Last time I checked (which admitedly has been a few months, but I haven't seen anything in the changelog/announcements that make me belive things got better), that's not a viable option.
I always keep it as "International" (luckily that's an option!), as setting it to "German" significantly degrades the results as for e.g. technical topics it will rank many rubish German results higher than they should be. Google still has a significant edge in getting the distinction right between regional and technical expertise and how they relate to language.
reply