Yes, historical medicin was so good, lets work our ass off to recreate it...
Good to know that every time I feel the need to use ALGOL 68, I must remember to disable ligatures. Still not sure this is going to be a huge problem 😂
Well, that was something.... I have used ligatures in my code editor for quite a few years now, and I have NEVER been confused about the ambiguity this person is so upset about. Why? I have never ever seen the Unicode character for not equals in a code block, simply since it is not a valid character in any known language. In fact, I have never even seen it in a String where it actually would be legal, probably since nobody knows how to type that using a standard keyboard. This whole article felt like someone with a severe diagnose have locked in on some hypothetical correctness issue, that simply isn't a problem in the real world.
But, if you for some reason find ligatures confusing, then you shouldn't use them. But, just to be clear, there is not a right of wrong like this blog post tries to argue, it is a matter of personal taste.
It is making the tracking protection part of containers obsolete, this is basically that functionality but built in and default. The containers still let you have multiple cookie jars for the same site, so they are still useful if you have multiple accounts on a site.
But per mile measurement for flying implies that every mile of a flight is equally dangerous, but the truth I'd that it is most dangerous to start or land, which is a per trip occurrence. The take off and landing is equally dangerous whether you travel a long or short distance in between.
One breaking change, that they doesn't list as breaking (I guess since I assume the old was always broken) is: Dynamic registration of LSP capabilities. An implication of this change is that checking a client's server_capabilities is no longer a sufficient indicator to see if a server supports a feature. Instead use client.supports_method(). It considers both the dynamic capabilities and static server_capabilities.
So if you had code like
if client.server_capabilities.inlayHintProvider then
...
end
you now should use
if client.supports_method("inlayHintProvider") then
...
end
So, not really a breaking change I guess, but something you should change any way.
I say that you should find some interesting project, possibly something related to some desktop environment like Gnome, KDE, sway, cosmic and so on. There are multiple fun/interesting projects around them. Then pick a small and manageable task, use that to learn the language that project uses.
I find Cosmic to be a very interesting desktop project, and they use Rust if that would be of interest.
And the Copy question.It is not that s reference has to implement Copy. A reference IS Copy, by the simple fact that it is a primitive value on the stack.
I actually agree, I much prefer articles. However, I found this interesting since it looked at turbopack, parcel, rspack and others and talked about how it comes that the JavaScript ecosystem seems to start to use a lot of rust for their tooling. It was quite long though...
Just to be clear, I'm not the author I just found it a quite interesting article and thought I'd share it here.
I think you are getting things backwards.... Learning to write rust might be hard, if you are not used to typed languages or languages with explicit memory management with stack/heap separation. However, writing rust is not hard. It might take slightly longer in the coding phase, since you are forced to do things correct, you need to handle errors and are not allowed to share data between threads in dangerous ways aso. But that makes the resulting software a lot better, which means that the testing and support is a lot less. So, if anything, the net result of writing software in rust is that it is easier, since you are not allowed to shoot your self in the foot over and over again.
And remember, that every time rust is making your life difficult, you might have introduced a subtle bug in another language.
These are good in a more hands on way, but it is hard there to understand the conceptual difference between MIT and EUPL. So, I deliberately didn't go in to the details, since there are a lot of tools for that. I aimed for a higher level, since I find people often have missed that.