8
galena
185d

Fucking hell! Why is it so hard to just create a simple websocket!
C#: Yeah, you should use ASP.Net with SignalR! But heres a totally undocumented mess of a lib to get it to work. J.k. Deadlock!
Rust: async while let OK((some)) = ws.create.unwrap_or_else().suckadick()
Why the fuck is Rust so fucking dense! I want one line that means one thing! If I would compress my code with gzip it would be less information dense than this!
Zig: Yeah, Its in Beta and shits semi stable. Atleast i got it to work? Nope!

I've ben fussing aound with these three Languages for more than a week now and can say: Just use an established way to webdev. Its not worth it to try and make it as simple as possible!

Comments
  • 0
    I tend to use Typescript when I don't want to make decisions about error handling and thread safety and just want something to work in the happy case with possible hidden assumptions in as few lines as possible. It has good enough types for accurate intellisense for non-library types and libraries for literally anything I'd ever want to do.
  • 0
    @tosensei Isnt that asp?
  • 0
    @retoor Initially i focused on compiled languages, but this might acutally be a viable sölution 🤔
  • 0
    @tosensei we don't speak of asp classic! Let me forget about it please.

    But app.UseWhatever() looks like ASP.NET Core
Add Comment