3,219 karma · joined February 7, 2015
It doesn't matter if anyone is being sued or in what quantity. Most types of incidental recordings have been declared copyright infringement in some capacity or another, and everything else is selective enforcement.
Mobile OSes got to rethink everything in an era of constant adversarial connectivity and started off on a better foot in this regard.
Do you see the term "Asian" as having the same weirdness? It's even more geographically & ethnically overbroad than the word it replaced, as well as compared to 'white/european/caucasian'.
To my recollection, a big part of the reason the former term was shunned is because it verbally homogenized distinct ethnicities from south-east asia that would prefer to identify distinctly... only to now double down in literally including the entirety of the largest continent in the world! (which I guess just returns to the more historical use of the former term, but whatever) :)
I understand the intended implication, but the vernacular is pendulum swinging too far in the wrong way factually against CO2.
Nitpicky, but hey this is HN, and I can be unpopular at this party, too! :-P
The particular form of authoritarian scaremongering on display tries to undefine that court-testable line to include any useful moral panic, but never really addresses the notion that loosening that line means their own speech could also easily be suppressed, as the "other side" could use the new suppression tools as freely and subjectively as themselves.
Plus, one could easily distinguish between the terms "establishment"/"hierarchical structures" as entrenched leadership focused on power dynamics rather than the science itself, versus "community" which is involved in the science.
SNES programming also directly introduces people into the notion of 2d vectors advancing over an original axis, which ends up in a rotation in mode 7 stuff.
The actual full name doesn't matter that much, and it can still be called "Odin" as shorthand in the docs, but this way the full name can still have both the implications you want and uniqueness. Plus, adding "Flow" now makes it a tiny bit more self-describing than just a proper name.
It can be seen as an issue of intent. By posting something, that datum might be there for personal use, and is not intended for further commercial use, especially by companies outside the one hosting the information originally.
The act of data aggregation is one that I personally think should be heavily considered for regulation, especially since it can de-anonymize people. This in my opinion is a privacy invasion, performing extra actions to access additional private data when no access to the more private details was granted, and those details did not exist publicly in an accessible way. Especially at scale and yielding personally targetable results, this isn't something we want organizations or governments to use against people unchecked.
I've used Lego stuff on the job for prototypes and experiments as well. They're overall really good and handy, but some simple mechanical tasks can get really messy or rattly.
There's 3 different models that happen:
1. Type in the entire thing
2. Type in a unique portion and ask it to autocomplete
3. On each keystroke, evaluate if the list of auto-popped-up completions to see if the one you want is quickly available yet.
Clearly the 3rd is slowest to interact with, and does not convey useful information for familiar interfaces.
If you do not know or cannot remember what the interface looks like, it might be a bit more useful, but gives you similar information as the 2nd above when you have little to autocomplete. But the 2nd option still leaves you in control of the coding flow instead of the system constantly interrupting you to ask you if it knows what you mean yet.
This very day in the USA, computers are deciding whether prisoners are eligible for parole, and the biggest statistical determiner burdening them is their skin color. That goes completely against the morals of a country holding notions of free, equal citizens and due process.
Threads' contexts should be independent from each other. If reading your stack trace relies on the state of other threads, you've got a very brittle design.
What is lost is the history of the state the current thread is working with, but the state should be fully encapsulated within the thread, except in the case of large shared read-only input buffers that are being processed in parallel. But those latter buffers aren't hidden from the current thread nor its debugging. Debug information can also be logged on state objects to show its provenance.
Things like environmental concerns also act against raw economic progress, but are necessary for a healthy society as well.
This video is historical fact, the most direct record of an important terrible event that had wide-ranging effect and became global news. Its accessibility helps squash rumors about what people think happened or didn't happen. Combined with the manifesto, it also shows why it happened.