101–110 of 203 posts
x^2 means x squared, orphaning the XOR operator. Rune is for crypto, so math comes first. Isn't XOR used very heavily in crypto? (As is exponentiation of course)
https://github.com/google/rune/blob/main/bootstrap/database/...
That innovation does seem like a potential footgun.
Earlier quoted context omitted.
How do you operator overload in C++ so that calling computeHmac(secret(string)) returns secret(string)?
Define the computeHmac method to return a secret(string) type? Then define the equals operator for "secret" to behave in the needed way.
The advantages of monads include exactly the opposite decoupling: the hmac algorithm implementation is true to its bare specification, and it is the context that changes some of its behavior.
Earlier quoted context omitted.
Given that they mention SQL more than other things, and stress SoA and memory intensive applications, I think this makes more sense than it would otherwise
SQL null is not like the null of programming languages, it behaves more like "unknown" than "blank". For instance, null != null. Arithmetic on null values is also well-defined so that 1 + null = null. I'm not convinced that implicit nullability is a good idea, either in SQL or in newly designed languages. I don't see the connection between implicit nullability and SoA. If you have a link to some example, that would b…
As for SoA, I'm thinking of two relatively new formats and applications that have default nullable types, are SoA, and are specifically targeting memory intensive applications: apache arrow and duckdb, both seeing some success and well deserved hype
There already exists Rune programming language and that one was earlier: https://rune-rs.github.io/ They should be more careful picking the name.
Let's be real for a minute. A couple of hobbyists have named their pet project "rune". Should the name be then forsaken for all eternity?
But in the spirit of being real: what are you trying to do by calling the Rune devs "a couple of hobbyists"? Is that an attempt to minimize them, as if they are not a corporation therefore they don't have any naming rights to their projects? "A couple hobbyists" are how many great language you know and love started out. Their rights are important too. We don't want the norm to be big corporations snuffing out hobbyist projects by making them unsearchable, like Google did to Go!. That's bad for everyone.
Earlier quoted context omitted.
It seems like somebody got too easy access to the Google Github repo. Usually only higher quality projects get approved to the central repo.
If I remember correctly we were supposed to have our personal projects there. Since Google owns the copyright it almost makes sense. Also, being in the Google organization doesn't mean that Google is involved in it. I'm maintaining a project there (`google/double-conversion`), despite not having worked for Google for years. Nobody at Google has any influence or reviews on that project.
That's nice to see they went with C
I like the syntax
x^2 means x squared, orphaning the XOR operator. Rune is for crypto, so math comes first. Isn't XOR used very heavily in crypto? (As is exponentiation of course)
But hey, if Google says math comes first...
There already exists Rune programming language and that one was earlier: https://rune-rs.github.io/ They should be more careful picking the name.
Let's be real for a minute. A couple of hobbyists have named their pet project "rune". Should the name be then forsaken for all eternity?
Earlier quoted context omitted.
This is a timing attack or timing oracle. Lets assume a mac represented in an array of 32 bytes. If we had a pseudocode method like: byte [32] (actualMac, expectedMac) for int x = 0..31 if (actualMac[x] != expectedMac[x]) return false; fi end return true; We return false as soon as we hit an invalid byte in our calculated mac. If the time taken to execute one iteration of the loop is Y and the attacker is able to tim…
> in constant time why is it called constant time if it isn't constant with respect to array length? Just seems confusing because the algorithm is linear without a short circuit
What's even more confusing is that it is also constant time in the complexity analysis sense given that the mac is usually a fixed-size string after choosing a hashing algorithm.
Earlier quoted context omitted.
There already was a GO programming language before Google decided to use the name, too.
As some other comments have pointed out, this seems to be a one-person project. FWIW, Go also started as a project by 3 people who happened to be working for Google (Robert Griesemer, Rob Pike and Ken Thompson), so it wasn't Google consciously choosing the name. Perhaps Google as an employer shouldn't allow employees to choose any name they like, and do some diligence to avoid name clashes. This may sound quite reaso…