BenMorganIO

I would start with asking the backend and front-end developers to learn Laravel and begin using it. All code review should be quite strict. It's going to suck for a while, but that's just the way of it.

Set up two nginx servers. One that's your usual to load Laravel and the other to the legacy nginx server that acts as routing to the legacy application. I would even recommend using OpenResty to help delegate if you need something intelligent.

I would strongly discourage a JS framework that would add increased complexity when you need to keep things focused. The front-end would need to be recorded in Laravel and brought back over in a clean fashion.

Set up a CI and ensure all the code that goes over to Laravel is near 100% tested. Might also be useful to set up a visual regression test tool such as Percy to ensure everything moves over nice. Push for SMACCS and BEM to keep things consistent. Or just make new styling for the new pages to surprise the users.

Rewrites are a trap though and can be painful. Keep a balance of features entering Laravel and the big foxes entering the legacy app. I would recommend RabbitMQ to communicate between them.

You sure? All the projects I've worked on have used snake case. I've only seen newcomers to programming use capitalized table names.

When to Use MySQL?

Never.

Dangerous human beings can't be trusted.

But that would make the hash braces redundant so you could just use parenthesis.

I have met a physicist at Perimeter Institute who went all the way to Engineering at Master level and pivoted to Physics PhD. If he could do that, I'm sure you can. I do not remember his name, just his face.

Except film produced with film. Godfather is supposed to look spectacular since it was film, Star Wars though needs a lot more work.

I suspect it's more for VR and 8k bump on output is cheap compared to helping Samsung and LG sell their 8k models.

That's not true. KYC is for preventing money laundering and terrorist financing. You do NOT want the RCMP/FBI asking why you permitted terrorists to use your platform.

Having read Three Roads to Quantum Gravity, I think there's a lot of substance there. It's a book made to even include high schoolers, so you have to give it some benefit of the doubt.

As per the philosophy question, neither classical mechanics, relativity, or even death cares about what we think. What matters here is how we perceive and understand a concept.

Also an android user, also interested :)

You can sort of, but you'd need your own server. Google has control over this and I'm not sure if they permit different content for each device. They probably don't.

Given the title, I expected this to be about how PG improved their counting. This is not what it was about.

I remember working over half a billion records and having problems when I needed a count. I used count(id) but that was mainly from internet mantra. I did not see an improvement. Using Citus gave me a significant improvement from 7 minutes to 1. And that was just a single coordinator, two workers on the same host. It could become much much better.

If the data is very stagnant and writes are very low the triggers are great. Usually the "close enough" with pages is good if you have over 100k since paging - please correct me if I'm wrong - is sometimes 1k off.

My preference is Citus as a catch all, but a trigger, a Redis cache managed at the app level, or using page counts are all . really useful for stickier situations.

I sincerely hope this never comes to Canada.