Lmst

It's hilarious how minor tasks explode in tech...

I wanted to write a #gentoo :gentoo: ebuild for #tailwindcss to be able quickly install and update the standalone binary. Got the ebuild working but when I run the binary from /usr/bin it complains "Pkg: Error reading from file." After digging around the repo I realize the binary is built with #bunjs and now I'm sitting here disassembling the binary in #ghidra mucking around with #gdb and learning #zig as I go.

All fun and games till I realized it's 5am and the 2nd day I've went without sleep... :laughing_cirno: :blob_dizzy_face:

I just completed all 25 days of Advent of Code 2024! #AdventOfCode https://adventofcode.com/

@ecadre thanks so much for this! this is exactly what I was wanting to do! 😀

@ecadre Literally the exact same use case, I'm adding family birthdays and anniversaries to my calendar and I wanted the day of the week.

There is a `org-read-date-force-compatible-dates` custom variable to remove the bounds but I haven't played with it yet.

@ecadre You're right that agenda picks it up!

Interactive `org-time-stamp-inactive` doesn't work. Did a bit of digging and found that `org-read-date-analyze` specifically bounds the date between 1970 and 2037. I'll just manually type the date instead.

Thanks so much for the info!

Does #emacs #orgmode not support time stamp dates before the unix epoch?

mndz boosted:

Are #framework laptops prone to becoming uncomfortably warm when in operation? A too-warm palm rest is a bit of a deal breaker for me. Also, I hear the speakers are crap, any upgrade options?

I'm looking at the smaller one, I believe it's 13 inches or so. How well does it run #Gentoo and should I chose AMD or Intel?

mndz boosted:

I've seen this one come up a few times in PL threads too... despite what some believe, Go is not a memory safe language!

Specifically, Go is not memory safe if your program uses goroutines. Go does not protect against data races, which trigger UB and memory unsafety.

See: https://go.dev/doc/faq#atomic_maps
Also: https://blog.stalkr.net/2015/04/golang-data-races-to-break-memory-safety.html

This is unlike Java, Python, and I think C# too, which do guarantee no UB or memory safety issues even if you don't handle concurrency properly.

Safe Rust is technically in the same camp as those, but better in practice because it tends to push you towards writing race-free code.

Every time I replace a SFINAE with a concept, an angel gets its wings! #cplusplus #cpp

mndz boosted:

It doesn't get old.

mndz boosted:

"Note that Recall does not perform content moderation. It will not hide information such as passwords or financial account numbers."

The computer, however, will stop you from recording DRM'd content.

Find it fascinating that when faced with drawing safety and security boundaries, the primary beneficiary is not the owner of the device, or the person using it, but random corporations who control the intellectual property rights.

The system doesn't work for you.

mndz boosted:

TIL: `std::filesystem::path` has `begin ()` and `end()` iterators, allowing you to apply algorithms to paths!
Used that to implement prefix search and removal today 😎.

#cpp

mndz boosted:

#270 Given the following in C++

template <typename T>
void f(T);

void g() {
f<int>(1);
f<void>(); // Well-formed? f now takes zero arguments?
}

Without checking:

A. Yes
B. No
C. Show results

#Cplusplus
#Cpppolls

@cJ @mgorny If the issue is strictly in the software source, then upstream with additional non-public reporting to Gentoo Security if applicable. If the problem is in Portage, Emerge, or how the package builds or integrates with Gentoo, then the Gentoo bugzilla. Sometimes it's not straightforward and you have to make some judgement calls.

mndz boosted: