News for hackers. Stuff that matters.

A comment on .NET Core 3.0 Concludes the .NET Framework API Porting Project. Parent comment

Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by jeswin on Tuesday October 15, 2019 @05:38AM (#21256898)
> But that would mean optimising for "hello world" and other small script scenarios, which isn't a goal of the language design.

Fairly complex programs can be written with just plain functions, all of them elegantly starting off column 0 instead of being tabbed for namespaces and classes. It works especially well with directory structure based namespaces. eg: Microsoft's own TypeScript.

> Like "dynamic" in C# 4 ?

No not dynamic, I wouldn't use that very much either. https://en.wikipedia.org/wiki/Structural_type_system

[ Parent | on HN ]
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by nbevans on Tuesday October 15, 2019 @09:34AM (#21258162)
It sounds like you are using the wrong language. F# is what you want to be using.
[ Parent | on HN ]
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by SideburnsOfDoom on Tuesday October 15, 2019 @10:24AM (#21258687)
> No not dynamic

Ok, I see that structural typing is a third type system option.

But honestly, I don't want C# and .NET to contain every feature and paradigm ever created. It would be bloated and hard to use. Already there is significant legacy and different ways of doing the same thing, and it's likely to get even worse.

If the language that you ideally want is built around structurally typed free-floating functions, then it probably isn't C#. It probably exists, it's likely possible on the .NET platform, but it doesn't work and think like C#.

[ Parent | on HN ]