Official redirects (still up-to-date):
https://aka.ms/vs/16/release/vs_community.exe
https://aka.ms/vs/16/release/vs_professional.exe
https://aka.ms/vs/16/release/vs_enterprise.exe
| #!/bin/env python3 | |
| # This has a lot of problems, e.g. I should have used os.path.join() | |
| # and as such this has only been used in my own little WSL world. | |
| # replace steam_libraries, ssdir, and extractdir with your values. Probably could just run | |
| # with steam_libraries as empty and then the script would just pull everything from store.steampowered.com | |
| # instead of locally | |
| # this was just a quick hack because I wanted to backup my screenshots in a format that wasa little more readable. |
| Adding a new file to see changes in revision ! |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Terminator by Aéza</title> | |
| <style> | |
| html, body { | |
| margin: 0; | |
| height: 100%; |
| 即時分享程式碼、筆記和程式片段 |
Minimal D3D11 reference implementation: An uncluttered Direct3D 11 setup + basic rendering primer and API familiarizer. Complete, runnable Windows application contained in a single function and laid out in a linear, step-by-step fashion that should be easy to follow from the code alone. ~200 LOC. No modern C++, OOP or (other) obscuring cruft. View on YouTube
| In search engine optimization (SEO) terminology, black hat SEO refers to the use of aggressive SEO strategies, techniques and tactics that focus only on search engines and not a human audience, and usually does not obey search engines guidelines. | |
| Some examples of black hat SEO techniques include keyword stuffing, invisible text, doorway pages, adding unrelated keywords to the page content or page swapping (changing the webpage entirely after it has been ranked by search engines). |
| From 598bc565905de1de2146e781013882bc9577ff21 Mon Sep 17 00:00:00 2001 | |
| From: =?UTF-8?q?Joan=20Bruguera=20Mic=C3=B3?= <[email protected]> | |
| Date: Sun, 3 Aug 2025 19:43:40 +0000 | |
| Subject: [PATCH] Updates headers for glibc-2.42 | |
| Match the extern definitions in cuda-crt headers with the changes in glibc-2.42. | |
| /usr/include/bits/mathcalls.h(206): error: exception specification is | |
| incompatible with that of previous function "rsqrt" | |
| /opt/cuda-10.2/include/crt/math_functions.h(684): here |
What you do with this information is your own responsibility. If you brick your TV trying this, it's not my fault. You should probably have some electronics experience if you want to attempt this.
This is going to involve opening your TV and attaching wires to the pins of an integrated circuit. If you're not comfortable with that, this is not for you.
This document is a work in progress.
LG TVs since at least the era of NetCast and "Global Platform" (webOS predecessors) have had the notion of a debug level, generally called "debugstatus". There are three modes: DEBUG, EVENT, and RELEASE. TVs normally operate in RELEASE mode. DEBUG mode enables a variety of logging and other debugging features in webOS, including access to the bootloader console and debug menus via serial. EVENT is similar to DEBUG, although it may not enable as much logging and has other relatively minor differences.