ByteCode.News
RSS
SubmitLog in

Community

Chat Logs

Tuesday, June 23, 2026

  1. bluedreamreal: you're not gonna like this
  2. dreamrealwhat am I not going to like
  3. bluedreamreal: I've been getting into golang
  4. dreamrealwhy would I care about that?
  5. dreamrealHell, I had a conversation yesterday when FOXPRO came up
  6. dreamrealgo has a lot going for it. I think Rust is better, still, but eh
  7. dreamrealin the end it's all machine language
  8. bluedreamreal: I KNOW you hate go!
  9. bluemaybe not as much as you hate python, probably
  10. dreamrealI don't hate go. I dislike python, actively despise tcl but for reasons, don't like ruby much, but most others I'm pretty neutral about. Typescript I dislike as well, more than JS, which I find amusing, but I have reasons there too!
  11. blueI'd say on your negative list, there's scala, python, then go
  12. blueI think the language I historically despise the most is php, even though it had one of my fav frameworks, paradoxically
  13. dreamrealThen you should ask me instead! The truth is: I LIKE scala-the-language. I hate scala-the-ecosystem. I dislike python because significant whitespace offends me and it damn well should. I dislike typescript because it LIES about its type system. If you STAY in TS it's fine, and useful, but it's trivial to decay to JS, and boom, breakage.
  14. dreamrealI don't know PHP so I can't judge it.
  15. bluephp is just a poor excuse for a language, really, no structure at all, it's just cobbled together nonsense
  16. dreamrealGo is okay; I find it relatively paltry and the "batteries included" mindset is useful but amusing.
  17. dreamrealRuby is very meh, it's like someone said "let's look at python and fix the whitespace problem" without fixing some of the other problems they shoudl ALSO have addressed.
  18. dreamrealI despise tcl because of Vignette Storyserver. tcl *by itself* is probably fine but I found storyserver scarring.
  19. blueyou're wrong about that, though. TS doesn't lie about anything, it's just used by a host of morons, above all me, and they ENJOY those lies, in fact they embrace them
  20. dreamrealWell, to ME a typed thing is very easy to subvert in TS
  21. dreamrealbecause JS doesn't have it
  22. dreamrealI know they've fixed the Object.prototype.hasOwnProperty() thing to be something different now but that STILL makes me angry
  23. blueonce you stop looking at TS as a language and more like an LSP impl, it all makes sense
  24. dreamrealI never thought it DIDN'T make sense. I just don't care for it.
  25. dreamreal(in storyserver, IF, if, and If all had different semantic meanings.)
  26. dreamrealso if you like go, rock on wif yo bad self!
  27. bluethere are things I actively despise about it. like the fact `const foo = ["a", "b"];` will expand to string[]
  28. bluewhilst if you really want it to be `readonly ["a, "b"]`, you need to add `as const`
  29. bluethis has implications that break a core rule of programming, which is, trivial abstractions shouldn't modify semantics
  30. dreamrealsure
  31. blueie: `some_library.config({ "foo": bar })` // works
  32. blueer, should have been foo: "bar"
  33. dreamrealwhich ties into why I don't like tcl and storyserver: if you can see the differences between those three if expressions, I'd love to know how and why
  34. bluemeanwhilst, `const conf = { foo: "bar" }; some_library.config(conf);` // will fail, since conf is { foo: string }
  35. blueiow, those anonymous objects imply `as const`
  36. blueobv the key to solve this is type `const conf = { foo: "bar" }` with no expansion
  37. blueand if you really want a { foo: string}, you could still type it out, ie `const conf: { foo: string } = { foo: "bar"};`
  38. bluemagic is deadly!
  39. dreamrealyep
  40. bluedreamreal: curious case. I've got a email from contabo (my vps hoster) that they're raising the prices because of electricity costs and war and blablabla. and then, they offer for me, for the *raised* price, to switch to the next tier plan which is double the pcus, double the ram, and double the storage
  41. blueI must be the missing something
  42. blues/the //
  43. blueI mean, I'm not gonna say no to 24gb RAM instead of 12gb. I wanted more ram anyway, for repopack
  44. bluebut I feel like the electricity costs is just an excuse, lol
  45. bluethe raise priced isn't earth-shattering, either. from 7.91 to 9.52 euro
  46. blueso I *really* don't mind getting double the buck for roughly 1.2 of the bang
  47. blueit's just curious
  48. blueand my stupid ape brain doesn't like curious
  49. bluemoreover, the same plan, if I were a new customer, costs roughly 14, paid annually, and probably more monthly
  50. bluephaleth: hi, ssh2 is implemented
  51. bluefyi https://github.com/mscdex/ssh2/issues/1478#issuecomment-4770501899
  52. nevetPost-quantum safe kex algorythm? 路 Issue #1478 路 mscdex/ssh2
  53. phalethhi blue
  54. phalethyeah, already noticed
  55. blueso the ssh2 solution is generally better -- less code, less deployment complexity. however, that PQC notice is annoying, and I know it's gonna annoy users and lead to complaints
  56. bluefor now it's acceptable, but we might need to pivot to openssh if this becomes too much of an issue and the guy doesn't add the mixed algo
  57. phalethI guess the build or even other output messages will have to be modified anyway
  58. blueya