zach43

I wonder if there is a typo in the title: '"C is how the computer works" can lead to inefficient code' makes more sense to me.

> I've got great experience with Indians working in Europe, not so great with Indians working from India. My impression is that the best Indian developers tend to move here, because they'll be able to earn European/American rates.

as an Indian developer working in the US, I have to say that this is a bit of an unwarranted stereotype, despite being repeated often on HN and Reddit

There absolutely is a large contingent of good developers in India (as you'd probably expect from a country with over a billion people), but they are mostly working with locally-managed projects and teams. A lot of them wouldn't work for outsourcing companies because of the poor pay and hours.

There is a bit of confirmation bias going on here: since western companies will frequently outsource to the low-cost shops in India, they will mostly see poor quality work. I don't think its fair to generalize this to all Indian devs.

out of curiosity, how wide apart do you place the two halves of your split keyboard?

i recently got one, and been wondering if i should place them full shoulder width apart or not.

used / refurbished iPhone SEs still work beautifully...i got one a few months ago and i've had zero issues with it

its not really "top of the line" anymore, but the fact that its light on the wallet (~$250) is another major benefit

Gentoo also seems to have updated firefox-bin (and possibly www-client/firefox too?)...I ran an emerge update a few minutes ago and saw it install the firefox update

I think the question of "Why does it takes fifty lines to create a dialogue with a button" is very programming-language dependent:

If you're working with a higher-level programming language, you can make cross-platform GUIs very easily (see tkinter + python as others have recommended) without having to write 50 LOC.

If you're working with C / C++ specifically, then your bottleneck really is figuring out how to build and link with your cross platform library across all platforms. In my experience that has been much more painful than the lines of code required to set up a GUI in C++.

Once you've got the build/deployment system working in C++, most GUI libraries don't need as much as 50 lines of code. For example, even with Qt this is the code to get a dialogue with a button:

    #include <QApplication>
    #include <QPushButton>

    int main(int argc, char **argv)
    {
     QApplication app (argc, argv);

     QPushButton button ("Hello world !");
     button.show();

     return app.exec();
    }

In newer low-level languages with sane standardized package managers, like Rust, things should be much better, but I'm finding any good examples right now

Yeah, I understand the pains of implementing native GUIs, but one of the niceties that they provide is that you can implement simple - moderately complex GUIs in fewer lines and cleaner APIs than what the cross-platform libraries provide.

People who aren't very tech/privacy-savvy, like elderly people, or kids/teenagers.

I remember signing up for facebook when I was in high school, and I probably would've provided my email password if facebook asked for it...as an adult now I wouldn't provide my email password to anyone, of course.