It boils down to simplicity. While error reporting is extremely valuable for most projects, it is absent from many. The most common reason is that this requires entering SaaS territory. Most solutions are provided by third-parties that require you to subscribe and pay for the privilege of tracking your errors. Cost is the main noticeable downside. Data protection (GDPR, HIPAA, etc) is another.
As other commenters say, latest Fedora has Wayland and Pipewire properly configured and by enabling a flag in Chrome/Chromium (search by "pipewire") it will run smoothly and allow you to choose which screen to share.
I want to use Firefox for everything.
Unfortunately my company relies a lot on Google Hangouts and Meet for video calls. Google has implemented both in a way that seems to be incompatible with Firefox (I know that the non corporate version of Hangouts works with Firefox since a few months ago).
After reading the title this was exactly my first thought.
Polluting the titles with emojis feels unnecessary and childish to me. I them a mental burden that makes it difficult to read the important information.
I can not imagine a new car announcement page filled with emojis and I don't know why it should be different for software.
With emojis in the headlines, I look at a tiny picture for 0.2s (usually related to the headline) and then read the section as normal. How can that be a mental burden?
Thank you very much for mentioning Plato here. I was thinking exactly about this wile reading this paragraph:
> Let us also be clear that classes do not “model the real world”. Objects may or may not model the real world, but classes certainly don’t. Although there are many chairs in the real world, there is no “chair class” in the real world.
Totaly agree. Dialyzer/Dialyxir can provide a high degree of confidence about types.
The wonderful thing about it is that you don't have to get all type annotations since the begining, you can add them over the time. This allows to use "unspecified" types for quick prototyping, and make them more specific when the project evolves, which is a major complain of traditional type systems such as Java's.
Another tool that I find useful is Credo[1] which "is a static code analysis tool for the Elixir language with a focus on teaching and code consistency".
The Ecto[2] project uses a tool called Ebert[3] that automatically runs Credo for each pull-request and comments with the issues found. Here you can see an example of Ebert's bot commenting on a PR[4]
I have one for the work. It is absolutely wonderful.
I am currently using Ubuntu 16.04.1, and I feel it lightweight and performant. The battery lasts about 9 and a half hours (doing web browsing and light programming).
I suppose that the thing will only improve with future Ubuntu Hardware Enablement Stacks that include new kernels and so...
I wrote a post explaining the reasons for building this when we already have multiple third-party SaaS providers: https://crbelaus.com/2024/07/31/built-in-elixir-error-report...
It boils down to simplicity. While error reporting is extremely valuable for most projects, it is absent from many. The most common reason is that this requires entering SaaS territory. Most solutions are provided by third-parties that require you to subscribe and pay for the privilege of tracking your errors. Cost is the main noticeable downside. Data protection (GDPR, HIPAA, etc) is another.
The Elixir community is providing great feedback and it was covered both in a YouTube video (https://youtu.be/TNmSVjGyZx0?si=yd6kOwa2ZpxUyFad) and a Podcast (https://podcast.thinkingelixir.com/215).