Comments by "Winnetou17" (@Winnetou17) on "ThePrimeTime" channel.

  1. 105
  2. 51
  3. 27
  4. 26
  5. 20
  6. 20
  7. 16
  8. 11
  9. 10
  10. 10
  11. 8
  12. 7
  13. 6
  14. 5
  15. 5
  16. 5
  17. 4
  18. 4
  19. 3
  20. 3
  21. 3
  22. 3
  23. 3
  24. 2
  25. 2
  26. 2
  27. 2
  28. 2
  29. 2
  30. 2
  31. 2
  32. 2
  33. 1
  34. 1
  35. OhMyGaaawd, I can't believe you missed the point on that C vs Go comparison at the end. It is a VERY GOOD comparison. Why ? The very thing you mentioned, that you wouldn't use C and Go in the same places. Initially there was only C (ok, a few others too, doesn't matter). But because it is only good at performance and low level control, it sucks at everything else (well, arguably) Go was invented as an alternative. Now Go occupies its own niche because C couldn't properly cover that part. Compared to C, Go has decent everything, it's just not perfect or the best in any of them. And since in some contexts speed of running is not the most important thing, but ease of developing is, they would prefer Go's "decent" vs C's "horrible" part. In regards to his SQL complaints... I'm still not sure what he wants/needs. Apparently statically analyzing that a query works is one of them. Ok, that can be done with SQL. Maybe he wants something like having directly an ORM-like library for a language, bypassing SQL ? Like, you only call functions and everything is run directly or sent from one server to another directly as binary data ? I guess that would be something. I remember that at the beginning there was a screenshot in which I think he wanted to highlight that the parsing of the query took semnificative time. Which, if you use something more direct, could be bypassed. Can't say I dislike the idea of having the option to send directly the structures and data exactly as the DB works with/uses them, so no more parsing is required.
    1
  36. 1
  37. 1
  38. 1
  39. 1
  40. 1
  41. 1
  42. 1
  43. 1
  44. 1
  45. 1
  46. 1
  47. 1
  48. 1
  49. 1
  50. 1