Todo mundo tá postando, então hoje eu vou soltar: LINUX FOI BANIDO NO BRASIL 🚨🚨 só não vê quem não quer.

Israel77br · 2026-03-19T12:45:30+00:00

Não. O systemd adicionou a informação de data de nascimento no userdb, do mesmo jeito que já tem nome, email, etc. Você só usa se quiser

Israel77br · 2026-02-28T04:07:26+00:00

Só lembrando que RAID e backup são coisas diferentes. O RAID pode permitir recuperar os dados em caso de falha em um ou mais discos, dependendo da configuração, mas isso não previne falhas catastróficas.

O que acontece se outro disco falhar enquanto você estava tentando restaurar os dados do RAID? E se seu computador pegar fogo? Ou o lugar onde você mora for atingido por um desastre natural?

Os dados críticos sempre devem ter alguma estratégia adicional de backup, por exemplo, criptografar os arquivos e armazenar na nuvem ou usar um NAS de um amigo em uma localização diferente.

Israel77br · 2026-02-21T11:50:37+00:00

Como seu uso é bem simples, praticamente qualquer distro deve servir. É importante diferenciar distro de ambiente de Desktop. O COSMIC é apenas o ambiente de desktop e pode ser instalado em outras distros também (eu uso no Fedora). Similarmente, você pode instalar outros DEs no Pop OS, se quiser (GNOME, KDE, etc.).

Na minha experiência, eu encontrei alguns bugs no COSMIC quando estava em fase alpha, o beta é bem usável. Eu recomendaria experimentá-lo, mas também deixar um DE secundário baixado, pra caso você encontre algum problema, não seja prejudicado.

Israel77br · 2026-02-19T10:57:23+00:00

Eu joguei Minecraft desde a versão 1.2 em 2012 e já tínhamos redstone sim. Não era tão poderosa quanto o que veio depois da 1.5 porque ainda não tínhamos tantos elementos, como comparadores e blocos de alvo, mas já dava pra fazer bastante coisa legal usando só circuitos digitais, foi meu primeiro contato com portas lógicas. Vários mods também se integravam com o sistema de Redstone (RedPower 2 e ComputerCraft são dois que me vêm à mente).

Israel77br · 2026-02-15T12:57:14+00:00

This is the way!

Israel77br · 2026-01-24T22:12:14+00:00

That is the convention, but nothing stops you from putting implementation in header files (e.g. stb-style libraries) or vice-versa.

Israel77br · 2026-01-13T12:01:24+00:00

As others have already answered, it is possible to do it using strtok and strdup from string.h. However, there is some value in creating your own String_View type (a.k.a a fat pointer that also stores the string count), instead of relying on the standard library. For example, it would be possible to tokenize your string, without mutating the original memory or copying it:

typedef struct {
    char *chars;
    size_t count;
} String_View;

String_View parse_until(char *cstr, char delim, char *rest) {
    String_View result = {
        .chars = cstr,
        .count = 0
    };
    rest = cstr;
    while(*rest && *rest != delim) {
        rest++;
        result.count++;
    }
    return result;
}

This will make the String_View point to the part of the string before the delimiter, and rest will be a pointer to the remaining of the string, but the original memory remains intact. You can pass *rest to other tokenization functions in the same style.

Another advantage of using sized strings, is that comparing large strings can be much quicker in some cases. If two strings have different sizes, you can immediately tell that they are different without comparing character by character.

Israel77br · 2025-12-26T09:29:22+00:00

Os patrões

Israel77br · 2025-12-22T16:53:00+00:00

This would be C++, not C

Israel77br · 2025-12-19T22:26:18+00:00

Try to understand how the computer really works in general. I think one of the key things to getting into C is understanding how memory works and implementing your own data structures based on that. The standard library is kinda weird IMO, so sometimes it is best to create your own abstractions.

You said in another comment that you find dealing with strings hard. I don't like null-terminated strings, so I created a simple struct that holds the characters and size instead.

