Relax, I only have one Sunday to work on idea, literally my weekend project. So I tried Deepseek to see if it can help. Surprisingly, it works and it saves me another weekend...
Just chat.deepseek.com (cost = free) with prompts adapted from this gist.
| $mode = Read-host "How do you like your mouse scroll (0 or 1)?"; Get-PnpDevice -Class Mouse -PresentOnly -Status OK | ForEach-Object { "$($_.Name): $($_.DeviceID)"; Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Enum\$($_.DeviceID)\Device Parameters" -Name FlipFlopWheel -Value $mode; "+--- Value of FlipFlopWheel is set to " + (Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Enum\$($_.DeviceID)\Device Parameters").FlipFlopWheel + "`n" } |
Copy of commit message to mpv repo:
stream_libarchive: workaround various types of locale braindeath
Fix that libarchive fails to return filenames for UTF-8/UTF-16 entries. The reason is that it uses locales and all that garbage, and mpv does not set a locale.
Both C locales and wchar_t are shitfucked retarded legacy braindeath. If the C/POSIX standard committee had actually competent members, these
[ Update 2020-05-31: I won't be maintaining this page or responding to comments anymore (except for perhaps a few exceptional occasions). ]
Most of the terminal emulators auto-detect when a URL appears onscreen and allow to conveniently open them (e.g. via Ctrl+click or Cmd+click, or the right click menu).
It was, however, not possible until now for arbitrary text to point to URLs, just as on webpages.
| What is some existing documentation on Linux memory management? | |
| Ulrich Drepper (the glibc maintainer) wrote an article series called | |
| "What every programmer should know about memory": | |
| Part 1: http://lwn.net/Articles/250967/ | |
| Part 2: http://lwn.net/Articles/252125/ | |
| Part 3: http://lwn.net/Articles/253361/ | |
| Part 4: http://lwn.net/Articles/254445/ | |
| Part 5: http://lwn.net/Articles/255364/ |
| [user] | |
| name = Marek Niepieklo | |
| email = xxx@yyy.zzz | |
| [alias] | |
| alias = "!f() {[ $# = 2 ] && git config --global alias.\"$1\" \"$2\" && exit 0 || echo \"usage: git alias <new alias> <original command>\" >&2 && exit 1}; f" | |
| aliases = !git config --get-regexp 'alias.*' | colrm 1 6 | sed 's/[ ]/ = /' | |
| amend = commit --amend -m |
Extract from POSA 4
The specific partitioning criteria can be defined along various dimensions, such as abstraction, granularity, hardware distance, and rate of change.
The abstraction dimension
For example, a layering that partitions an architecture into presentation, application logic, and persistent data follows the abstraction dimension.
The granularity dimension
Quite a lot of different people have been on the same trail of thought. Gary Bernhardt's formulation of a "functional core, imperative shell" seems to be the most voiced.
"Imperative shell" that wraps and uses your "functional core".. The result of this is that the shell has fewer paths, but more dependencies. The core contains no dependencies, but encapsulates the different logic paths. So we’re encapsulating dependencies on one side, and business logic on the other side. Or put another way, the way to figure out the separation is by doing as much as you can without mutation, and then encapsulating the mutation separately. Functional core — Many fast unit tests. Imperative shell — Few integration tests
I have a pet project I work on, every now and then. CNoEvil.
The concept is simple enough.
What if, for a moment, we forgot all the rules we know. That we ignore every good idea, and accept all the terrible ones. That nothing is off limits. Can we turn C into a new language? Can we do what Lisp and Forth let the over-eager programmer do, but in C?
| #include <iostream> | |
| #include <unordered_map> | |
| #include <list> | |
| #include <stdexcept> | |
| template <typename K, typename V> | |
| class lru_cache { | |
| private: | |
| typedef std::pair<K, V> cache_entry; | |
| typedef std::list<cache_entry> cache_list; |