Hacker News Reader

This is a nice improvement but I still think C# does this better:

Console.WriteLine(“Hello, World!”);

https://learn.microsoft.com/en-us/dotnet/csharp/whats-new/tu...

I like that this illustrates the C#/Java enterprise programming-ism that all identifiers must be in completely random namespaces to make it look fancier.

Is it helping anyone that the print function is under Console? Why is an array a standard type but also a class named ArrayList under System.Collections?

(Which seems to be deprecated and replaced with a class called List that's now under three namespaces instead of two.)

but what is the better alternative (if any) though? In practice this can help to enable having the same Square class name, just one in MyPackage and another in SomeOtherVendorPackage.

One level namespaces is all you need. Anything else just encourages bikeshedding and Conway's Law issues.

How does putting a print function inside a namespace lead to issues with Conway's Law?

Putting things in different namespaces will cause them to be maintained by different teams regardless of how similar they actually are.

I don't find it better. You now have an intuitive scope about what you can, or cannot do in the Top Level Statements.

Reply on news.ycombinator.com