if baby is 100% US citizen then how is that an 'illegal immigrant'? Again, you may call them 'unwanted', and you have right to such opinion. But law is what is written, if they got citizenship then they aren't illegal
People who abuse birthright citizenships are, by definitions, not illegal immigrants. But even if you count all of them as 'unwanted' immigrants - how many % of total immigration to the US is result of those birthright laws?
core (as in kernel) is running linux kernel which is C, yes.
But java is not 'just UI' - majority of user space apps run java (or jvm, to be precise), as well as tons of system services, to the point where you can't actually do a lot of android API calls from native code, because a lot of logic is written in java(or kotlin) code, and not just java being wrapper around native code.
Not to mention him saying no one writes java anymore when it literally powers world's most popular OS (android) and double digit percentage of internet backends
In the end, it’s the people who fight that determine if the thing they are fighting for is worth their lives.
Dying for some lines on the map sounds bad, but if it were only lines on the map, then the people probably wouldn't choose to die for them, would they?
Nobody wants to die, but if someone is ready to give up their life for some cause, then who are you to tell them they can't?
It's the fate of Ukrainians that is at stake and its the Ukrainians that determine if changing that fate is worth the costs of their lives.
What makes You claim that game like this can't be made in Unity?
Cause honestly this sound like the typical "Unity bad, UE with their flashy trailers good".
But maybe You actually do have a valid reasoning, please share it then
Delete the file from (past) commits? Isn't the whole point (idiomatic way) that you don't do that, and only delete it in the newest commit?
Unless you mean some intentionally weird scenario, where you want to just delete the file to prevent it from being accessible period.
But that's (afaik) against the whole concept of git, and so verry much outside the intended use.
Sure, 'good' and 'bad' are inherently (too) simplistic descriptions.
But imo, if we take the context in which J. Blow calls himself (and user of his language) "good" programmers in good faith, then it would be natural to call those fresh googlers 'bad' (again, in the same context of meaning for 'good' and 'bad').
Not because they are inherently worse people and aren't talented - but simply because the reason you state yourself - they just don't have the experience to tread the fine line of using a super powerful language "properly" (YET).
Dunno about runtime performance, but compiling speed is something that's regularly mentioned as an important aspect of Jai and I think it's not an exaggeration to name it as one of the fastest languages when it comes down to comp speed.
GO was named a language for bad (not experienced) programmers by its creator.
I don't see why doing the reverse of that automatically egregious
I mean sure, people are in general hesitant when someone calls himself good, and for a decent reason.
But pushing it to extreme and defaulting to reverse JUST BECAUSE someone dared to call himself good is also a pretty childish reaction.
At the end of the day it is a fact that there are differences in skill between programmers and different languages expect from you different levels of understanding. Pretending it's only valid to acknowledge these differences in others but not in oneself is irrational.