ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

  1. phalethbun is gone https://repopack.com/project/repopack/tasks/786
  2. blueamaze sauce
  3. phalethalso clanker added gawk to two of the containerfiles, including a debian one, too funny, but other than that good work
  4. phalethshows clanker can follow patterns
  5. blueya
  6. bluesoon node will be gone too hopefully, once dog/cit stabilises
  7. phalethhah, really
  8. phalethanyway, it's great how clanker can do so much working during late evenings
  9. blueya
  10. phalethI mean for development dog can be used, why not
  11. bluedog can be used in production as well. it's just v8 in the end so it's no different than node. just better APIs
  12. phaletheven for prod, as long as there are no latency and resources consumption issues
  13. blueya
  14. blueif all goes well anyway, all that clanker needs to do is change @rcompat stuff to std:
  15. phalethdoes that mean rcompat will be baked in rewritten in golang?
  16. bluein cit, yes
  17. bluedog is written in cit
  18. phalethoh, ok :D
  19. phalethI hope cit has no backend and just compiles to AT&T assembly
  20. blueyes, it's currently written in c++. will self host eventually
  21. bluecit is a rather simple language
  22. bluehex(u32 value) u32 {}
  23. phalethself hosting is a waste of time when there is gcc installed on most of linux distros
  24. blueor rather in this case
  25. bluehex(u32 value) u32 { return 1; }
  26. bluetypes before identifiers, like java, unlike zig/rust
  27. bluefunctions don't have an fn keyword, you just write them
  28. blueif you wanna export a function, you add `export` before the name
  29. bluephaleth: https://dpaste.com/5BAGB3SSE.txt
  30. bluesmall example in cit
  31. bluea bit safer than zig, but no rust borrow checker craziness
  32. bluetransfers ownership. it must be specified on both sender or receiver, any other combination is an error
  33. blueFactoidUpdatedEvent(selector=transfers ownership. it must be specified on both sender or receiver, any other combination)
  34. nevet`ok, blue: updated transfers ownership. it must be specified on both sender or receiver, any other combination.
  35. blue() cleans up in a struct (only known as a destructor in other languages)
  36. phalethdpaste is busted
  37. bluebusted?
  38. bluedoes'nt work?
  39. phalethyeah, it blocks proxies
  40. bluewhat works for you?
  41. phalethbut whatever, I'm not interested in complexity :D
  42. phalethwe can use dog as long as there is trust me bro installer to install somewhat stable version
  43. phalethshould actually be beneficial when the image drops all the non-runtime specific fat
  44. blueok, great
  45. phaleththe reason I'm hoping for it to compile to AT&T assembly is to avoid all the glibc problems
  46. phalethand so it should then just run on alpine
  47. phalethof course it will not be compatible with freebsd, but whatever, I don't even know if AT&T assembly is used on freebsd, prolly it is
  48. phalethand I mean x86_64 of course
  49. phalethalso gcc can just convert AT&T assembly to Intel assembly
  50. phalethor the other way around if clanker decides that Intel assembly is better
  51. blueok fair, added notes to dog projec
  52. bluet