4 ms·

> (Emphasis mine.) My god. yes, C finally catching up with what languages such as F# have been able to do for years with great success https://docs.microsoft.c

> (Emphasis mine.) My god. yes, C finally catching up with what languages such as F# have been able to do for years with great success https://docs.microsoft.com/en-us/dotnet/fsharp/tutorials/type-providers/ https://docs.microsoft.com/en-us/dotnet/fsharp/tutorials/typ... ; wild isn't it to step into the 2010-era of programming ?

oefrha 4y ago
I suppose you’re of the opinion that every feature of every language should be added to C, or maybe even assembly.
- jcelerier 4y ago
  this isn't adding a new feature. This is replacing a feature that everyone already implemented independently on every other project - some with xxd, some with special embedders such as rcc or windres or whatever, some through CMake directly (like this: https://gist.github.com/sivachandran/3a0de157dccef822a230 https://gist.github.com/sivachandran/3a0de157dccef822a230 for instance) - in a standard and more performant way. Instead of being paid per-project this cost will now be paid per-compiler implementation which is unambiguously good as there are <<< compilers than C projects.
  - oefrha 4y ago
    You replied to my quote about pulling network resources and “other shenanigans”, which certainly isn’t what “everyone already implemented independently”. Plus that’s a potential vendor extension, i.e., some may implement it independently, some may not, implementations will likely differ.
    - jcelerier 4y ago
      > You replied to my quote about pulling network resources and “other shenanigans”, which certainly isn’t what “everyone already implemented independently”. ?? pulling network resources works, today, with what people are using. there's zero difference between "cat foo.txt | xxd -i" and "curl https://my.api/foo.json https://my.api/foo.json | xxd -i"
      - joshuamorton 4y ago
        Hell, I #include files mounted over FUSE regularly.
        remexre 4y ago
        https://github.com/camel-cdr/execfs https://github.com/camel-cdr/execfs ?

oefrha 4y ago

I suppose you’re of the opinion that every feature of every language should be added to C, or maybe even assembly.

jcelerier 4y ago
this isn't adding a new feature. This is replacing a feature that everyone already implemented independently on every other project - some with xxd, some with special embedders such as rcc or windres or whatever, some through CMake directly (like this: https://gist.github.com/sivachandran/3a0de157dccef822a230 https://gist.github.com/sivachandran/3a0de157dccef822a230 for instance) - in a standard and more performant way. Instead of being paid per-project this cost will now be paid per-compiler implementation which is unambiguously good as there are <<< compilers than C projects.
- oefrha 4y ago
  You replied to my quote about pulling network resources and “other shenanigans”, which certainly isn’t what “everyone already implemented independently”. Plus that’s a potential vendor extension, i.e., some may implement it independently, some may not, implementations will likely differ.
  - jcelerier 4y ago
    > You replied to my quote about pulling network resources and “other shenanigans”, which certainly isn’t what “everyone already implemented independently”. ?? pulling network resources works, today, with what people are using. there's zero difference between "cat foo.txt | xxd -i" and "curl https://my.api/foo.json https://my.api/foo.json | xxd -i"
    - joshuamorton 4y ago
      Hell, I #include files mounted over FUSE regularly.
      - remexre 4y ago
        https://github.com/camel-cdr/execfs https://github.com/camel-cdr/execfs ?