phpnode

I'm still surprised that Reddit avoided a major scandal over the Ghislaine Maxwell situation. It's clear that they have serious ethical/integrity issues yet have avoided the kind of criticism that FB and Twitter get, despite arguably wielding more power. I wonder if this is partly because a lot of the community call themselves "redditors" and therefore interpret criticism of the platform as a criticism of the community. No one would call themselves a twitterer or a facebooker

As a user? sure.

People who create and curate content quite often want to be paid for their work, they create businesses to support themselves, often in the form of a website. If Google scrapes and repackages that content, so the searcher never even visits the creator's site, what incentive does the creator have to continue making content freely available?

This is an example where the quote is actually worse with the broader context.

Team is maybe a bit of a generous term to describe dang!

The US Air Force ran a war game. While the war game was in progress the Chinese Military ran a war game of their own, simulating a series of attacks on Taiwan. The timing appears to be unrelated, I suppose the article mentions them to draw attention to the escalating tensions in the area.

All it takes is for the US and EU to ban cryptocurrency itself and the problem goes away. It doesn't matter if mining is done in countries beyond their borders because the demand will go through the floor and those countries will have no incentive to keep wasting energy on it.

The idea that cryptocurrency is beyond government control is fundamentally wrong. Most people don't want to be criminals.

The problem with making this bet is that the value of the underlying crypto can move by far more than the possible 15% return while the result is pending.

2 months is more than enough for the price to double or halve and people want to be able to exit to fiat at a moment's notice when they think things are heading south.

The V8 team experimented with "Strong Mode" which was approximately this - a fast subset of JS [0]. The experiment was ended [1]

[0] https://docs.google.com/document/d/1Qk0qC4s_XNCLemj42FqfsRLp...

[1] https://groups.google.com/g/strengthen-js/c/ojj3TDxbHpQ/m/5E...

it's not named after it, it's just amazon is so massive they have to reuse brand names. AWS has exhausted not only the supply of IPv4 addresses but also the supply of 3 letter initialisms.

I'm wondering how many people are working on Sea Shanty Tech right now

it's not "unlearning" anyway, it's just "learning". I'm trying to imagine how many other things this person would have had to "unlearn" in tech since BBC Basic came out.

My very first interaction with a computer was with the BBC Basic command prompt, 30 years ago when I was 7. If it hadn't been so accessible I doubt I'd be a programmer now, so I feel like I owe it a lot!

Just the media

in addition to counting dependents you can also run the graph through pagerank to find the most impactful files to convert first. This strategy is useful when converting codebases from JS to TS too because it's common to incorrectly type a file when it has a bunch of untyped dependencies, so getting the translation order right saves a lot of rework.

I'm saying that's a different argument, and not one I raised.

You incorrectly inferred my meaning from my original post and are now doubling down, I'm not sure why.

It's as simple as this: We want to produce as much food as possible from as few natural resources as possible, emitting as little carbon as possible in the process. Large fields are more efficient at this, for reasons I've spelt out already.

Even in a fully communist society this would be true.

I'm talking about the process of turning sunlight into food. If you want to make that process use as few resources as possible (especially fossil fuels) then you need big fields with large machinery. Distribution of wealth is a different topic.

No, I mean it's less efficient. A large field can be farmed with larger machinery which is more fuel, time (and yes, cost) efficient than smaller machinery. There is less time spent moving between fields which can be critical for something as weather sensitive as harvest. Large machinery typically produces bigger gaps between tramlines and reduces spillage when turning, leading to greater yields and less waste.

It's not just that, certain pieces of equipment (combines in particular) are needed at the exact same time in multiple different places, and a delay of a day or even a few hours can be ruinous (if you don't harvest wheat at exactly the right time it can be more or less destroyed by the weather)

Definitely, but smaller fields are a lot less efficient unfortunately.

Why did you feel the need to edit your post to include those examples?

> There is no way the first group to land there will be able to establish dominance over the whole planet in one go.

Every potential adversary is approaching from the same direction and you have weeks / months of warning before they arrive. If you have the resources to establish a colony on another planet then defending your stake is relatively trivial in comparison. Also your team are already experts at the rocketry required to implement such a defence.

Wind turbines can be incredibly dangerous, I'd be worried if this was anywhere near my home. jacquesm wrote up his experiences making a wind turbine from scratch here: https://jacquesmattheij.com/how-to-build-a-windmill/

> I'd say there should be an exception for ransomeware cases where physical safety is being threatened.

doesn't that incentivise attacks on critical services/systems?

They set up the incentive structure, they're responsible for the effects

If everything is political then nothing is political and the term loses all meaning

all of the functionality happens at compile time

A while ago I built this exact mechanism for Flow, it could be done in TypeScript if there was enough demand for it (it's rather a large effort) https://gajus.github.io/flow-runtime/

there's the reflect-metadata package but the type information it exposes is very limited, "object" instead of {a: "foo"} and so on.

I wrote an article about this a while ago: https://codemix.com/opaque-types-in-javascript

I don't think even ReScript can do this (yet?)