theginger

The comment could be more about the politics of this not the economics, Donald Trump has made it clear he is very against this sort of rate rise

Not without leaving potential proof that it happened behind

This is a really good example of how capitalism doesn't work so well in a digital economy. Normally there is are various arguments about how the subscription pays for the development / invitation. But here we have a feature that's been there for more than a decade, the only innovation is figuring how to monetize it.

There is very little rational about car buying or branding. In the eye of many consumers a car with 3 wheels and 1 with 4 from the same brand will have more in common than 2 identical cars with different badges.

What I see a lot is working with developers who believe the goal is to write software that can complete the task. They demo it, release it and watch it immediately fall apart with first contact with the user.

What they should be doing is having a goal of software that cannot fail to complete the task.

The GÖÅTSE toilet seat? For some reason their little thumbs up / down icon made me think of this.

Anyone else surprised how small the number is? It looks quite big without commas but if you add them in it looks like the sort of number that is almost conceivable 43,252,003,274,489,856,000 43 quintillion, that's the type of number i've vaguely heard of. Compared to the number of possibilities for a shuffled deck of cards 80,658,175,170,943,878,571,660,636,856,403,766,975,289,505,440,883,277,804,000,000,000,000 Thats a big number, and weirdly I think those 00s at the end are exact not a rounding error.

> based on a novel reading of the law

So they found a loop hole. Why do they need to find a loop hole in their own law, why not just make better laws to start with.

>There'd be a certain irony being able to reverse shell anyone doing an nmap scan.

Every TV / movie hacker has known about this.

Cors is hard to understand because the browser is protecting you and the server from malicious code that the developers are not expecting to be there. Its a hypothetical threat you cannot see during development unless you really go out of your way. If you can't see the threat it's hard to understand it, it you don't understand the threat it's hard to understand the protection against it.

Its one of those situations where you need to think like an attacker to see the whole picture.

What does it do better than parquet? The compression ratio quoted is lower than parquet but I expect higher to be better in this context

A lot of fast chargers are over $1 per kwh so unless you have access to home charging there isn't much room for savings.

We don't use unit of measurements. We use metrics because we have a lot more context. Rps, requests per second is a commonly used unit but it has no defined standard, you could and often do average it over time for reporting but no one says you have to. For scaling however you'll probably want to use the max not the average, because no one wants a web application where in business as usual 60% of the time it works every time.

What proportion of devices would need to meet this 80% rule? 50%? 90%? 99%? Could make a huge difference