4 ms·

This is such a concise and informed comment. Why has it been voted down to being barely dim on my screen? These are good arguments. Please reply to stuff like t

This is such a concise and informed comment. Why has it been voted down to being barely dim on my screen? These are good arguments. Please reply to stuff like this instead of knee-jerk downvoting.

V-2 11y ago
Agreed. I would actually be curious to read some counterarguments. Alas, noone has offered any
- KirinDave 11y ago
  I think the community has a prevailing opionion that C# is part of a UWP lock-in and they're concerned about that. I'm sure at least some people think C++ is helpful as a hedge against this.
  - pjc50 11y ago
    Surely writing to the Windows Platform API is where the lock-in is, not the choice of language?
    - KirinDave 11y ago
      ¯\_(ツ)_/¯ But that argument revolves around the growing importance of the Microsoft software store. Its actually an argument between ISVs and Microsoft about how much control MS can have in software distribution and security.
- Aleman360 11y ago
  Runtime heap usage.
  - KirinDave 11y ago
    Isn't that a performance concern though? Especially within the context of a react native implementation that environment is already going to push you way above what is achievable with C++. If we're talking a 5% reduction in the net heap usage for a react native app at the cost of substantially more error prone code, is that really a win? Hell, make it 10%? These apps still readily fit in mobile hardware, and you wouldn't be using react native on a Pi or other more tightly resources embedded system.
    - deleted 11y ago
      [deleted]
    - Aleman360 11y ago
      Performance should be a pretty big concern for UI frameworks. Would be interesting to see some benchmarks.
KirinDave 11y ago
I sit upon my horde of HN karma burning it daily. I knew I'd be downvoted for replying to a language preference quote. Especially given how very charged the C++ community is as they feel increasingly abandoned by Microsoft. I am just happy one person liked it. :)

This is such a concise and informed comment. Why has it been voted down to being barely dim on my screen? These are good arguments. Please reply to stuff like this instead of knee-jerk downvoting.

V-2 11y ago

Agreed. I would actually be curious to read some counterarguments. Alas, noone has offered any

KirinDave 11y ago
I think the community has a prevailing opionion that C# is part of a UWP lock-in and they're concerned about that. I'm sure at least some people think C++ is helpful as a hedge against this.
- pjc50 11y ago
  Surely writing to the Windows Platform API is where the lock-in is, not the choice of language?
  - KirinDave 11y ago
    ¯\_(ツ)_/¯ But that argument revolves around the growing importance of the Microsoft software store. Its actually an argument between ISVs and Microsoft about how much control MS can have in software distribution and security.
Aleman360 11y ago
Runtime heap usage.
- KirinDave 11y ago
  Isn't that a performance concern though? Especially within the context of a react native implementation that environment is already going to push you way above what is achievable with C++. If we're talking a 5% reduction in the net heap usage for a react native app at the cost of substantially more error prone code, is that really a win? Hell, make it 10%? These apps still readily fit in mobile hardware, and you wouldn't be using react native on a Pi or other more tightly resources embedded system.
  - deleted 11y ago
    [deleted]
  - Aleman360 11y ago
    Performance should be a pretty big concern for UI frameworks. Would be interesting to see some benchmarks.

KirinDave 11y ago

I sit upon my horde of HN karma burning it daily. I knew I'd be downvoted for replying to a language preference quote. Especially given how very charged the C++ community is as they feel increasingly abandoned by Microsoft. I am just happy one person liked it. :)