duyet duyet

This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.

In that post I talked about 3 main reasons for moving from require.js to webpack:

Common JS support
NPM support
a healthy loader/plugin ecosystem.

Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.

Guide

Note The extension Imagick is now included in Ondrej's PPA. All you need to do now is $ sudo apt-get install php-imagick, and you're done. I'll keep the guide here because a lot of it is still true for other extensions

======

I've installed PHP7 via Ondrej's PPA. He maintains these PPA's on his free time, consider donating

Install dependencies

*2vec papers

act2vec, trace2vec, log2vec, model2vec https://link.springer.com/chapter/10.1007/978-3-319-98648-7_18
apk2vec https://arxiv.org/abs/1809.05693
app2vec http://paul.rutgers.edu/~qma/research/ma_app2vec.pdf
ast2vec https://arxiv.org/abs/2103.11614
attribute2vec https://arxiv.org/abs/2004.01375
author2vec http://dl.acm.org/citation.cfm?id=2889382
baller2vec https://arxiv.org/abs/2102.03291
bb2vec https://arxiv.org/abs/1809.09621

(This is a translation of the original article in Japanese by moratorium08.)

(UPDATE (22/3/2019): Added some corrections provided by the original author.)

Writing your own OS to run on a handmade CPU is a pretty ambitious project, but I've managed to get it working pretty well so I'm going to write some notes about how I did it.

58 bytes of CSS to look great nearly everywhere

When making this website, i wanted a simple, reasonable way to make it look good on most displays. Not counting any minimization techniques, the following 58 bytes worked well for me:

main {
  max-width: 38rem;
  padding: 2rem;
  margin: auto;
}

SQL language proposal: JOIN FOREIGN

The idea is to improve the SQL language, specifically the join syntax, for the special but common case when joining on foreign key columns.

The problem

Example below taken from PostgreSQL documentation [1]

In SQL-89, we didn't have any JOIN syntax yet, so queries were written in this way:

	consumer_key = 'your-consumer-key'
	consumer_secret = 'your-consumer-secret'
	access_token = 'your-access-token'
	access_secret = 'your-access-secret'

	import os
	import unittest

	from airflow.models import DagBag

	class TestDags(unittest.TestCase):
	"""
	Generic tests that all DAGs in the repository should be able to pass.
	"""

	import boto3
	import botocore
	import datetime
	import progressbar
	import itertools

	# from https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html
	STORAGE_TYPES = [
	"StandardStorage",
	"IntelligentTieringStorage",

	<style>
	.git-graph {
	text-align: left;
	line-height: 1;
	}
	.git-graph-row {
	clear: both;
	text-align: left;
	}
	.git-graph-cell {