Well == is a question or a query rather than a declaration of the state of things because it isn’t necessarily true.
You can write
a = (3 == 4)
which is perfectly valid code; it will just set a to be false, because the answer to the question “does 3 equal 4?” is no.
I think you’ve got it anyway.
Ok after reading the article this is bullshit. It’s only because they are counting JavaScript and Typescript separately.
Typescript is far nicer than Python though. Well I will give Python one point: arbitrary precision integers was absolutely the right decision. Dealing with u64s in Typescript is a right pain.
But apart from that it’s difficult to see a single point on which Python is clearly better than Typescript:
uv is a shining beacon of light here but I have little hope that the upstream Python devs will recognise that they need to immediately ditch pip in favour of officially endorsing uv. No. They’ll keep it on the sidelines until the uv devs run out of hope and money and give up.They seem exactly the same to me: when a variable is assigned a value, it’s equal to that value now.
Yeah it’s confusing because in maths they are the same and use the same symbol but they are 100% not the same in programming, yet they confusingly used the same symbol. In fact they even used the mathematical equality symbol (=) for the thing that is least like equality (i.e. assignment).
To be fair not all languages made that mistake. There are a fair few where assignment is like
x := 20
Or
x <- 20
which is probably the most logical option because it really conveys the “store 20 in x” meaning.
Anyway on to your actual question… They definitely aren’t the same in programming. Probably the simplest way to think of it is that assignment is a command: make these things equal! and equality is a question: are these things equal?
So for example equality will never mutate it’s arguments. x == y will never change x or y because you’re just asking “are they equal?”. The value of that equality expression is a bool (true or false) so you can do something like:
a = (x == y)
x == y asks if they are equal and becomes a bool with the answer, and then the = stores that answer inside a.
In contrast = always mutates something. You can do this:
a = 3
a = 4
print(a)
And it will print 4. If you do this:
a = 3
a == 4
print(a)
It will (if the language doesn’t complain at you for this mistake) print 3 because the == doesn’t actually change a.
Interesting how they build a community starting with rebasing on top of Gitea, and then hard-forked later. Probably a good blueprint for forking.
GPL move also seems like a good idea - it reduces the chance of needing yet another fork.
Can they get whoever came up with the excellent name “Codeberg” to fix the terrible name “Forgejo” though? It’s not quite as bad a name as GIMP or Got, but still…
Also i absolutely hate how they talk about moderation. You can’t just say “someone was banned for some actions”. That doesn’t inspire confidence at all! Imagine if the police were always saying “one of your peers was sent to prison for a crime” and refused to say who or what they did. That’s communist Russia territory…
They claim they can’t say because of the right to be forgotten but that’s not what the right to be forgotten means.
… in one benchmark.
It does still have a traditional assignment operator. You can assign values to mutable variables.
Also I would say let-binds are still pretty much assignment; they just support destructuring. Plenty of languages support that to some extent (JavaScript for example) and you wouldn’t say they don’t have assignment.
I don’t think it affects the ability to overload = anyway. I think there aren’t any situations in Rust where it would be ambiguous which one you meant. Certainly none of the examples you gave compile with both = and ==. Maybe there’s some obscure case we haven’t thought of.
= and <= match the mathematical operators. The question you want to ask is why doesn’t it use = for equality, and the answer is that = is already used for assignment (inherited from C among other languages).
In theory a language could use = for assignment and equality but it might be a bit confusing and error prone. Maybe not though. Someone try it and report back.
https://github.com/microsoft/vscode/issues/205125
Also I found this duplicate: https://github.com/microsoft/vscode/issues/211508
There’s probably more…
They’ve been doing that for about the last 6 releases. I wish they’d fix some of the long-standing annoying bugs like the fact that you can’t respect .gitignore and search in a subdirectory at the same time. Or the fact that you can’t stage a submodule unless you also have that submodule open.
Or how about a less annoying way to configure Run/Debug than launch.json?
Still, can’t complain. It’s mostly free and still very good overall. I’ll definitely be watching Zed… but maybe not too closely until it supports opening large files.
where before we ran into compatibility problems with glibc
I wonder if GNU will ever fix that. Surely at some point they have to say “ok we still think things should be open source but we are going to make it suck a little bit less for people that don’t build literally everything from source on their local machine”… right? Ok maybe not.
Yes, but I was talking about Linux in general. I’m pretty sure Gnome at least has commercial backing.
And Linux advocate never say “don’t use Linux; it isn’t a commercial product so it isn’t as good as Windows” do they? They say “you’re an idiot for using Windows; Linux is better”.
GPU reset recovery
Woah catching up to Windows 18 years ago! :D
Tbf I did not think we would ever see this feature. What next, secure login prompts (“press ctrl-alt-del to login in”, which admittedly Windows seems to have dropped)?
Yes but they frequently ask for optional donations too. Are you a parasite for not donating?
I think he meant the idea of shaming companies for not donating to things.
I don’t think you can blame them for this. How many resources do you use without voluntarily paying extra above your legal requirements? Do you donate every time you go to free libraries, museums, parks, cathedrals, etc? I certainly don’t and I don’t think that makes me “the parasite class”.
No that’s a subtly different thing. The storage is a contiguous vector, but because it is a ring buffer there must be one pair of adjacent elements that are not contiguous in memory. That’s what that comment is saying.
But because it is only one discontinuity it doesn’t affect algorithmic complexity, so it is still O(1) to access elements, unlike a linked list which is O(N).
If you google “circular buffer” there will be loads of diagrams that make it really obvious how it works.
Standard ring buffers or circular buffers are implemented as continuous vectors, with a read and write pointer.
Rust’s VecDeque is a ring buffer: https://doc.rust-lang.org/std/collections/struct.VecDeque.html
Zero surprises. It’s the same as in any other language.
Yes:
Operator '+' cannot be applied to types 'number[]' and 'number[]'.We’re talking about Typescript here. Also I did say that it has some big warts, but you can mostly avoid them with ESLint (and Typescript of course).
Let’s not pretend Python doesn’t have similar warts:
>>> x = -5 >>> y = -5 >>> x is y True >>> x = -6 >>> y = -6 >>> x is y False >>> x = -6; y = -6; x is y True>>> isinstance(False, int) True>>> [f() for f in [lambda: i for i in range(10)]] [9, 9, 9, 9, 9, 9, 9, 9, 9, 9]There’s a whole very long list here. Don’t get be wrong, Python does a decent job of not being crazy. But so does Typescript+ESLint.
“It’s so bad I have resorted to using Docker whenever I use Python.”