201–210 of 404 posts
Earlier quoted context omitted.
“Bozo” is pretty lightweight for someone actively trying to destroy the foundations of this country’s government and democratic policies.
[flagged]
This sort of condescension is characteristic of people who hold the opinions you do. The rest of your post is complete nonsense.
Earlier quoted context omitted.
[flagged]
They’re calling a public figure a bozo. That’s always been fine. Name calling other HN users is against the guidelines.
Not in Germany. Public insults are punishable. Doing so in a permanent way with lots of outreach (like the web is) increases the consequences.
Earlier quoted context omitted.
Anti-interventionist Democrats criticized military spending but never advocated abandoning treaty obligations that maintained global stability since WWII. (or you would prefer that the US hadn’t even joined the Allies in WWII?) There's a profound difference between questioning military budgets and actively undermining alliances while praising dictators. Your characterization whitewashes the specific nature of Trump's…
[flagged]
> Yes, obviously! How other people run their countries is none of America's business. E.g. as long as Syria was keeping Muslim terrorists from attacking America, it was irrelevant to America how many of his own people he killed.
Where do you think the Syrian's that don't want to die go? This question applies to other countries as well such as say Mexico.
The world is very connected and ignoring that fact will just leave with you ton of problems. Say at the southern border ...
Earlier quoted context omitted.
That's not well-commented code, that's just noise. When you are calling a function named "read_csv()", you do not need to add a comment that says "Read the CSV file". These sorts of comments make code harder for humans to read. The hill that I will die on is that if you need to comment what your code is doing, your code is either a) bad and should be rewritten to be clearer, or b) the result of tricky, clever optimiz…
I agree that there should be "why" comments. Those are great to have in any codebase. However, that does not preclude descriptive comments. Obviously, the best way to make code self-documenting is to wrap logic in a method whose name clearly describes its intended function. For one-liners however this can lead to overabstraction, and leaving a "what" comment can be entirely appropriate if the engineer decides it is.…
Oh the tasty irony.
Earlier quoted context omitted.
[flagged]
“Bozo” is pretty lightweight for someone actively trying to destroy the foundations of this country’s government and democratic policies.
We need politics out of here. Maybe make the line between HN and the rest of news a bit more clear.
And that is where many of us have played a role: increasing engagement.
Works created by U.S. federal government employees as part of their official duties are in the public domain, according to 17 U.S.C. § 105, except for classified or restricted information (but none of what he posted is classified or restricted)
Implying that DOGE bozo is law-compliant while breaking laws and destroying trust is...humor too soon?
Earlier quoted context omitted.
This is a bad comment. It adds nothing to clarify anything, since the function in the line below is "read_csv." This would be a textbook example of a comment that is not useful to improve legibility by humans and it demonstrates a lack of expertise among the people who are currently dismantling our government.
I'm sorry, but a code comment does not demonstrate lack of expertise, although such a perspective certainly brings your own expertise into question. Perhaps we should all assume a little less?
Earlier quoted context omitted.
He's not looking at, he's gathering
I gather things like this all the time. I'm against DOGE as much as 90% of the US is, but collection of open data for curiosity and interest is really not a thing to focus on.
[1] https://www.newsweek.com/doge-support-collapsing-poll-elon-m...