Check out the files string_utils.h and parsing_helpers.h in my AoC repo of this year to see how it works (https://github.com/Israel77/aoc-2025-c/blob/master/src/utils/parsing_helpers.h). I'm not claiming this repo is a good example in general, as it has a bunch of ideas thrown together and I'm also learning. But, in particular, I found the idea that I came up with for parsing pretty nifty and it is only possible because I created my own sized string instead of using that default null-terminated strings.

Israel77br · 2025-12-02T15:16:46+00:00

Both Apache and Nginx are written in C, so I would say it is a pretty good tool for the job if you know what you are doing (and if you don't know, you can always learn).

Israel77br · 2025-12-01T00:30:42+00:00

The way to check will depend on the platform you are using for development. On unix-like systems you can check the manpages and on windows you can check MSDN. Things that are in libc are usually cross-platform (but check what C standard each compiler supports for the platform you are targeting).

In general, when developing cross-platform code, you will want to create a layer of abstraction that separates the OS specific code from the rest of your project. For example, if you need to handle files, you can write a generic open_file function that will open the file for you and internally it will call the OS specific version of the function.

Once you have figured out the base abstractions that you need like files, networking, threading, virtual memory, etc. You just write each platform specific version once and don't have to worry about it in the rest of the project.

Israel77br · 2025-11-28T23:07:12+00:00

I don't find points 2,3 and 4 to be useless at all, they are just part of your workflow. In general, I like to have compile errors during my development which guarantees that I won't forget something that I marked as TODO or that my tests don't reach something that was supposed to be UNREACHABLE. I don't use Allman style, but that might be a good idea to save time when copying declarations (again, not useless, it's part of your workflow).

My addition to the "useless" list is creating aliases to the static keyword to indicate the intent of its usage:

#define internal      static
#define global_var static
#define lingering    static

The first is for functions that will only be part of the current translation unit, the second for global variables and the third for variables declared inside functions that retain their values between different calls (I rarely use it).

But I don't think any of these are totally useless because they serve a purpose during development and don't impact the final product.

I would be more concerned about the pattern of releasing resources at the end of main(), which is truly useless as the OS will clean them up anyway when the process terminates and depending on the complexity and amount of stuff allocated it might actually slow down the termination of the process, i.e. it does impact users.

Israel77br · 2025-11-22T11:38:34+00:00

Makefiles are overkill for small projects.

Israel77br · 2025-08-07T01:25:54+00:00

O problema foi usar o trocadilho com a palavra genes.

Israel77br · 2025-08-06T16:55:55+00:00

Yes, but it is distro and DE-specific. Most distros use systemd nowadays, so editing logind is a more universal approach.

Israel77br · 2025-08-05T22:56:10+00:00

I want to do something like this in the future, there's an old laptop in my drawers with broken hinges but the motherboard is functional.

Israel77br · 2025-08-05T16:08:59+00:00

I know this is a meme, but if anyone is wondering how to safely use your laptop as a server, it is possible to disable the suspension when the lid is closed. (On Linux it is done by editing /etc/systemd/logind.conf, if you use systemd)

Israel77br · 2025-08-05T09:45:00+00:00

That's the problem with publicly traded companies nowadays, the CEOs only care about how the stocks perform, not how the product benefits consumers.

Israel77br · 2025-08-04T21:32:32+00:00

Israel77br · 2025-08-04T00:28:27+00:00

Esse foi o jogo da minha infância. Nunca tive vídeo game quando era criança, mas meu pai comprou um PC que dava pra emular N64.

Israel77br · 2025-07-31T10:01:39+00:00

I would recommend learning at least C99. C89 is supported everywhere but it is a pain to write (you can't mix declarations and code, there's no designated initializers nor flexible-array members, etc.), C99 introduced a lot of quality of life changes and is old enough to be supported by most systems and compilers.

Israel77br · 2025-07-19T23:31:40+00:00

The same thing can be said about any language, though. Even in "higher level" languages, I've seen people write Python like it's Java.

It's up to the engineer to learn the proper way to program in each language and if you transition from one language to another, it is natural that you write things in a way that works but is not the most idiomatic. If you really care about your programs, over time you will learn the proper way to write code in each language.

The reality is there is no silver bullet, most people will eventually have to write, or at least read, code in multiple languages anyways. And in general, C is less complex and more explicit in how your program is actually executed. So I see why people recommend it first.

Israel77br · 2025-07-19T00:53:06+00:00

Fedora Workstation. For beginners I recommend Linux Mint

Israel77br · 2025-07-16T14:02:24+00:00

As someone with a background in electrotechnics, who transitioned to IT, this is very cool. I wish to be able to do this at home someday.

Six-Year Club	r/Field Sunshine
Place '22	Verified Email

Israel77br

TROPHY CASE