There are two sides to compatibility with Elixir: using Gleam in Elixir and using Elixir in Gleam. The former is harder, the latter is easier (with caveats).
Using Gleam in an Elixir project did/does rely on mix_gleam. I've used it some years ago and it worked then, but I haven't had recent experiences. There is a pull request[0] to Elixir to add built-in support for Gleam and as I understand it the Gleam team have made several changes to Gleam tooling to facilitate it, but it's unmerged as of now.
Using Elixir in a Gleam project is just an external function away, just like using Erlang or JavaScript (when using the JS target). E.g.
You can also write .ex files in your codebase and use functions from them as externals and they'll be compiled by Gleam.
The two main issues on that side are macros and structs. Since Gleam doesn't know about Elixir source or Elixir macros, you can't use them directly. But you can have an .ex file that uses macros and then you can call functions from that file. Structs are trickier, because they're just dynamic maps with a special key-value pair, and maps in Gleam (called Dict) have fixed types for the keys and values. That means you can't model a struct as a Dict. Gleam uses records for its own custom types, so what you can do is either use records on the Elixir side (with the Record module or by hand), or map the Elixir side data structures to be more palatable for Gleam (and vice versa) in your external functions --- which is what you generally do with externals anyway. Of course, if you only intend to pass the Elixir structs around and then back to Elixir, you can model them as external types that are then opaque to Gleam.
This article is a bit old, LVV has already ordered Google to stop construction until the YVA processes are done. What is still unclear is if Google will face any repercussions for acting before the YVA was done, but it is looking unlikely.
That's the entire reason the court stopped construction. It's in the public documents. The ESA was supposed to identify any plots of old growth native forests (especially stuff like bogs and streams). Google rushed to cut everything down to remove any evidence of old growth habitats but they claimed that they did their own internal assessment beforehand and preserved a few of those sites. The Finnish Association for Nature Conservation (aka Suomen luonnonsuojeluliitto) is the group that used satellite imagery to argue in court that they lied and that there were several native, protected strands that were NOT spared.
Which court stopped construction? I have not read that courts are involved at all yet, only that Finnish Supervisory Agency (Lupa- ja valvontavirasto LVV) has ordered Google to stop construction. I found a source [0] claiming that some areas that are important for biodiversity were first spared and then cut down, but this does not mean that they were old growth and the Muhos county official Mikko Kari states "[The areas] are not legally mandated to be protected."
Now, I'm not a fan of Google and I'd much prefer this whole project was scrapped, which is why I'm interested if there are sources that provide something that I've missed from the Finnish media.
> More than 75% of Finland’s land area is covered with forest. [...] About 3 million hectares of Finnish forests are protected or under restricted use, which represents 13% of the total surface area of forests (forest land and low-productive forests). The area of protected forests fully excluded from fellings is 2.5 million hectares, which represents 10.8% of the total surface area of forest and low-productive forest land.
I still call it the Apple key ("omppu" in Finnish, colloquial form of "omena") even though the symbol hasn't matched for a long time. I use it when thinking about shortcuts as well, like a screenshot being shift-omppu-4.
A classic way of getting endless money in Transport Tycoon was to build a tunnel going from one edge of the map to another. The money counter would overflow and you'd get enough money to last you a lifetime.
As kids we didn't know why this would happen, we just knew that it did and used it every game.
In my case it's my Forgejo instance. My blog is static files with a limited amount of pages to crawl and indeed it's no issue at all. Forgejo is a dynamic service with an infinite amount of pages to discover and it runs git in the background to generate (some of) the pages. Tons of bots can easily overwhelm my small server. I could hide the repositories, but they're open on purpose (it's open source after all).
I have it guarded by a simple cookie check now, which seems to work well enough. Only a small subset of bots pass it. It likely kills search engine discoverability, but that's the tradeoff I have to make.
Using Gleam in an Elixir project did/does rely on mix_gleam. I've used it some years ago and it worked then, but I haven't had recent experiences. There is a pull request[0] to Elixir to add built-in support for Gleam and as I understand it the Gleam team have made several changes to Gleam tooling to facilitate it, but it's unmerged as of now.
Using Elixir in a Gleam project is just an external function away, just like using Erlang or JavaScript (when using the JS target). E.g.
You can also write .ex files in your codebase and use functions from them as externals and they'll be compiled by Gleam.The two main issues on that side are macros and structs. Since Gleam doesn't know about Elixir source or Elixir macros, you can't use them directly. But you can have an .ex file that uses macros and then you can call functions from that file. Structs are trickier, because they're just dynamic maps with a special key-value pair, and maps in Gleam (called Dict) have fixed types for the keys and values. That means you can't model a struct as a Dict. Gleam uses records for its own custom types, so what you can do is either use records on the Elixir side (with the Record module or by hand), or map the Elixir side data structures to be more palatable for Gleam (and vice versa) in your external functions --- which is what you generally do with externals anyway. Of course, if you only intend to pass the Elixir structs around and then back to Elixir, you can model them as external types that are then opaque to Gleam.
[0] https://github.com/elixir-lang/elixir/pull/14262
reply