Look at the following image...
...it shows an object being tested.
You can't see inside the object. All you can do is send it messages. This is an important point to make because we should be "testing the interface, and NOT the implementation" - doing so will allow us to change the implementation without causing our tests to break.
| 1) Clone and build WebKit | |
| git clone https://github.com/WebKit/WebKit.git WebKit | |
| cd WebKit | |
| Tools/Scripts/build-webkit -cmakeargs="-DENABLE_WEBGPU_BY_DEFAULT=1" --debug | |
| 2) Run your app | |
| __XPC_METAL_CAPTURE_ENABLED=1 Tools/Scripts/run-minibrowser --debug --url http://localhost:5000/index.html#/loaders/gsplat |
| @echo off | |
| title Activate Microsoft Office 2019 ! | |
| cls | |
| echo ============================================================================ | |
| echo #Project: Activating Microsoft software products | |
| echo ============================================================================ | |
| echo. | |
| echo #Supported products: | |
| echo - Microsoft Office Standard 2019 | |
| echo - Microsoft Office Professional Plus 2019 |
These are NOT product / license keys that are valid for Windows activation.
These keys only select the edition of Windows to install during setup, but they do not activate or license the installation.
A guide how to get and activate Windows 8, 8.1, 10 and 11 Pro for free!
If you see the Windows keyboard button 
| Given the following text: | |
| {browser-tab} | |
| Please provide a summary of the writing post [title/link] in approximately 300-500 words. | |
| The summary should cover the following: | |
| 1. Main topic/subject of the blog post. | |
| 2. Key points and important context discussed in the post. | |
| 3. Significant takeaways, insights, or conclusions drawn by the author. | |
| 4. Any relevant data, statistics, or examples cited to support the main arguments. | |
| 5. The conclusion, nuance or importance of newly introduced concepts or conclusions arrived upon by the author. The summary should be well-structured, concise, and written in a clear and objective style. Please avoid verbatim quotes from the original text unless they are particularly impactful or necessary for context. The goal is to capture the essence of the blog post in a way that someone who hasn't read it can quickly understand the key ideas and arguments presented. |
| #!/usr/bin/env zsh | |
| #=========================================================================== | |
| # * INFO | |
| # | |
| # macOS Preferences Defaults | |
| # By Christopher Allen @ChristopherA https://github.com/christophera/ | |
| # My most basic macOS preferences, in this gist to make it easy to load on | |
| # multiple machines and VMs. Ideally runs on all macOS versions since Yosemite, |
| #!/usr/bin/env bash | |
| # TODO: Need to figure out the settings for the following: | |
| # 1) Dock: Items with order (not capturing binary data - since that is dependent on installed apps) | |
| # 2) Security & Privacy Preferences: Full Disk Access, Camera, Microphone | |
| # 3) Login items for my user (i.e. apps started when I login) | |
| # 4) Retina displays scaling | |
| # 5) Finder sidebar with order | |
| ## |
| /** | |
| * 1Password Duplicate Remover | |
| * | |
| * Usage: node 1password-duplicate.js | |
| * | |
| * Author: Will Hackett | |
| * | |
| * License: MIT | |
| * | |
| * Requirements: |
