I've been spending more time reading about robotics projects lately, and one thing that keeps surprising me is how much of the challenge seems to be software and infrastructure rather than the physical robot itself. When people talk about robotics, the conversation usually focuses on sensors, motors, and hardware design. But once you start looking deeper, there are things like AI models, data pipelines, edge computing, security, and system reliability that seem just as important. I recently came across thedreamers while reading about autonomous systems and noticed that many of their projects involve AI, infrastructure, and robotics-related engineering. It got me wondering how common that approach is across the industry. For those working in robotics, what percentage of your time is actually spent on hardware versus software, integration, and system maintenance? submitted by /u/No_Hold_9560 [link] [Kommentare]

The Fear & Greed Index is sitting in the low 20s — solidly "Extreme Fear" — and it feels worse than the number suggests. Wanted to lay out what's actually driving this leg down instead of just "number go down, scary," and open it up. **What's driving the fear** This isn't really a crypto-native selloff. The bigger move is in equities — a sharp semiconductor/chip-stock drawdown has been bleeding into every risk asset, and crypto is just the highest-beta expression of it. On top of that, spot BTC ETFs have seen sustained net outflows over the past month, which pulls out a steady bid that propped up the last leg. BTC's now hovering in the low-to-mid $60Ks after trading a lot higher earlier in the cycle. Memecoins and the long tail are getting hit harder than majors — the usual risk-off rotation. When fear spikes, the speculative froth bleeds first. **The contrarian case (and the honest counterpoint)** Textbook take: "be greedy when others are fearful." Historically, F&G prints in the low 20s have more often lined up with local accumulation zones than the start of real capitulation — sentiment extremes tend to mean-revert. Honest counterpoint: F&G is a sentiment gauge, not a bottom signal. "Extreme Fear" can sit there for weeks, and there's a genuine macro overhang (rates, the equity selloff) that won't resolve just because a needle moved. Plenty of people have caught falling knives buying "extreme fear." Useful context, not a buy button. **The one green corner: privacy coins** The privacy sector has been the standout this year and is holding up far better than the broad market through this — ZEC had a massive run and Monero printed new highs after a major protocol upgrade. Part narrative (surveillance/CBDC fears), part supply dynamics, but it's been one of the few things actually up while everything else bleeds. **How people seem to be positioning** Mostly defensively: trimming leverage (funding got wrecked on the way down), moving to self-custody so they're not carrying exchange/counterparty risk if volatility spikes again, and sitting in stables waiting for confirmation instead of timing the exact bottom. Boring — but boring tends to survive fear markets. Not financial advice, just mapping the terrain. Curious where everyone lands: is this "extreme fear" a gift, or are we still early in the unwind? submitted by /u/b4basit [link] [Kommentare]

pkgit (package it!) What is this? pkgit is an unconventional package manager designed to compile & install packages directly from their git repository. License pkgit is licenced under the GNU-GPL-2.0-or-later. if you did not get a copy, please see https://www.gnu.org/licenses/. [DISCLAIMER] Due to the nature of pkgit, you are solely responsible for vetting the repos that you add to your system. Use at your own risk. Compile pkgit Enter the project directory, and follow one of the following procedures. Using Make make Using pkgit pkgit --build Both methods will create an executable in the root directory of the project. You'll probably also want to generate a base configuration file if you don't already have one. Run this as a user to generate the config in ~/.config/pkgit: make defconfig You can also run this with root using sudo/doas to genereate the config in /etc/pkgit sudo make defconfig Install pkgit After compiling, run the following with root privilages: make install Don't have root? You can specify any install location with PREFIX=. A popular option is ~/.local: make install PREFIX="~/.local" Usage Command Syntax The structure in which you type commands into pkgit is very standard: pkgit [--flag|-f] Flags have two types; long, and short. The short type of each command uses the first letter of its long counterpart. For example: Long: pkgit --install Short: pkgit -i If you use the short version of commands, you can chain them together into one argument: pkgit -qif This example uses the --quiet, --install, and --force flags to: --quiet: minimize logs to stdout --install: install a package --force: even if already installed, will force the package to be installed Installing Packages Pre-installation Before you use any programs that you installed with pkgit, you need to specify the path of the binaries in your shell's configuration. For most users, this is the command: export PATH="$HOME/.local/bin:$PATH" or for fish users: fish_add_path $HOME/.local/bin or for csh users: setenv PATH $HOME/.local/bin:$PATH Basic install Assuming you have already added its respective repo, you can install a package by specifying its name: pkgit --install [pkg_name] Or you can use the short command: pkgit -i [pkg_name] Specific version install You can specify a version of any package based on its tags with '@' separating the name from the version: pkgit --install [pkg_name]@[version] Specific target install You can specify a target of any package based on its configuration in bldit.lua or init.lua with ',' separating the name from the target: pkgit --install [pkg_name],[target] Combined target and version install You can specify both the target and the version of any package you install in the same command (order does not matter as long as the package name is first): pkgit --install [pkg_name],[target]@[version] pkgit --install [pkg_name]@[version],[target] Repo install If you haven't added the package's repository yet, or you just want to be specific, you can install the package using its git URL: pkgit --install [url.git] This also works with the target and version syntax. Local install If you want to install a package from a local code repository, and want to take advantage of pkgit's build system autodetection, you can enter that repository's root directory and install it from there: pkgit --install . Building packages FOR DEVELOPERS You can also use pkgit as a sort of meta-build-system to automatically compile any supported project with the build command: pkgit --build [/path/to/project] This can also be done without specifying the path (pkgit --build) if you're in the project's root directory Removing Packages Removing (uninstalling) a package is as simple as it seems: pkgit --remove [pkg_name] Or the short command: pkgit -r [pkg_name] Updating Packages You can easily update your installed packages by running: pkgit --update Or the short command: pkgit -u Declaring Packages If you prefer a declarative approach, you can use the config file (read below) as a package declaration file. When you're ready, you can declare all your packages at once with: pkgit --declare Or the short command: pkgit -d Dependency Management As it is, pkgit is capable of dependency management, but you will likely have to specify the dependency URLs for each package you install in /pkgit/init.lua. There's not a universal way to check for dependencies without using an existing package manager (unless the package you're installing has a bldit.lua). Configuring pkgit Thankfully, this is a very simple process. To configure pkgit, you have one centralized configuration file: /pkgit/init.lua Thanks to liblua, pkgit pushes a package.path variable directly to your configuration file. This means that you can require any sub-file/directory, without wrestling with require(). The overall structure of the configuration file is explained in detail in config/init.lua [DEVELOPER]: bldit.lua If you want your own package's dependencies, version, compilation, and other aspects to be properly resolved in pkgit, you can create a bldit.lua file in the root directory of your project's git repo. Do not name it anything other than bldit.lua, otherwise pkgit will not find the file. A great example for bldit.lua is right here in the pkgit repository! Check it out if you want to know how it's structured. Contributing to pkgit If you want to contribute to pkgit, please refer to CONTRIBUTING.md