Except of course working-class Dublin, where its "yous" or "yis"
And I've heard "yousuns" in the North
2,335 karma · joined January 8, 2022
And I've heard "yousuns" in the North
"you" is most frequently used in direct address, a context where it is frequently necessary to distinguish between addressing an individual in a group or the group as a whole
However, using the word "history" in a way different to historians is not going to uncover any blind spots.
https://www.researchgate.net/publication/344644569_Definitio...
Yes, the dividing lines are blurry.
No, it is not totally subjective
nope
The person you were replying to was asking about cities. The article you are posting is about Sedentism - "the practice of living in one place for a long time". The figure of 25,000 years ago is for the first evidence of permanent settlements. These do not fit anyone's definition of a city.
The first evidence of cities are from Sumer, which is what this whole thread is about.
no one said that
but there is a definitional issue here - to reiterate the previous poster's point:
> Historians use “history” as a technical term for events recorded in written and other durable records.
That's how the word is defined by historians. It's not a value judgement on oral traditions.
Your post is using the word "history" in a different way. You have some good points to make, but as long as you're using "history" in a different way to everyone else you're not going to get very far in conversation.
Apple's corporate structure in Ireland is designed around leveraging tax law to its advantage.
It's unclear how much the former depends on the latter.
The reality was a lot less glorious than that. And with a lot of less than glorious moral compromises and cognitive dissonance. Again, I refer you to the founding fathers.
> Yet in modern times we only hear about a particular angle that pushes blame solely on the very cultures and nations that forcefully ended slavery
We don't only hear that angle, it's trivially easy to access balanced and detailed history. Maybe you're spending your time arguing with zealots on social media but the rest of us can actually educate ourselves
> blame solely on the very cultures and nations that forcefully ended slavery
In fairness those societies were also responsible in the first place for the expansion of slavery into an unprecedentedly vast system
Can we just accept that, and not feel so defensive?
Not sure who is blaming the West for slavery, but whatever.
The West did set the norm that slavery is unacceptable, but only after embracing slavery on a vast scale for centuries, overlapping to a great degree with the Enlightment and with the birth of representative democracy. I think that is the underlying dissonance - the founding fathers expounded at length on equality, liberty from arbitrary rule and so on, while the South prospered on the back of slavery. A similar criticism could be made of French revolutionaries, and British liberals of the 17th/early 18th centuries.
Junior developers will write suboptimal code in any language. So I'm not sure what your point is.
They are so different in DX, ergonomics, implementation and traceability that I'm not sure this is true other than in the most abstract sense
> any open source project should consider docker not an option to solve their problem
That's generalising far too much.
You're working with some seriously hairy technologies, dealing with very knotty compatibility issues, and you don't want to learn... Docker?
I find this odd because it's relatively simple (certainly much simpler that a lot of what you're currently dealing with), well documented, has a very small, simple syntax and would probably solve your problems with much less effort than setting up a third development machine.
You sure about that? Not what I would have expected. Source?
If you're going to quote Knuth you better be damn sure you've fully understood him.
The quote in question is about micro-optimisations which were pointless on account of design issues. The situation you are commenting on is kind of the opposite.
I really don't think this dramatic language is helping
But maybe I'm missing something here. Do you know of an async runtime and a threaded runtime that do not have significant differences?
you're using a definition of "thread" that is quite abstract and not at all what is generally meant by most people when discussing these things
> multiple lightweight threads map on an heavier weight thread like in Node
describing Node as implementing M:N threading, while correct in an abstract sense, is not really useful or again, how most people would describe it.
> A specialized async/await runtime is a bit different from the typical M:N runtime... but conceptually there isn't much difference.
sure, conceptually, but again, you're using definitions in a very idiosyncratic and abstract manner. Which is your right, but it's not very persuasive and it's out of touch with how most people talk about these things.
This is not correct.
Async is orthogonal to multithreading. The async runtime's threading model is an implementation detail. e.g. Node is single threaded. In Rust the Tokio async runtime has a configurable threading model.
The article is mostly focused on Dart and C# - maybe you're referring to one of those specific implementations
woah
You're not doing yourself any favors.