crbelaus

This is great! Would love to see if Opencode sends different payloads and hoe they differ.

The progressive introduction of automated type checking in Elixir should serve as a reference on how to improve a programming language gracefully without breaking changes.

So many examples of programming languages have huge breaking changes between versions that end up creating a split in the ecosystem that takes years to resolve.

Thankfully José has been very clear about Elixir being done since at least 2018. The language is stable and the language/core foundation is not changing anymore.

https://www.youtube.com/watch?v=suOzNeMJXl0

Truly outsanding work and stewardship.

I (along with a friend) am working on an Elixir-based built-in error reporting and tracking solution: https://github.com/elixir-error-tracker/error-tracker

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).

https://archive.is/hJBD3

Seems to work just fine from Spain

The multi screen sharing problem in Chromium is a known one. I've been following this patch for some time, and it seems to be close to release now: https://webrtc-review.googlesource.com/c/src/+/165724

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.

All of the troubles explained in the post are caused by a bug in Chromium which identifies all the monitors as a single one.

If you are interested take a look at the bug in the Chromium issue tracker: https://webrtc-review.googlesource.com/c/src/+/165724

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.

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]

[1] https://github.com/rrrene/credo [2] https://github.com/elixir-ecto/ecto [3] https://ebertapp.io/ [4] https://github.com/elixir-ecto/ecto/pull/1785

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...

It's incredible how small is the Internet. Just today I went to my optometrist because I have problems focusing objets at a certain distance. Turns out that I had exactly the same diagnosis, and I was recommended to buy a 0.5 glasses and use them when I'm staring at the computer or tablet.

It may shound harsh, but why should I want a modular Android phone? To update my hardware over the years to come while still running the same Android version without receiving updates.

Google, your Android updating system is fucked up. Fix it first, and then we can talk about exending the life of hardware.

Atom is my main editor (actually I use Vim for git commit messages and for doing quick file editions). It may be unresponsive sometimes, but it is known, officialy recognized and actively being worked on.

The main reason I use Atom is because it is free as in freedom. Since Emacs and Vim no other free text editor has received so much effort. This makes me think that Atom will live for a very long time.

Actually, with the current EU laws it is not.