this post was submitted on 10 Sep 2023
51 points (89.2% liked)

Programming

17489 readers
66 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago
MODERATORS
snowe
Ategon
[email protected]
51
What programming languages aren't too criticized here? (lemmy.fbmac.net)
submitted 1 year ago by [email protected] to c/programming
63 comments fedilink hide all child comments
 

It feels like anything is mowed down on the internet. I've been a dev for a long time too, and I never feel sure when I chose a stack for a new toy project (in my day job I rarely get to chose, so that's a non issue there)

you are viewing a single comment's thread
view the rest of the comments
[–] kogasa 6 points 1 year ago* (last edited 1 year ago) (2 children)

The 2 that I struggle with on a daily basis:

  • missing discriminated unions. Third party libraries kind of sort of fill the gap, but it's a pain point.

  • a flawed async programming model. Namely, there are multiple models (for historical reasons / backwards compatibility), and the more current one (task-based) throws a wrench in your ability to effectively design interfaces, functions, delegates etc. that can be shared between synchronous and asynchronous code. Green threads would have fixed this, at the cost of some other potential issues, but it looks we're stuck with tasks for now. Also, there is the awkwardness of needing to constantly use .ConfigureAwait(false) after every await, unless you shouldn't (e.g. in the UI thread), and if you get it wrong you might cause a deadlock in your app but not in a console app... A bit confusing and easy to mess up.

[–] [email protected] 1 points 1 year ago

I really like ReactiveX for async programming, though having to go through a library is definitely a pain. It also does not make it less awkward to design your public API unless you're okay exposing Rx types. Fair points!

[–] [email protected] 1 points 1 year ago

F# will give you discriminated unions and do-notation (it calls it 'computational expressions') while retaining full access to the .net ecosystem.