I've said it before and I'll say it again: presidential systems suck. I'm not an expert on Polish politics, but it seems at the very least like the Poles were given a good choice of a candidate. Still, having too many people voting for a single candidate for a single office repeatedly leads to bad outcomes. France, Turkiye, USA - now we can add Poland to the list too.
Abolish presidencies! Embrace parliamentary systems!
100% agree. But I like posting articles like these because it brings me back to how I learned programming, and Linux specifically - namely by reading a bunch of articles from similar link aggregators and sharing sites.
My hope is that sharing articles like these is a form of planting the seeds for another cycle for people to learn the way that I did.
We can easily take images like this for granted today, but for its time, a photograph like this was an incredible achievement. Both photography itself as well as air travel have progressed a lot over the 160+ years since this photo was taken. It really puts a lot into perspective how much technology (and the world itself) has changed in so much time.
I just disabled this today and life is so much better. Thanks! Everything works so much better now.
There are a lot of other helpful replies in this thread, so I won't add much, but I did find this reference, which you could read if you have a lot of free time. But I particularly liked reading this summary:
- _start calls the libc __libc_start_main;
- __libc_start_main calls the executable __libc_csu_init (statically-linked part of the libc);
- __libc_csu_init calls the executable constructors (and other initialisatios);
- __libc_start_main calls the executable main();
- __libc_start_main calls the executable exit().
Reserving main is definitely more hacky. Try compiling multiple objects with main defined into a single binary - it won't go well. This can make a lot of testing libraries rather convoluted, since some want to write their own main while others want you to write it because require all kinds of macros or whatever.
On the other hand, if __name__ == "__main__" very gracefully supports having multiple entrypoints in a single module as well as derivative libraries.
Is it? I really don't think so. What can you propose that's better? I think if __name__ == __main__ works perfectly fine and can't really think of anything that would be better.
And you don't have to use it either if you don't want to anyway, so no, I don't think it's that much of a hack. Especially when the comic compares C as an example, which makes no sense to me whatsoever.
I have no words for how stupid of an idea this was. Pitching your browser as a privacy-friendly alternative (which few people ever cared about), and then doing the exact opposite thing and integrating a service like this which nobody asked for, and also making it unremovable was just a hilariously stupid move.
Good riddance, but the damage done by this chapter of stupidity is basically irredeemable.
Can you put some milk on the algorithm please?
You're right, but I think the main reason companies like it is because it's easier to get rid of contractors than full-time employees.
Vim when I can, and when I can't, Neovim with plugins (LazyVim). Both are fast. I have had troubles with Neovim and configuration, and it does some things that really annoy me (like autoclosing parentheses - it just messes up everything). Honestly, the only feature that I really need is Go To Definition.
But vim - I absolutely love it. I started using it nearly 20 years ago and it still does everything one could want if you're willing to learn the keymaps and commands. Macros, ci), block indentation and so on. It's even great for editing XML. If the codebases I'm working on these days weren't so large and complicated, I would still be using it with very little configuration in my .vimrc.
Sticky headers. Unbearably distracting.
Also, wasted space and a lack of information density.