pgactive has limitations with not supporting DDL, sequence management, column and row filtering, conflict and exception handling, incompatibility with native logical replication, etc. The license is also different (Apache 2.0 for pgactive vs PostgreSQL for Spock). Most importantly, it's not "supported anywhere" by AWS, just on RDS.
2. Influencer Paige Lorenze is a mod of nycinfluencer snark and she prolifically deletes all unflattering threads and specifically all photos of her from before her numerous plastic surgeries:
Also happens on YouTube. Mr Beast’s team deleted all comments on his videos (of which there were thousands) that mentioned or linked to those videos exposing alleged fraud by the Mr Beast group.
Err...I know I'm one of the olds and probably shouldn't be allowed to comment, but isn't the whole point of these sites to allow one to present and enforce a carefully curated public image, often completely divorced from reality?
I’m curious why you know about these cases off-hand.
I have the impression that there’s a certain type of user that likes to be a gadfly in communities to devoted to not particularly relevant or famous personalities.
My significant other follows influencers thus I heard about the Paige Lorenze controversy/lore.
I wouldn't say either of them is "not particularly relevant" as D4vd is super popular among GenZ on tiktok and has 30 million listeners and 4 million followers. Paige isn't as big but she is a well-known WAG dating some tennis bro and has a successful clothing brand that sells to the genZ crowd.
I have so many disagreements on goals for the language with Russ, but have been a fan since his early days of writing the regex package and the c-to-go conversion code. Glad to hear he will still contribute to the lang, and hoping for a bit different direction from the new leads.
If you already have your own functions or variables named max, min, or clear in-scope, they will shadow the new built-in functions and your code will continue to use your own version of the functions. No breakage to existing identifiers that match the new function names.
(This is the same behavior as the append built-in function today, for example. These things in Go are _not_ reserved keywords, they are simply global functions that can be overridden at other scopes.)
In what way? Overall as a language, identifier shadowing is a feature of the language in nested scopes. Are you saying built-in identifiers (that aren't language keywords) should be treated specially and work differently than user-declared identifiers?
It's terrible, IMO, because every package that has generic words is now a variable name I can't use. A simple example which i find unreasonable:
package main
import (
"fmt"
"path/filepath"
)
func main() {
filepath := filepath.Dir("./")
//filepath.Dir('./") -> This is now a string. Can't use filepath package anymore
fmt.Println(filepath)
}
Now I have to make up variable names because `filepath` will shadow the package. How it this sensible in any shape? Zip just does this better by having @ in front of builtins.
you're complaining that the nomenclature for packages is not differentiated in a way that allows user code to have variable names with the same name as package names
you can still allow this, of course, by aliasing the package import
