HN user

mutatio

382 karma
Posts1
Comments168
View on HN
Eels are fish 11 months ago

I think it's not about diversity, but lineage. The phenotype for "fish" is so tight and well defined; a salmon is closer related to a human in the tree of life than to a coelacanth even though both are categorised as "fish".

Crab mentality, the closer proximity to your profession / place in society the more resentment/envy. This is a win for some of us in tech, it's just not us, so we cannot allow it! Article even mentions the age of "24" as if someone of that age is inherently undeserving.

Make no mistake, this display was a disgrace, but... after the annexation of Crimea the EU (Germany) moved ahead with Nord Stream 2, we are culpable too, massively. Ironically there's a famous video of none other than Trump lambasting the Germans about it.

I've worked on such a platform: Hyperledger from IBM et al. It was generic enough we could deploy our own "smart contract" / business logic layer via a Lisp dialect built in Go.

Likely because some core components of health care cannot be comoditised via technology, there's still vast human involvement from diagnosis to surgery, all the way to social support of the aged. Everything is getting stretched at the edges by aging populations in most of the developed world meaning medical and technological advances don't even touch the sides.

I'm in the UK (NHS), I don't see a bright future for systems like the NHS or mostly private systems like the US. There's an extreme core cost which "systems" cannot make disappear.

Ireland having tax sovereignty was doing what it felt was best for itself, the low tax ecosystem it has fostered is in its benefit. Much like car and farming tax incentives favour Germany and France respectively.

Now perhaps the EU as a entity is moving towards collective taxation policies, but it's not there yet and there's still an aspect of getting away with certain fiscal policies depending on any member nations "clout". Perhaps Ireland is mostly guilty of not having said clout.

Isn't the actual idea that any given individual has more genetic points of difference to any other random individual, even within a racial group, than genetic differences between races. So I don't understand the assertion that the idea that there aren't some foundational genetic correlations tied to race - there are. I'd be intrigued to get a measure of genetic distance between individual chimpanzees vs. humans to see if the standard deviation shows a similar pattern, of sexual selection selecting for diversity between individuals.

But it's a one time event. What comes next and what if there are negative externalities?

It feels like a land grab, the real failure here is a lack of construction, and that isn't the fault of people renting via Airbnb.

Is shared memory access naturally async like IO/io_uring? If not, asking for async is misplaced and any implementation would be synonymous with wrapping sync calls in `async fn` wrappers.

My preference is common nouns, generally it's the most concise and precise naming, I understand the issue in Go however, so the argument carries weight. What I would say is redundant verbosity is a fair halfway house.

Namespacing in languages such as Rust (modules) are probably most favourable to me, i.e. f64::min/max ~ u64::min/max or a hypothetical crypto::rand() math::rand().

My provocative take of your thought experiment is that there might be social strife from the fallout, from the mass bricked devices and effects on communications. This in itself implies anti-monopoly investigation is warranted, I'd also argue it's a failure of government to allow it to get this far in the first place. That is to say the government itself should be interrogated as to why this took so long, I don't like how the gov is cheered in these circumstances whilst allowing it to get to this.

I don't think consumer choice is an argument for the allowance of these walled gardens because it's mostly an illusion of choice, that's what these corporations are experts at, and this applies to the Android ecosystem too.

I say all this as a Adam Smith fanboy and general fan of free market economics.

I'd honestly class that as reductio ad absurdum, quantum mechanics dictates it is a probability my car might spontaneous become a pink elephant.

I'm all for evidence showing the latency shown on the video is comparable to competing implementations, but I'm not interested in lazy arguments that all momentum is eventually consistent as a defence.

Occupancy rate for commercial property is mostly over 90% in London, and I believe the residential market is even more efficient. How would LTV help if occupancy is so high? Don't forget occupancy rate also highlights slack in the market allowing for the dynamism you need, if you punish that I suspect the unintended consequences would be less desirable than any tax proceeds, after all, all forms of rent control invariably disadvantage the renter the most - and I don't see this being any different - the market would absorb the risk and rental prices would likely increase.

Satirical post I assume?

The demo shows the person stearing couldn't apply urgency in directing the wheel, sounds dangerous. Onus should be on the driver being capable of making the steering angle appropriate for the conditions, defending eventually consistent steering is comical, now drivers must account for where and by what speed the wheel angle reaches the desired position?

I wonder what the reality is regarding Pixel's success; they lost me as a customer this year after it turns out the "free" Pixel 2 watch is mostly a paper weight because Fitbit and its new unified Google account requirement doesn't support Workspace custom domains. I pay for Workspaces, I paid for the device(s), but the penny has finally dropped in regards to their real motivations, they can't allow Workspaces to mingle with the private data regular accounts give them access to when it comes to Fitbit. Hopefully this will finally give me the motivation to wean off Google completely.

I understand that, my point solely rest around defining the clone function from the slices package in the article, explaining why, yet the actual implementation is different. The source code I found via the docs doesn't consider capacity, it merely uses a empty construct and appends.

I'm not sure I'm following the preamble about the nuances of a slice with a zero capacity allocating a new backing array, given the fact that if I follow the link to the docs and then to the source, the implementation is exactly how I would have expected it to be done: append(S([]E{}), s...) - which of course is different and would make the preamble redundant.