Forced price matching could be considered a abuse of their position. If a dev cannot sell on another store for less (even if that platform takes a smaller cut) then that makes reduces the need for others to use a different platform to get a cheaper deal. Devs cannot use pricing to save you some money while drawing you to a platform that gives them a larger margin. All of which means that there is less incentive for valve to reduce their cut of the sale to be more competitive. This is what some lawsuits against valve are arguing ATM I believe.

Random programming certificates are generally worthless. The course to get them might teach you a lot and be worth while, but the certificate at the end is worthless. If it is free then it does not matter too much either way, might be a good way to test yourself. But I would not rely on it to get you a job at all. For that you need other ways to prove you can do the job - typically with the ability to talk about stuff and having written some real world like application. Which a course might help you do to.

IMO the best thing is to just start using it. You will start to pick things up fairly quickly then. Puzzles don't often ingrain different ways todo things and often focus on weird or niche things that don't come up as often. They can be a nice supplement to not a substitute for just using it in real world usescases.

I do also find it helpful to read the shortcut keys on their site to get a feel for what is available. You won't remember everything but it can be useful to know what is possible. Then when you hit a problem you may remember reading about something that can help and go look it up again.

There is no perfect OS that just works for everyone. They are all software so they all have bugs. People how say an OS just works have never hit those bugs or have gotten used to fixing/working around or flat out ignoring them.

This is true of all OSs, including Windows, Linux and MacOS. They are all differently buggy messes.

Linux is the buggy mess that works best for me though.

I seem to be one of very few people that does not use shell aliases. I much prefer just using the reverse history search for previous commands instead. That way I don't have to remember what letter I picked for different things, just ctrl+r then partially type out the command and I can see what it will execute. Bonus that I don't need to set them up before hand and that I can edit them before executing them for those times when I need to do something slightly different.

should a third-party acquire control over chrome's development, mv3 gets shredded. restrictions and limitations on adblockers get scaled-back or reverted outright.

That is far too optimistic. If the courts force a sale then a for profit company will but it expecting a return on investment. Which very likely means more monetisation efforts like embedding ads or even more tracking built into it. It is a fantasy to think who ever gets it will scale anything you dislike about it back.

Worst then that, it is an excuse to continue or increase emissions and distract people from real solutions. We need to reduce emissions first. It might be valuable someday once the low hanging fruit has been dealt with.

Why wait? Start using Linux friendly software in your day to day workflows. Then start to dual boot Linux with your current system and start using it more and more. By the time windows 10 reaches EOL you will know if you still need a Windows install or not.

TBH, I find the whole premise a bit silly. The one use case the original video talks about there this might be a good idea is when you have something like a MonsterId(String), and argues for MonsterId(Arc) instead - which I think is an anti-pattern. Use MonsterId(usize) and it becomes far cheaper to clone than even an Arc. There is no need to lug around strings as ids - which are presumably going to be used to look up values in a hashmap or similar (which again, I would suspect it is faster to has a usize than a string of any type).

Most of the rest of the time cloning a string is not a huge issue or if it is &str is often good enough. I find it rare that you would ever need the clone performance and multiple ownership of a Arc.

There are also crates like smallstring, smallstr etc, that are stack allocated strings up to a certain limit before they start allocating. Which would be worth a look at and see how they preform compared to Arc or String. Since most things I bet they were using Strings for would fit inside these types just find without the extra allocation.

It is a neat trick to have in your toolbag - but not the first thing I would jump for when dealing with strings.

All you get is a watermark in the corner

Well, that is a consequence. Just not a very big one. You also cannot change the background in the settings, though that is also a very small consequence. Yeah, they are only small and you can likely live with them, but small and tolerable are not zero.

there will be a subscription “premium” version like in any app that removes ads and enables AI features.

This makes me glad I no longer use it. An OS should not have ads baked into its core and there should not be a subscription for it.

The bill is not asking for things to be redesigned to be more repairable. It is more focused on being able to get the spare parts, chips, tools and docs that make more repairs of the devices to be viable. Many places can already do component level repairs of boards. It might not be worth it if the SOC dies, but a board has many other components on it that are far more likely to fail and much easier to replace than the SOC. If a power regulator fails why should you have to buy whole new board? Or if a few resisters/caps get burned out/shorted they can be replaced without needing a whole new device.

No not everyone can do these repairs - but why should those that can be blocked from doing so? Why should companies be able to deny chip manufacturers from selling a 12c chip that can fix a several hundred dollar board? Why should chips be serialised so that you cannot swap them out with working chips from donor boards? Why cannot tools be made available to calibrate sensors after they have been replaced? Why should any company be able to stop you getting the parts and tools needed to fix the stuff you own? Or be able to go to someone else to fix it?

Not every device will be fixable - but why stop any device from being fixable just because a few cannot be?

They should also be required to support it for X (exact time is up for debate) years after they stop selling it so you have some minimum amount of time that you know the device will be supported for no matter when you buy it.