Yu Inao / 稲尾遊 japboy

グラボをNvidia Storeから個人輸入する際にハマった

結論

無事購入できました:joy:
代理店価格(日本価格)より1~2万円ほど安く購入できる
初めて購入するときは結構沼るので注意が必要
必ず在庫通知がメールに届くようにする
万が一キャンセルされたときに、早く返金が欲しいならPaypal決済かつ銀行口座からの引き落としを使え

そんなところです

2020/5/31追記: 自分用のメモに書いていたつもりだったのですが、たくさんのスターを頂けてとても嬉しいです。
と同時に、書きかけで中途半端な状態のドキュメントをご覧いただくことになっており、大変心苦しく思っています。

このドキュメントを完成させるために、今後以下のような更新を予定しています。

TODO部分を埋める
書籍を基にした理論・原則パートと、実装例パートを分割
- 現在は4層のレイヤそれぞれごとに原則の確認→実装時の課題リスト→実装例という構成ですが、同じリポジトリへの言及箇所がバラバラになってしまう問題がありました。更新後は、実装時の課題リストを全て洗い出した後にまとめて実装を確認する構成とする予定です。

2021/1/22追記:

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

Reposted from Qiita

For almost a year now, I've been using this "flux" architecture to organize my React applications and to work on other people's projects, and its popularity has grown quite a lot, to the point where it shows up on job listings for React and a lot of people get confused about what it is.

Why I'm tired of using and teaching flux

There are a billion explainations on the internet, so I'll skip explaining the parts. Instead, let's cut to the chase -- the main parts I hate about flux are the Dispatcher and the Store's own updating mechanism.

If you use a setup similar to the examples in facebook/flux, and you use flux.Dispatcher, you probably have this kind of flow:

フロントエンドを楽にするために

Qiitaを支えたい技術 at 時雨祭

About

HN: mizchi
Qiitaの方からきました(入社半年たったらしい)
Reactオジサンはそろそろ飽きてきた
Angularに興味が無いのでこっちにきた

Google Maps に大量のマーカを表示する - Too Many Markers!

Too Many Markers! - Google Maps API — Google Developers https://developers.google.com/maps/articles/toomanymarkers

のメモです。

Introduction

Some applications are required to display a large number of locations or markers. Despite the v3 JavaScript API's significant improvement to performance, naively plotting thousands of markers on a map can quickly lead to a degraded user experience. Too many markers on the map cause both visual overload and sluggish interaction with the map.

	"""
	This is an example on how to reload Flask app in runtime

	It can be useful for the use case where you want to enable/disable blueprints/routes dynamically.

	To run the app:

	> pip install flask & python app.py

	Then test it via curl

	/**
	* Lightweight script to detect whether the browser is running in Private mode.
	* @returns {Promise<boolean>}
	*
	* Live demo:
	* @see https://output.jsbin.com/tazuwif
	*
	* This snippet uses Promises. If you want to run it in old browsers, polyfill it:
	* @see https://cdn.jsdelivr.net/npm/es6-promise@4/dist/es6-promise.auto.min.js
	*

	/*!
	* Copyright 2015 Google Inc. All rights reserved.
	*
	* Licensed under the Apache License, Version 2.0 (the "License");
	* you may not use this file except in compliance with the License.
	* You may obtain a copy of the License at
	*
	* http://www.apache.org/licenses/LICENSE-2.0
	*
	* Unless required by applicable law or agreed to in writing, software

	/*
	* Steps
	* 1. Rename your gulpfile.js to gulpfile.babel.js
	* 2. Add babel to your package.json (npm install -D babel)
	* 3. Start writing ES6 in your gulpfile!
	*/

	import gulp from 'gulp'; // ES6 imports!
	import sass from 'gulp-sass';

Yu Inao / 稲尾 遊 japboy