Pavel Shakhov pongo

Re: people with revalidate caching issues

I'm using getStaticProps with revalidate: 60 and was expecting to only get one data fetch per minute. I just checked our server logs and saw that the requests per minutes to that endpoint is bigger than 20.

The best solution is to not even hit your application. Let a CDN serve a response that's been cached, rather than your application. Trying to share disks/Redis's to sync up application caches is the wrong path - sure you could do it but it's a bunch of unnecessary complexity. Moving your caching solution in front of your application is a far better design.

Using Vercel should (caveat: this bug) take care of all of this for you. That's what Vercel want from Next.js - for you to use Vercel hosting, Vercel is a for-profit company after all. "It's all about that developer experience".

If you're running this on your own, I suggest not running multiple instances and trying to share disk caches. By all means, use multiple instances ("High Availability") but put

http://blog.sharaal.de/2015/10/30/typescript-and-performance-monomorphic-vs-polymorphic-code.html
same order access https://stackoverflow.com/questions/51973921/which-way-of-object-instance-creation-is-the-fastest-in-typescript
--trace-ic https://benediktmeurer.de/2018/03/23/impact-of-polymorphism-on-component-based-frameworks-like-react/
в какой момент polymorphic становится megamorphic (в комиксах!) https://mrale.ph/blog/2015/01/11/whats-up-with-monomorphism.html

значения по-умолчанию в аргументах функции (включая деструктуризацию объектов) работают быстрее, чем проверка === undefined внутри функции.
для мелких часто вызываемых функций нужно требовать указания всех аргументов. (если и не из-за полиформизма, то хотя бы чтобы не тратились ресурсы на проверку указан ли параметр)
для вложенных функций не совсем понятно — надо указывать все параметры или они нормально работают с переменными или параметрами замыкания. в одних тестах такие функции тормозят, в других — нет. но если указать,

Пакеты для миграций PostgreSQL

Main

Пакет	Raw SQL	cli	cli-create	only up	migration table	transaction
knex	- +	+	+	-	+	+
[node-pg-migrate][2]	- +	+	+	-	+	+
[postgrator][3]	+	+	-	-	+	-
[@slonik/migrator][4]	+	+	+	-	+	slonik do??

If you want to reload after file changes, you can run Parcel in watch mode, which compiles changes to another directory (default ./dist/) but does not run a server.

parcel watch index.html --no-hmr

Then run a live-server, which listens to file changes and reloads (assuming your output is to the ./dist/ directory)

live-server ./dist/

Here's what my npm start script looks like:

Загружаем babel-polyfill только для старых браузеров на примере vue.js

1. Используем polyfill.io

Это сервис, который на основании юзер-агента определяет какие полифиллы нужно загружать.

Попросту в index.html добавляем:

<script src="https://cdn.polyfill.io/v2/polyfill.min.js?features=es6"></script>

	// https://stackoverflow.com/a/14551263/136559
	var start = process.hrtime();

	var elapsed_time = function(note){
	var precision = 3; // 3 decimal places
	var elapsed = process.hrtime(start)[1] / 1000000; // divide by a million to get nano to milli
	console.log(process.hrtime(start)[0] + " s, " + elapsed.toFixed(precision) + " ms - " + note); // print message + time
	start = process.hrtime(); // reset the timer
	}

	// 525,957 ops/s ±1.38%

	const length = 500,
	array = new Array(length);

	for (let i = 0; i < length; i++) {
	array[i] = i;
	}

	// 452,446 ops/s ±1.78%

	class Greeter {
	greeting: string;
	private __brand = Symbol; // private __brand!: never;
	constructor(message: string) {
	this.greeting = message;
	}
	greet() {
	return "Hello, " + this.greeting;
	}
	}

	// models
	const CREATE_ENTITY = 'CREATE_ENTITY'
	const UPDATE_ENTITY = 'UPDATE_ENTITY'

	type TEntityActionTypes = typeof CREATE_ENTITY \| typeof UPDATE_ENTITY

	type TCreateAction = {
	type: typeof CREATE_ENTITY,
	payload: string
	}