innocenat

As other have said, the problem is that Safari is only available on Mac OS.

Say what you will about IE, at least Microsoft make an attempt to make it available to everyone (via free Windows VM preloaded with specific IE version).

It's not in master database, but there's a few on YouTube/Twitch. 99% though, it's: 1. e4 e5 2. Ke2 Ke7 3. Ke1 Ke8 and then just become non-castling chess.

It's probably not downvoted because it's wrong, but it's because it doesn't help anyone who don't have "simple technical understanding of how distributed caching works."

And what if you want to display Japanese and Korean at the same time?

What about datetime, random, system, etc?

How is it different? Why do you draw the line at I/O function?

Do you also expect `sqrt(a)` to be `call sqrt` and not `sqrtss xmm0`?

Caching plugin for wordpress still has benefit that nginx cannot provide like providing object caching, etc.

    dist.js: $(wildcard *.js)
        cat $? > dist.js

Like this?

> If the science isn't finding an effect, they are either not measuring the right thing or they are not measuring it with a large enough sample size.

This is a very dangerous idea to have. Placebo is a very well known effect.

I think most C++ implementation of bogosort use std::next_permutation

The registrar service has been here for some times, but previously you need to transfer domain in instead of register new domain.

I am not actually familiar with Tohoku/Joetsu Shinkansen (living in Osaka), but I can tell you that for Tokaido Shinkansen, dwell time is still very much a problem even with parallel platform. For Tokaido Shinkansen, while the door only open for a minute or so, by the time we are leaving a station, the next train (running 3-4 min behind) is already pretty much pulling into the station.

Previously Tokaido Shinkansen only can only runs 14 train per hour (note that unlike Tohoku/Joetsu, Tokaido Shinkansen runs 14 tph over 350km of tracks, and not all trains has same stops), but after some optimization, including a procedure to reduce dwell time by a few seconds, they were able to push that to 16 tph.

> But that might apply to metro and regional rail more than long distance, so it might not be relevant here.

Shinkansen at peak time runs more frequently than even some subways line in Japan. The Tokyo-Omiya section (shared between Tohoku/Joetsu/Hokuriki Shinkansen, which E4 also ran on) runs at peak of 15 trains per hour per direction, or 4 minute heading. (The Tokaido Shinkansen is even more impressive at peak of 16 trains per hour per direction.) The loading time is very, very relevant, and it's why E4 has been phrasing out for a long time already.

I immediately realised what must have happened and was scrolling down trying to find this news lol.

I meant that trying for a few tab with one site won't help me, because previously it's dead AFTER I migrated my entire 200+ tab session.

I said I did twice? Both of them f*cked me up completely.

Not going to help when my session is 200+ tabs. Previously it's dead after moving my main session.

As I said, I was bitten twice. It's hard to even try now. Back then I try for a few week before committing, but when I move my session (of 200+ tabs) onto Firefox, it's dead.

And back then I was told the exact same thing I was told this time, too.

I have attempted to move to Firefox twice: once 12 years ago and once 8 years ago (probably, I don't really remember exact time). I know, Firefox has come a long, long, long way since then, but the same were also promised 8 years ago, and it turn out Firefox cannot handle my use case well to the point of almost being unusable. (That said, my use case are definitely not normal)

It's a lot of effort to move everything: current session, bookmarks, extensions, sync (which mean I need to move on my 5+ devices at once). I have been bitten twice -- not sure if I want to risk it again. No matter how much people are saying how good it is now, it's hard to muster up the effort to move again.

EDIT: Perhaps I wasn't clear enough. Back when Firefox was saying it's as fast as Chrome without being multi-process. They were saying that it's better. I tried. I moved. I got f*cked up. I move back. Twice. You'd excuse me if I no longer believe what the Firefox dev were saying about their browser.

I agree wholeheartedly that php-fpm rapidly speed up nginx adoption.

Before nginx, lighttpd was a thing. It also comes with `spawn-fcgi` to handle fastcgi, but it's a little complex to set up. Back then people were also using `spawn-fcgi` with nginx, too. I remembered reading some tutorial and decided that I will continue to use Apache with mod_php due to complexity. When php-fpm come, I immediately switched.

So putting these config in .htaccess which live in project folder is a technical debt, but putting all these logics in nginx master config file is not?

From a hygenic point of view, yes, it's a serious question.

You wear watch while cooking?

Vista SP1 was fine. Vista before that wasn't, really.

Discourse is open source: https://github.com/discourse/discourse

The plans shown on the pricing page are managed plan. You can install it on your server without problem.

I thought almost all laptop before 2010 is like this though. It was normal back in the day.

Currently it's ~86% according to caniuse.com. I think it's still a bit low to be used comfortably.

> It's been simple and predictable and easily learned for decades, calling it "borderline unusable" is just hyperbole.

And it's also completely not discoverable. I only know how it works when I read from HTML book back in the day.

Just because it was the standard doesn't mean it's easily learned.

This just don't make sense. People do scripting in sh, bash, python, etc all the time. Why not js?