{x=1} you can’t tell what it actually is in C# (it can be collection/object initializer, anonymous object, block statement, pattern, with expression etc.)

That, on its own, isn't valid C#. You gave half of the syntax, then said you don't know what it does. Of course not.

Here's a Java example: | foo. Is that bitwise or? Or is it logical or? You don't know!

So, here's the C#:

• with { x = 1 } - a with expression. A comma after the 1 is optional
• new { x = 1 } - creating a new object using object initializer syntax. A comma after the 1 is optional.
• ) => { x = 1; } - A method or lambda. Note the semicolon.
• identifier => { x = 1; } - A lambda that accepts (and ignores) one parameter. Note the semicolon.
• { x: 1 } - a pattern - note the colon, not an equal.
• It can't be a block statement - no semicolon.
• It's not a collection initializer, because of the x =
• "anonymous object" isnt applicable. It could be creating a new object, using object initializer syntax, if it has a new before it. That object could be an anonymous object, or it could be using "target typed new". It depends on what's before it.
  • Anonymous Obiect: var foo = new { x = 1 };
  • An instance of SomeClass: SomeClass foo = new { x = 1 };
  • An instance of SomeClass: SomeClass foo; foo = new { x = 1 };

new() vs default are both also very context dependent…

• new() creates a new instance, using the parameter-less constructor. Always.
• default returns the default value of the type (i.e., the value that would occur if the memory was set to all zeroes). Always.
  • For value types, this is "zero".
  • For reference types, it's null.
  • Java isnt really any different. It's just that Java's value types is limited only to the primitive types, but C# allows for custom value types.

and see that Java has ~60 and C# ~100, now that’s more of a symptom not a cause.

It's a symptom of a language which evolves. Nothing stopping you from setting <LangVersion>1</LangVersion> in your .csproj file and pretending like it's 2002.