It's called Ostrich effect and we all do it. You enjoy toying with your own idea so much, that your brain shields you from the pain of finding out it already exists. Deep down you know it probably exists. It's harmless, unless there's other people's time and money involved.
> You enjoy toying with your own idea so much, that your brain shields you from the pain of finding out it already exists.
Doesn’t look like the author toyed with the idea at all, though, apart from having it in their head. Considering how they describe themselves (Check the About/Home page), if they had toyed with it at all they would have already built it.
I also don’t see why finding out it exists would be “painful”. The game is free and the author didn’t experiment or learn anything from building it, they just prompted it in one go.
Yes, any default browser just as long at it uses the WebKit engine. This is comparable to how the Ford Model T could be ordered in any colour just as long as it was black.
Apple has been required by the DMA to accept non-webkit browsers in the EU for 2 years now. But in practice no one has built one. There are some claims about malicious compliance on Apple's part (what else is new), but it seems equally likely to me that no one wants to maintain 2 rendering engines for the same app (1 for EU and 1 for the rest of the world).
I remember Google had a slogan “don’t do evil” (dropped since then). On the top of the list of companies that do evil, I have Microsoft and Adobe. They coerce users and they destroy everything they acquire.
Elixir is gradually typed, while Gleam is fully statically typed.
Elixir's type system does not have generics, while Gleam's type system does.
Elixir has a powerful macro system, Gleam has no metaprogramming features.
Elixir’s compiler is written in Erlang and Elixir, Gleam’s is written in Rust.
Gleam has a more traditional C family style syntax.
Elixir has a namespace for module functions and another for variables, Gleam has one unified namespace (so there’s no special fun.() syntax).
Gleam standard library is distributed as Hex packages, which makes interoperability with other BEAM languages easier.
Elixir is a larger language, featuring numerous language features not present in Gleam.
Elixir has an official test framework with excellent support for concurrency, partitioning, parameterized tests, integrated error reports, and more. Gleam has no official test framework, but there are multiple community-maintained frameworks.
Both languages compile to Erlang but Elixir compiles to Erlang abstract format, while Gleam compiles to Erlang source. Gleam can also compile to JavaScript.
Elixir has superior BEAM runtime integration, featuring accurate stack traces and full support for tools such as code coverage, profiling, and more. Gleam’s support is much weaker due to going via Erlang source, resulting in less accurate line numbers with these tools.
Elixir and Gleam both use Erlang's OTP framework. Both have additional modules for working with OTP, which provide APIs more in the style of each respective language. Both common use Erlang's OTP APIs directly, but Elixir can do so more conveniently and concisely due to having a less-strict type system.
Elixir currently has superior deployment tooling, including support for OTP releases and OTP umbrella applications.
Gleam’s editor tooling is superior due to having a more mature official language server, but Elixir has recently announced an official language server project which is in active development.
Elixir is more mature than Gleam and has a much larger ecosystem.
Gleam and Elixir compile at similar speeds due to using the Erlang compiler as their compiler backend. Elixir's macros are evaluated at compile time, so a program that uses macros will take longer to compile the larger the amount of work performed in macros. Gleam has no language features that result in slower compilation.
If you need to declutter your app, simplify the flows, or just make it look better, I'm your man. And I can code everything I draw, so there's no haggling between design and development :-) Avid prototyper, and I ship my own small products + some OSS — https://github.com/josefrichter.
Past: Enaia, Medable, T-Mobile, Vodafone — 764 PRs in my current role, so "I build" is real.
reply