TBurette's comments

The fact that they had a long time to transition doesn't negate the fact that they have to spend the time doing the transition.

At market-rate developer salary, it doesn't take a lot of man months for the port not to be worth the investment for small shops.

Regarding the multiple human ancestors aspect, here is an diagram of human species or groups if you want to avoid the "what is a species discussion" : https://imgur.com/a/AfrYjqF It is from a recent symposium [1] on human evolution The vertical axis is the age. The horizontal axis represent the geographical spread and the color represents the continent.

We can see multiples things:

- Disregard the 2010, it is indeed up-to-date. These past few years new bars have been added regularly.

- A single homo species is a new development and is an exception and not the rule

- Not only did different species live at the same time they sometimes lived in the same places

- There is no edges between the groups to represent ancestors as a simple "single ancestor" link is not easy to establish.

[1] https://www.college-de-france.fr/media/jean-jacques-hublin/U...

What I don't understand is why it is such a prevalent issue in the US but not in Europe.

I've had a couple of French phone numbers over the past 15 years and I can't recall a single time I got spam call (though I did get an occasional spam text message with a shady link). I know my parents occasionally get some call but it's a small handful of offenders that keep repeating the same call again and again.

I don't think it's a technical difference as you can make call using IPBX/VOIP without too much trouble here.

That's what Excel Tables are for. You get a table within your spreadsheet and instead of using cell references like =Sum(C2:C7), you can use structured reference like =SUM(DeptSales[Sales Amount])

A while ago I wrote a similar interactive article to prove that the martingale betting technique at the roulette doesn't work : [1]. The martingale is when you bet 1, double the bet each time you lose, start again at 1 when you win.

The aim was to create a single page anybody could link to that proves without a doubt the abysmal odds of making money off the roulette with the martingale technique. Instead of pre-written probabilities, charts and 'obscure complicated math' that people could easily dismiss. I wanted to give people the ability to run simulations of playing at the casino in the browser. The idea being that people would end up building the probabilities/charts themselves through simulations.

It is running Monte Carlo simulations inside the webpage and outputs the result as charts dynamically using js and D3. What it does is it repeatedly simulates going to a casino with a certain starting amount of money and an objective of how much you want to win. It then plays the roulette using the martingale technique until you got your target winnings or you lost your money.

Unfortunately I don't think I wrote the article really well and the 'generate yourself the charts proving it doesn't work' doesn't come across really well. I should have put a 'run' button instead of needing a page refresh for a start.

[1] http://thomasburette.com/martingale/

Fractional scaling in Wayland is great news.

Until now if you had linux on a high resolution touch screen computer you had to make do with a subpar experience. It doesn't matter which combination of X11/Wayland and KDE/Gnome you chose.

In X11 : touch support is bad to the point of being unusable but you can scale the UI with fractions.

In wayland : touch support is better but you can only scale per unit (100%, 200%) which makes things either way too small or way too big.

There is https://usesthis.com/categories/developer/ , where people describe the hardware/software they use.

The site was fairly popular a decade ago. I'm glad it's still up and doing new interviews.

I didn't know about the Coase Theorem. The link between property right, transaction cost and externalities is not obvious and interesting.

We could imagine many tech examples similar to the school and highway :

- An ISP provides a connection with poor delay/jitter and it creates problem for software developers (Skype, multiplayer games,...) --> should the ISP compensate the developers or the developers pay the ISP to fix the problem?

- A developer is selling created a program that degrades the performance of another program if they are both run simultaneously. Who should pay who to compensate/fix the problem?

You could say it's a 'lemon market' ( https://en.wikipedia.org/wiki/The_Market_for_Lemons ).

A lemon market is when the buyer doesn't have enough information to tell the difference between a good product (peach) and a bad one (lemon). Since the buyer can't tell the difference, the price he is willing to pay will end up somewhere between the value of the peach (more expensive) and the value of the lemon (cheaper). What happens then is that the sellers of lemons thrive while the the sellers of peaches end up leaving the market. This lowers the average price and creates a cycle where the price decreases which drive even more sellers of quality products to leave the market which lowers the price further...

I like the clean look and the overall way it is presented. The examples using angle brackets (eg.: <list>.append(<el>) ) is highly legible and the one column format is faster to scan.