ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

  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. phaleththe idea of "Inter-procedural (whole program) escape analysis" sounds great
  4. phalethanother good idea "The architecture separates CPU-bound work from I/O-bound work into different thread pools"
  5. phalethactually 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. blueHi phaleth
  8. phalethhi blue
  9. blueclanker is sleeping
  10. bluewhat's up?
  11. phalethlooking into inko
  12. phalethno idea what's up with clanker, but inko seems like ideal lang for clankers
  13. liolochey guys, can you use flog for monorepos?
  14. liolocblue: ^
  15. liolocnvm 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. liolocwhat do you think?
  17. lioloclike `flog init --workspaces=apps,packages`
  18. liolocwooooo nice new primate.run website !
  19. lioloclooks sick
  20. bluelioloc: sounds good, could you create a task on flog project?
  21. bluewe use flog for primate and rcompat, which are both monorepos. flog is primarily developed for monorepos
  22. liolocsounds good, I noticed that i had to run flog init inside the apps/<project> as well, this is normal right?
  23. blueI believe flog init just creates a package.json
  24. blueand potentially flog.lock
  25. bluewhat is inko, phaleth?
  26. bluehonestly any new language that forces you to do blue and red functions is something I won't adopt
  27. blueasync should be integrated into the language, like in go
  28. blueyou should look into cit, phaleth, that's the future
  29. bluetbh even java doesn't have async
  30. phaleththe syntax is not the problem, simply take your time to read the article I've linked above
  31. phaleththere seems to be a lot of good ideas in inko's compiler that just take care of all the nerdy nonsense
  32. phalethalso java is out of question for us anyway, too big of a memory hog
  33. phalethor any JVM lang for that matter
  34. bluethe 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. bluewe don't need all this newage nonsense
  36. bluelook at cit, it's beautiful
  37. phaleththat doesn't solve concurrency problems at all, which is the hardest part
  38. phalethalso golang has go keyword, instead of async
  39. phalethheh, how is that newage nonsense, it's just continuation of whatever also erlang and BEAM languages have been trying
  40. bluebecause anything that uses or relies on rust is nonsense
  41. bluerust is a complexity that should have never happened
  42. bluecomplexity is one of the two final bosses of SE
  43. blueI will not ever accept rust in my software stack
  44. blueI'd take java before rust :P
  45. phalethtoo late as a lot of what you use is written in rust, heh
  46. bluethere are areas I do accept rust, like my terminal (alacritty) or wm (niri)
  47. bluebut I will not run a product that relies on rust
  48. bluethat's just too much of a gamble. I cannot run code I don't understand
  49. phalethwell, using c++ for a compiler is also a problem
  50. blueyes, which is why cit needs to selfhost ASAP
  51. bluebut cit is just getting started, and dog is the only user
  52. bluealso cit doesn't need libc as per your suggestion, which is kinda awesome
  53. phalethyeah, but I don't think writing a new programming language makes sense either
  54. bluedid you look at the ownership model of cit?
  55. blueit's kinda cool
  56. phalethand 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. blueyeah I understand, but whatever faults c is, rust is definitely not the answer
  58. phalethI don't have access to that, and also I'm not arguing for rust anyway
  59. blueI thought zig would be the answer for a while, but then that happened
  60. blueit's not like I want to create a new programming language
  61. blueit's just no one is delivering
  62. phalethyeah, but neither rust, c, zig or cit solve concurrency problems on at least two platforms
  63. phalethmainly the two we are going to target
  64. bluecit could solve that, we'd need to see how we could design it
  65. bluewe have the chance to design a programming around our needs
  66. bluewhich is the best way to design anything
  67. phalethno, that is like a huge undertanking and clanker really has no chance
  68. blueall 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. phaleththat is an infinite rabbit hole
  70. bluecit is already working. and I'm slowly improving it, because it's not a high need situation, repopack is already working very well
  71. phalethyeah, cause it's an infinitely complex problem to not only have the language right, but also have the tooling right
  72. blueI'm hardly spending any time on it on the moment
  73. phalethand by tooling I also mean standard lib
  74. blueyes
  75. bluemost of my time is spent on repopack and primate
  76. blueI wish I had time to work on cit, but I don't
  77. phalethjust don't worry about cit, node is running fine
  78. phalethor dog or whatever
  79. bluedog is the future :P
  80. bluebut honestly, I'm not spending more than 1% of my time on any of this, so don't worry about it
  81. phalethI mean don't worry about dog as well
  82. bluemy time is currently I'd say, maybe 50% repopack, 40% primate, 10% flog
  83. blueflog is mostly done for now, the linting/formatting is like a sideburner
  84. blueand those 40% in primate are mostly requests coming from the repopack team
  85. phalethflog just needs some more flags and it's done
  86. bluelike transactions and so on
  87. phalethrepopack requires shit ton of effort
  88. blueyes
  89. bluebut it can already outdo fly in many aspects
  90. bluemost of the things I do with repopack, I can no longer do with fly
  91. blueanyway, we're very close to a breakthrough with repopack chat
  92. blueI think that's the moment people can 'get' it
  93. phaleththere are still a lot of features missing compared to fly
  94. blueright now it's like "what is this about"
  95. phalethand then there is the e-commerce part completely non-existent
  96. blueyes but you need investors for all of this
  97. blueit's a huge undertaking, you gotta convince one
  98. blueand you only convince people by showing them it's useful for them
  99. phalethin such domain it's possible to sell unfinished product, fly is also still unfinished
  100. blueyes, exactly
  101. phalethanyway, I highly recommend to read the article as a whole, there's lot of complaints about rust there as well
  102. liolocfor 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. liolocFor an investor that isn't technical, that will be tricky
  104. liolocsorry for interjecting
  105. bluetrue, lioloc
  106. nevet[ByteCode.News] Accreted Specifications - https://bytecode.news/posts/2026/11/accreted-specifications
  107. bluethat's simply not. the aws free tier gives you 400,000 GB-seconds of compute time.
  108. bluesorry, wrong channel
  109. bluephaleth: repopack isn't working, could you have a look please?
  110. bluethe containers are all up though
  111. phalethblue: yeah, sorry, it's back now