snaggen

joined 2 years ago
[–] [email protected] 13 points 1 year ago (2 children)

On my first programming lesson, we were taught that 1 second sleep was for i = 1 to 1000 😀, computers was not that fast back then...

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (10 children)

If you avoid Nvidia, it have been ready for many years. And to be honset, not sure X11 was really stable with Nvidia either. My main issue with Wayland, is that X doesn't have multi dpi support... and for that I really cannot blame Wayland. Also, Skype doesn't have screensharing, well, they actually had for a while, but then removed it... still, hard to blame on Wayland.

But as a general rule, if you have Nvidia, then you are not allowed to complain about anything... that was your choice, and with Nvidia under Linux, all bets are off. I thought that was clear a long time a go, especially after Linus not so subtle outburst.

[–] [email protected] 22 points 1 year ago

Also, it was easier to support X11, since there is no security. You wanted to read other applications key events, no problem. Want to read the screen, without without anyone knowing? No, problem, just read it. With Wayland you must use APIs for stuff, and you are not allowed to do everything.

[–] [email protected] 8 points 1 year ago (14 children)

Are they really? Didn't you press a button that said "Buy"? Just because they want things to be something else, doesn't mean that the meaning of the words changed.

[–] [email protected] 2 points 1 year ago (1 children)

Well, I have avoided Nvidia for 20 years due to driver issues on Linux, so I would be surprised if you had fixed them all :) But, it sound really promising, looking forward to try it out!

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago) (4 children)

I'm really looking forward to the alpha release. I hope someone package it for Fedora also, so I can test it without to much hassle... if not, I guess it will be PopOS in a VM. @[email protected] what is the general state of it as of today? Are the developers at S76 able to use it as their daily driver (By that I mean, being able to use it since they can over look bugs and such, since they are the developers. Obviously a different bar than end users), or is that expected after the alpha?

[–] [email protected] 12 points 1 year ago (1 children)

The borrow checker handles more than just freeing allocated memory, it will also prevent data races and invalid concurrent access aso. I personally don't have any issues with using garbage collected languages, but the fearless concurrency is nothing I'm willing to give up.

[–] [email protected] 38 points 1 year ago (2 children)

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?

[–] [email protected] -2 points 1 year ago (7 children)

You have understood that there doesn't exist any country that meets you utopian communist view, yet you have not stopped to think about why that is.

[–] [email protected] -4 points 1 year ago (9 children)

Ahhh... the communist countries are where all the unicorn lives... got it!

 

Traits now support async fn and -> impl Trait (with some limitations), the compiler got faster, version = in Cargo​.toml is now optional, and many small functions have been stabilized!

view more: ‹ prev next ›