You shouldn't need tooling to fix an issue. Better for a design that does not require extra tooling.

One problem is GHs auto-merge when ready button. It will merge when there are still tests running unless they are required. It would be much better if the auto merges took into account all checks and not just required ones.

Just? This is a link to the last page of the benchmarks. The other pages have other workloads on them - quite a lot of DB benchmarks though.

But, what happened to all that extra money for the NHS due to Brexit?!?!? /s

I wouldn't sound so sure. There are a lot of blockers to getting a working ARM based steam deck. First Arch Linux (which steam os is based on) does not offer official ARM binaries. This would mean they would need a new base os or work on getting Arch Linux to support ARM. With their recent donations to Arch Linux were focused on unblocking some issues with supporting Arch on ARM (notibally stuff needed for better automated builds) would suggest they want to stick with Arch.

Next you need good emulation layers for x64 and x86 as that is what all games are written in. Which there are leaks that say they are working on this as well.

But that is two big blockers that could take years to solve. So all comes down to when they want to release the next deck. Within a couple of years and I don't think it will be arm based. After that the chances go up quite a bit.

IMO rust does use OOP styles all over the place. OOP does not mean dynamic dispatch or inheritance - that is just what older popular languages used. Note that static dispatch and monomorphization (where the compiler generates a method for each type at compile time rather than using a runtime lookup) give you a lot of the benefits of dynamic dispatch at the cost of binary size in favor of runtime checks and performance.

And other aspects of OOP, like encapsulation, data abstractions and polymorphism are easily achievable in rust and often are. Just look at any object from the std library - they are all essentially written in an OOP style. Such as Vec or File - hidden internal state with traits that you can swap them around with other parts that make sense. The only thing it really likes - like Go lang (which claims to be an OOP style language) is inheritance.

And the only reason rust is not seen as or describes itself as an OOP language is because it does not force the OOP style on you. But instead lets you program in more of a functional or procedural style if you want to. You can pick the best methodology to solve the problem you have at hand rather than trying to fir everything into a single style.

But that does not make it bad at OOP style.

One of the fabricated battery pouch cells was even able to work after being folded and cut off. “That proves its high safety for practical application,” the researchers emphasized.

If you can cut it in half and it still works I doubt piercing it will do much.

For me, I like the idea of a tiling window manager with batteries included. Been using tiling window mangers for ages now and cannot go back to floating window management. But all the tiling window managers are bare bones and configure everything you want from the ground up. Which I am not a huge fan of these days. I want something to work out the box with first party full tiling support (not just dragging windows to the side) but without needing 100s of lines of config to get a half decent setup.

There are basically two different versions of Cosmic. The current one which is basically just an extension for Gnome. This is what has shipped with PopOS and currently still done.

But system76 had a vision for what they wanted and they did not feel building that as an extension was sustainable long term. They had a bunch of stability issues (ie gnome breaking things in newer versions they were using). So they decided to write a new desktop environment from scratch in rust that they had full control over.

I believe that the new Cosmic sits somewhere in between KDE and Gnome in terms of customization - or at least what they are aiming for. No where near the level of settings as KDE but not trying to remove every option like Gnome.

And being a new project written from scratch it is forward focused - and only support wayland.

You can read more about their decisions in a recent blog post: https://blog.system76.com/post/cosmic-team-interview-byoux

I kinda disagree with him on this point. I wouldn’t necessarily limit to one thing, but I think functions should preferably be minimal.

I do actually agree with him on that point - functions should do one thing. Though I generally disagree on what one thing is. It is a useless vague term and he tends to lean on the smallest possible thing a thing can be. I tend to lean on larger ideas - a function should do one thing, even if that one thing needs 100s of lines to do. Where the line of what one thing is, is a very hard hard idea to define though.

IMO a better metric is that code that changes together should live together. No jumping around lots of functions or files when you need to change something. And split things out when the idea of what they do can be isolated and abstracted away without taking away from the meaning of what the original function was doing. Rather than trying to split everything up in to 1-3 line functions - that is terrible advice.

Yeah, I really hate having to install a different language interpreter when working another one. Basically makes me very unlikely to bother with the tool in the first place.

He added: “We completely understand the legitimate concerns around the use of mobile phones, including cyberbullying, the impact of extended screen time on mental health, and the lack of regulation of big technology companies. The fact is though that the widespread use of smartphones is a societal issue and problems that result from this are more likely to arise outside of the school gates.”

Banning phones in school does not help to fix any of this. At most it just pushes it to the rest of their lives. Maybe we should be looking at educating our children about these topics, not ignoring them for as long as possible...

I think this shows that adults are terribly addicted to their devices and think if they can’t stop using them, children won’t either. They certainly can’t teach how to use phones responsibly if they can’t do it themselves. Unfortunately for children the result is an outright ban.

Yeah, so we need to tackle the problem in some way, not just ignoring it with a ban. A ban teaches them nothing about how to use their devices responsibly. Additionally - the probably should be some legislation on what tech companies are doing here as well. Things like facebook pushing any content it can for more views even if they have shown to have negative impacts on peoples mental health is something that really should be regulated. Profits at the expense of peoples mental health should not be allowed.