Rendered at 11:22:45 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
Defletter 10 hours ago [-]
Huh, I didn't know how much I needed a "todo" type until now. So often I'll be defining a packet sumtype, or a collection, and not have created the type yet, so just use ubyte, or Object, or whatever. Having an explicit "todo" type would be amazing in other languages.
adamdecaf 10 hours ago [-]
Scala has had a function called ??? which fills the same role and it’s really useful.
Every time I read one of these I’m impressed by the language server work. Gleam’s DX is so good.
3stacks 27 minutes ago [-]
but do they oppose nazism? This is a key factor in choosing a programming language
__jonas 13 hours ago [-]
Lovely to see support for building escripts in the compiler.
I’d be excited to see that go one step further and provide something like the deno/bun/node compile feature, allowing one to export a binary that includes the BEAM and compiled code in a single file. I know some people are working on tools like that already and it’s not trivial, but having it in the compiler would be really neat.
ofrzeta 6 hours ago [-]
Stupid question but does the Gleam website run on Gleam?
The BEAM JIT is all done when .beam files are loaded. It's a runtime JIT, because you can always load new code, but it's not a tracing JIT and it's designed to be pretty fast to do it while loading. For most applications of BEAM, I think the time spent loading code, including JIT, is probably immaterial.
If you have a special need, I haven't seen anyone do it, but I would expect it wouldn't be that hard to run the jit ahead of time. I haven't fully studied it, but I think the expectation is the output from jit should be pretty much the same every run, so it seems doable to generate it once and load many times.
https://scala-lang.org/api/3.3.1/scala/Predef$.html#???-0
If you have a special need, I haven't seen anyone do it, but I would expect it wouldn't be that hard to run the jit ahead of time. I haven't fully studied it, but I think the expectation is the output from jit should be pretty much the same every run, so it seems doable to generate it once and load many times.