VMWare Fusion 13 is now released. Read Vagrant and VMWare Fusion 13 Player on Apple M1 Pro for the latest.
This document summarizes notes taken while to make the VMWare Tech preview work on Apple M1 Pro, it originated
VMWare Fusion 13 is now released. Read Vagrant and VMWare Fusion 13 Player on Apple M1 Pro for the latest.
This document summarizes notes taken while to make the VMWare Tech preview work on Apple M1 Pro, it originated
A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.
Nowadays lots of companies choose engines like Unreal or Unity for their games (or that's what lot of people think) because d
<?php | |
/** | |
* PHP var_dump() without newline after => . | |
* | |
* NOTE: The only issue is when a string value has `=>\n[ ]+`, it will get converted to `=> ` | |
* @link https://www.php.net/manual/en/function.var-dump.php | |
*/ | |
function vardump($value, $return=FALSE) { | |
ob_start(); | |
var_dump($value); |
This week NN Group released a video by Jakob Nielsen in which he attempts to help designers deal with the problem of customers being resistant to their new site/product redesign. The argument goes thusly:
There's slightly more to it than that, he caveats his argument with requiring you to have of course followed their best practices on product design, and allows for a period of customers being able to elect to continue to use the old site, although he says this is obviously only a temporary solution as you don't want to support both.
These set of scripts are for Magento 2. For Magento 1, see this Gist.
In your command-line run the following commands:
brew doctor
brew update
<?php | |
class Picture { | |
public function init_remove_hwstring() { | |
add_filter('image_downsize', array($this, 'remove_hw_from_downsize'), 10, 3); | |
add_filter('wp_get_attachment_image_attributes', array($this, 'add_srcset_sizes'), 10, 3); | |
} | |
public function add_srcset_sizes($attrs, $attachment, $size) { |
The best way to safely and securely use local domains pointing to 127.0.0.1 is to edit your local settings (/etc/hosts) and add your own settings. Keep in mind if you want to use subdomains, you need to enter all variations.
Example:
# Adding bottom of your current file /etc/hosts
################# MY LOCAL DOMAINS
127.0.0.1 local.com admin.local.com
127.0.0.1 domain1.com
# ignore everything in the root except the "wp-content" directory. | |
/* | |
!wp-content/ | |
# ignore everything in the "wp-content" directory, except the themes directories | |
wp-content/* | |
!wp-content/themes/ | |
# ignore all mu-plugins, plugins, and themes | |
# unless explicitly whitelisted at the end of this file |