HN user
It is more obvious with some and a bit more nuanced with others, but in general yes. Just like you can typically see the flat/wide nose in Africans and Asians but not Europeans. Again, there is no implication of one being "better" than the other here, but don't pretend it's impossible to categorize people like this.
Skin color and (facial) bone structure for example. Like it or not, but humans have adapted to living in different climates and have different ancestral lines. Take a picture of an average black person and edit to white skin, it will still not look like a white person.
As the commenter above you already said, this is not a bad thing. People on _hacker_news should be able to understand that being able to define the ==/!= operators on something does not automatically mean that you can define < and >.
The problem is what follows. They will make it mandatory to use the electronic ID to do anything, resulting in total surveillance. And if you happen to land on their "bad" list (which eventually everyone will), you're locked out of life completely. No banking, no traveling, no communication with anyone, no buying food, nothing.
I would guess that Ada is simply more known. Keep in mind that tech exploded in the past ~3.5 decades whereas those languages are much older and lost the popularity contest. If you ask most people about older languages, the replies other than the obvious C and (kind of wrong but well) C++ are getting thin really quickly. COBOL, Ada, Fortran, and Lisp are probably what people are aware of the most, but other than that?
If you have lots of pointers, you're writing C, not C++.
But my main gripe with tabs is that no one agrees on the width.
That's the entire point of tabs. One tab means one indentation level and you as the user can decide how that's displayed. Spaces forces everyone to see the code exactly as whoever decided on his favourite width and that is in the best case "only" annoying to people with different preferences and in the worst case actively hurtful to people with disabilities.
The only argument spaces people ever have is "some of my colleagues are too stupid to properly indent with tabs and align with spaces" and that is trivially fixed by either of those:
- don't use alignment, it's useless anyway
- get better coworkers
- educate your coworkers
- use commit hooks to check wrong usage
So basically there is no argument left on the spaces side at all^[1]. Meanwhile tabs semantically mean "one indentation level", take up less bytes, and most importantly allow everyone to have their own preferences without affecting other people. And honestly I am insanely baffled by how many people don't get the importance of that last part. Accessibility like that costs you nothing but means the world to other people, similarly how we have ramps at public buildings for the elder, wheelchair users, strollers, and so on. And not to mention the fact that there are a lot of autistic people in programming, which often have a harder time dealing with things not being as they want them to be. Is there any reason to choose an objectively inferior method and force that onto those demographics just because "muh alignment"?
[1] Okay fine, there is one: "Tools I don't own don't display tabs as I want them, for example GitHub with their retarded default of 8". But first of all you can change that if you're logged in and second you're supposed to use your IDE and not a web interface...
Ah, I didn't know that. To me your sentence read like autists out themselves by wearing a smartwatch.
Fully agree with you on that, the less data they have, the better.
and wearing a fitbit or smart watch.
Since when is wearing smart watches only for autists?
You should get your calculator checked. 9.11 is definitely less than 9.9
There is a GitHub icon directly at the top right of the side so your first two steps can be combined into one shorter one. But yes, screenshots should absolutely be on the home page, and prominently so.
If you want a game where you effectively script/program the entire gameplay, check out Bitburner: https://store.steampowered.com/app/1812820/Bitburner/
I can't say why the scientists aren't flocking to Nim, but as someone who wants to support them wherever they go, it's why I'm uncertain if it was the right call.
Because most scientists are only using programming as a tool and don't care one bit about it beyond what they need it to do. They don't go looking for new tools all the time, they just ask their supervisor or colleague and then by default/network effects you get Python, Fortran, or C"++". You need a killer argument to convince them to do anything new. To most of them suggesting a new language is like suggesting to use a hammer of a different color to a smith - pointless. With enough time and effort you can certainly convince people, but even then it's hard. It took me years to convince even just one person to use matplotlib instead of gnuplot when I was working in academia. You can obviously put that on my lack of social skills, but still.
Well first of all, C++ is the language you'd be using to power a rocket engine. And second, that code is a terrible example because most of it isn't C++. Large parts of that are very C like or directly C because it's using the Windows API.
Only due to contraceptions not being a thing for most of history.
Which is impossible to do properly, because those keyboards differ from US keyboards in their geometry, not just in the labeling of the keys.
The only difference is that on US keyboards the enter key is smaller and left shift is larger, leading to the "\" key being moved one down and one left on a German keyboard (and also being duplicated to left of z (German label: y)). So even if you move from a physical US keyboard to a physical German one while keeping the US layout, it's literally just one key where you'd have to retrain your hand. And for people that have learned to type on a German keyboard this is not a problem at all since they have never typed on a physical US one and using a different mapping means a training period anyway.
Source: German who mapped his keyboard to US (+ some AltGr modifiers for the German characters I need).
I don't know about the other European layouts, but I assume it's somewhat similar for them too.
While that is true, there might be other requirements that prevent memory safe languages from being used. For example not having a heap available instantly disqualifies most of them. Or when you have simulations running where having constant OOB and other checks would be a massive slowdown. Now obviously your code should still be memory safe (because otherwise it's not correct anyway and you should fix the code), but not at the cost of runtime checks.
We can not let a tyranny of 1% of users steer the ship.
Normally I'd agree with you on that the tyranny of the minority is a bad thing, but sometimes the minority actually has a point and this is one of the cases where the minority is _objectively_ correct and letting the majority decide would end up in a complete dystopia. Democracy only works if everyone is informed (and able to think logically/critically, not influenced (either by force or by salary), etc.) and in this case the 99% simply do not have any clue on the effects of this being implemented (nor do they care). This entire proposal is pure orwellian shit.
In LaTeX you can have actual boldface letters, so you should write a boldface letter R to represent the real numbers and so on.
Almost [1] every single student absolutely hates that notation in scripts. Bold is used to draw attention, it should not be abused as being part of the variable/type. Just use the proper symbol.
[1] And I'm only saying "almost" to account for the possibility of there being like 5 super weird people on this planet that think otherwise. I don't know a single person who thinks this is a good idea, even the professors writing their scripts like that think it's stupid and are only doing it due to some nonsense fear of it otherwise not printing correctly due to one single bad experience with a shitty printer in 1950. Or maybe there's some other historical reason for this, but in 2023 I'd classify not using the better notation as malicious.
I don't, I think that line length limits are typically not a good idea and thus I don't like hard limiting them. Now obviously arbitrarily long lines are no good, I'm not advocating for people to write 300+ char lines. I'm just saying that sometimes there's good reasons to (slightly!) go over the "limit", for example shortening the variable name "users" to "usrs" to make a n+1 line fit into the n char limit would be a terrible idea. And also when this topic comes up then typically people implicitly think about the 80 char limit, which is just way too restrictive and has no reason to exist anymore, it's not 1980.
The limit on what constitutes a reasonable line length is a bit subjective but I'd say that well written code rarely goes above ~120 or so. Depends a bit on the language, some just have more boilerplate than others. But instead of making that a hard limit I'd warn above that number so actual people can decide if it makes sense there or if a rewrite is in order. Auto-formatting is great and all, but ultimately a human should have the last decision.
Though if you force me to pick a value, then it's 4 because that's the sanest choice for like 95-99.9% of all people.
That's a pretty ignorant view, there's tons of developers using Windows. If you take a look at the SO survey (or similar ones), Windows has 47% in the "Professional use" category.
This has nothing to do with enterprise, it's about accessibility. For most people on the planet English isn't even the first language and now you expect them to know about obscure wannabe-cutesy internet slang? Fuck that shit, what's next? UWU.md instead of README.md?
It's not just age, plenty of people find 2 spaces hard to read. Thus the only logical choice for indentation is tabs. That way every reader can pick the size that is good for them.
Zeal works on Linux.
The ones that start with `telemetry`
I mean sure, more things being expressions instead of statements is pretty nice (e.g. in Rust you can do that). But you don't need to introduce different syntax for that.
That example is quite unfair. You could just write
println(is_me ? "me" : "you")
There are strictly more parentheses since other languages also use [] and {} (and <>) instead for different things. Or even ; or whitespace. Ignoring the majority of available brace types is just stupid if you ask me. The parentheses being at the wrong positions is something I can deal with (still no fan of RPN, but w/e), but intentionally crippling syntax that could help is just not a good idea. Syntax is your friend, use it.
Fair enough, I can see that this is something which can easily throw you off if it isn't part of your normal workflow.
Honest question, why? If you properly format your code then it's indented anyway so Python is basically just replacing `{` with `:` and then not having a `}`. Python is the least problematic of all the languages enforcing some style things. Go insisting on Google's stupid styleguide is just dumb, Lisp having the parentheses on the wrong positions and ignoring the fact that there is more than one bracket type available is dumb, all the languages with `END` blocks are dumb because `{ ... }` is much shorter and cleaner, ... . Python has its annoyances too but indentation really isn't a problem - it's there already anyway.
Copy initialization does not mean that the copy constructor is called. It is the correct term for an expression `T a = ...;`, which can often result in the copy constructor being called but does not have to. In this case it's mandatory copy elision from a prvalue, which leads to only one constructor being called.