Since Elon Musk's acquisition of Twitter over two years ago, the platform—now rebranded as X—has taken a troubling turn. The growing influence of its CEO in shaping political narratives and promoting specific ideologies, including altering how content is prioritized to reflect his own interests, has become increasingly apparent.
Jenv is great, but the JDKs have to be manually installed. If you need more than just a couple of them, you'll want to be able to install them via command line, and sdkman provides this capability very cleanly for java. So... is it possible to work with both sdkman and jenv? Yes and no. Some tricks will allow you to tell jenv about the java versions that are managed by sdkman, but setting defaults (using jenv local 17.0
for instance) does not work very well. Time for a cleaner solution. Sdkman provides all of the same functionality, with more power and a slightly different (but equally simple) syntax. I've switched from jenv to sdkman. Here's my cheat sheet.
Download and install sdkman. Follow the required instructions after installing. Then, run the config command to enable auto_env support.
echo “Installing SDKMAN"
curl -s https://get.sdkman.io | bash
The set
lines
- These lines deliberately cause your script to fail. Wait, what? Believe me, this is a good thing.
- With these settings, certain common errors will cause the script to immediately fail, explicitly and loudly. Otherwise, you can get hidden bugs that are discovered only when they blow up in production.
set -euxo pipefail
is short for:
set -e
set -u
- initial widget
Magento_Theme/js/view/breadcrumbs
(vendor/magento/module-theme/view/frontend/web/js/view/breadcrumbs.js
) - native mixin that extends this widget:
Magento_Catalog/js/product/breadcrumbs
(vendor/magento/module-catalog/view/frontend/web/js/product/breadcrumbs.js
)
Extend methods of the mixin Magento_Catalog/js/product/breadcrumbs
- Declare your mixin in custom theme
app/design/frontend/[Vendor]/[theme]/Magento_Catalog/requirejs-config.js
file and associate it with the initial widget
COPIED FROM https://build.opensuse.org/package/view_file/games/stockfish/stockfish-interface.txt?expand=1 | |
Description of the universal chess interface (UCI) April 2006 | |
================================================================= | |
* The specification is independent of the operating system. For Windows, | |
the engine is a normal exe file, either a console or "real" windows application. | |
* all communication is done via standard input and output with text commands, |
For a brief user-level introduction to CMake, watch C++ Weekly, Episode 78, Intro to CMake by Jason Turner. LLVM’s CMake Primer provides a good high-level introduction to the CMake syntax. Go read it now.
After that, watch Mathieu Ropert’s CppCon 2017 talk Using Modern CMake Patterns to Enforce a Good Modular Design (slides). It provides a thorough explanation of what modern CMake is and why it is so much better than “old school” CMake. The modular design ideas in this talk are based on the book [Large-Scale C++ Software Design](https://www.amazon.de/Large-Scale-Soft
Express makes it easy to nest routes in your routers. But I always had trouble accessing the request object's .params
when you had a long URI with multiple parameters and nested routes.
Let's say you're building routes for a website www.music.com
. Music is organized into albums with multiple tracks. Users can click to see a track list. Then they can select a single track and see a sub-page about that specific track.
At our application level, we could first have a Router to handle any requests to our albums.
const express = require('express');