Submit

Back to the channels

#primate

  1. phaleth "Wait forever for LLVM to compile the code" is sad but true https://lucaberton.com/blog/inko-programming-language-rust-erlang-2026/
  2. nevet [Node.js Blog] Node.js 27.0.0-alpha.0.1.1 (Alpha) - https://nodejs.org/en/blog/release/v27.0.0-alpha.0.1.1
  3. phaleth the idea of "Inter-procedural (whole program) escape analysis" sounds great
  4. phaleth another good idea "The architecture separates CPU-bound work from I/O-bound work into different thread pools"
  5. phaleth actually that continues with "without requiring async/await syntax" which sounds great
  6. phaleth "The compiler catches the dangerous patterns (use-after-free, null pointers, data races) without requiring you to annotate lifetimes or fight the borrow checker" also great
  7. blue Hi phaleth
  8. phaleth hi blue
  9. blue clanker is sleeping
  10. blue what's up?
  11. phaleth looking into inko
  12. phaleth no idea what's up with clanker, but inko seems like ideal lang for clankers
  13. lioloc hey guys, can you use flog for monorepos?
  14. lioloc blue: ^
  15. lioloc nvm i see that it does (workspaces), would be nice if `flog init` had a flag for workspace maybe so that it creates a monorepo, but not sure if that makes sense?
  16. lioloc what do you think?
  17. lioloc like `flog init --workspaces=apps,packages`
  18. lioloc wooooo nice new primate.run website !
  19. lioloc looks sick
  20. blue lioloc: sounds good, could you create a task on flog project?
  21. blue we use flog for primate and rcompat, which are both monorepos. flog is primarily developed for monorepos
  22. lioloc sounds good, I noticed that i had to run flog init inside the apps/<project> as well, this is normal right?
  23. blue I believe flog init just creates a package.json
  24. blue and potentially flog.lock
  25. blue what is inko, phaleth?
  26. blue honestly any new language that forces you to do blue and red functions is something I won't adopt
  27. blue async should be integrated into the language, like in go
  28. blue you should look into cit, phaleth, that's the future
  29. blue tbh even java doesn't have async
  30. phaleth the syntax is not the problem, simply take your time to read the article I've linked above
  31. phaleth there seems to be a lot of good ideas in inko's compiler that just take care of all the nerdy nonsense
  32. phaleth also java is out of question for us anyway, too big of a memory hog
  33. phaleth or any JVM lang for that matter
  34. blue the point is, the answer's been at our door all along, it's c. we take c, we add the most minimal stuff atop, remove the atrocities like pointers, and voila, we're done
  35. blue we don't need all this newage nonsense
  36. blue look at cit, it's beautiful
  37. phaleth that doesn't solve concurrency problems at all, which is the hardest part
  38. phaleth also golang has go keyword, instead of async
  39. phaleth heh, how is that newage nonsense, it's just continuation of whatever also erlang and BEAM languages have been trying
  40. blue because anything that uses or relies on rust is nonsense
  41. blue rust is a complexity that should have never happened
  42. blue complexity is one of the two final bosses of SE
  43. blue I will not ever accept rust in my software stack
  44. blue I'd take java before rust :P
  45. phaleth too late as a lot of what you use is written in rust, heh
  46. blue there are areas I do accept rust, like my terminal (alacritty) or wm (niri)
  47. blue but I will not run a product that relies on rust
  48. blue that's just too much of a gamble. I cannot run code I don't understand
  49. phaleth well, using c++ for a compiler is also a problem
  50. blue yes, which is why cit needs to selfhost ASAP
  51. blue but cit is just getting started, and dog is the only user
  52. blue also cit doesn't need libc as per your suggestion, which is kinda awesome
  53. phaleth yeah, but I don't think writing a new programming language makes sense either
  54. blue did you look at the ownership model of cit?
  55. blue it's kinda cool
  56. phaleth and it's just lately everything is written in rust, cause people are tired of c's undefined behaviours and every c compiler behaving slightly different, every platform requiring platform specific code and so on
  57. blue yeah I understand, but whatever faults c is, rust is definitely not the answer
  58. phaleth I don't have access to that, and also I'm not arguing for rust anyway
  59. blue I thought zig would be the answer for a while, but then that happened
  60. blue it's not like I want to create a new programming language
  61. blue it's just no one is delivering
  62. phaleth yeah, but neither rust, c, zig or cit solve concurrency problems on at least two platforms
  63. phaleth mainly the two we are going to target
  64. blue cit could solve that, we'd need to see how we could design it
  65. blue we have the chance to design a programming around our needs
  66. blue which is the best way to design anything
  67. phaleth no, that is like a huge undertanking and clanker really has no chance
  68. blue all those people designing things do them in a vacuum, that's why when you take them for a run, they never work like you need them
  69. phaleth that is an infinite rabbit hole
  70. blue cit is already working. and I'm slowly improving it, because it's not a high need situation, repopack is already working very well
  71. phaleth yeah, cause it's an infinitely complex problem to not only have the language right, but also have the tooling right
  72. blue I'm hardly spending any time on it on the moment
  73. phaleth and by tooling I also mean standard lib
  74. blue yes
  75. blue most of my time is spent on repopack and primate
  76. blue I wish I had time to work on cit, but I don't
  77. phaleth just don't worry about cit, node is running fine
  78. phaleth or dog or whatever
  79. blue dog is the future :P
  80. blue but honestly, I'm not spending more than 1% of my time on any of this, so don't worry about it
  81. phaleth I mean don't worry about dog as well
  82. blue my time is currently I'd say, maybe 50% repopack, 40% primate, 10% flog
  83. blue flog is mostly done for now, the linting/formatting is like a sideburner
  84. blue and those 40% in primate are mostly requests coming from the repopack team
  85. phaleth flog just needs some more flags and it's done
  86. blue like transactions and so on
  87. phaleth repopack requires shit ton of effort
  88. blue yes
  89. blue but it can already outdo fly in many aspects
  90. blue most of the things I do with repopack, I can no longer do with fly
  91. blue anyway, we're very close to a breakthrough with repopack chat
  92. blue I think that's the moment people can 'get' it
  93. phaleth there are still a lot of features missing compared to fly
  94. blue right now it's like "what is this about"
  95. phaleth and then there is the e-commerce part completely non-existent
  96. blue yes but you need investors for all of this
  97. blue it's a huge undertaking, you gotta convince one
  98. blue and you only convince people by showing them it's useful for them
  99. phaleth in such domain it's possible to sell unfinished product, fly is also still unfinished
  100. blue yes, exactly
  101. phaleth anyway, I highly recommend to read the article as a whole, there's lot of complaints about rust there as well
  102. lioloc for me repopack tasks only started making sense after I used it, and also having had experience contributing to traditional open source projects, but before using it I didn't get it
  103. lioloc For an investor that isn't technical, that will be tricky
  104. lioloc sorry for interjecting
  105. blue true, lioloc
  106. nevet [ByteCode.News] Accreted Specifications - https://bytecode.news/posts/2026/11/accreted-specifications
  107. blue that's simply not. the aws free tier gives you 400,000 GB-seconds of compute time.
  108. blue sorry, wrong channel
  109. blue phaleth: repopack isn't working, could you have a look please?
  110. blue the containers are all up though
  111. phaleth blue: yeah, sorry, it's back now

Search posts