Heres the blog post about the change dated in June this year
Half year too late for that outrage anyway :)
Heres the blog post about the change dated in June this year
Half year too late for that outrage anyway :)
Fantastic way to start a shitstorm. You people don't even use search function logged out, because if you did, you would know they changed it in 2016. Microsoft has nothing to do with it.
Yeah, fuck Microsoft. They haven’t changed at all.
GitHub changed that a few months before acquisitions talks even started lol
There already is µblock that's only MV3 based https://addons.mozilla.org/en-US/firefox/addon/ublock-origin-lite/ give it a try if you see any difference
You're telling me about compiling JS, to my story that is so old... I had to check. and yes, JS existed back then. HTTP2? Wasn't even planned. This was still when IRC communities weren't sure if LAMP is Perl or PHP because both were equally popular ;)
you are supposed to have written the tests and to have written your code with pair programming,
I commented out the tests because they were failing, pipelines were green so I merged. Now it's running on prod. What do you do?
Blog content was stored in memory and it was served with zero-copy to the socket, so yea, it's way faster. It was before times of php-fpm and opcache that we're using now. Back then things were deployed and communicated using tcp sockets (tcp to rails, django or php) or reading from a disk, when the best HDDs were 5600rpm, but rare to find on shared hosting.
Before nginx was a thing, I worked with a guy who forked apache httpd and wrote this blog in C, like, literally embedded html and css inside the server, so when he made a tpyo or was adding another post he had to recompile the source code. The performance was out of this world.
You live like this?
:00
- :ff
Edit: Just learnt this can be also noted as:
::
- ::f
It compiles = it goes to prod!
I don't agree that it's useless or misguiding. The smaller dataset, the less important it is, but it makes massive difference how the rest of the algorithm will be working and changing context around it.
Let's say that you need to sort 64 ints, in a code that starts our operating system. You need to sort it once per boot, and you boot less frequently than once per day, in fact you know instances of the OS that have 14 years of uptime, so it doesn't matter at all right? Welp. Now your OS is used by a big cloud provider and they use that code to boot the kernel 13 billions times per day. The context changed, time passed by, your silly bubble sort that doesn't matter on small numbers is still there.