"But I was very skeptical. The trailers seemed to indicate a train wreck. They were full of explosions, angry screaming guys and the taglines about war. Dune was never about war. War was in there, but it was never the point. But cinema, SciFi especially, loves special effects, and big-booms are amongst the most used. I dislike a lot of SciFi movies from the USA, as the (so called) spectacle is all there is."
Do I know any fvwm users? If looks very cool, but outside of being lightweight does it provide any cool features? In currently rocking a near-mainline dwm so it is also lightweight.
So, GPL forces all derivatives to be GPL as well, so I can not make a closed fork of Linux and sell it for millions.
But let’s say I create a product. I develop it internally. But it’s also released it as OS GPL. does my own closed source root also falls under GPL? It’s not a derivative but a base?
Im thinking of extracting review part of my site to a dedicated section. I love sections.
But this poses the biggest question of them all: naming. „Reviews” sound boring. „Fun” sounds cool, but everything I write about is fun - emacs is fun, bsds are fun. Heck, even drawing graph of stats is fun for me! It would be a sad life to have a hobby that is not fun.
But how do I put anime, old sf, fantasy and technical book under one name?
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/CC/E/IT/O d+(-) s+(+): a C+++$ UBC+(+)$ P L++ E++$ W+++$ N o K--? w--- O M V? PS+++(+++) PE Y+(++) PGP+ t++ 5+++ X++ R tv b+ DI++ D+ G e+++ h-- r+++ y
------END GEEK CODE BLOCK------
Post-hoc explanations based on personal interactions with processes that are substantially random will generally be incorrect. The observed patterns will be random, not systemic
IOW, everything written about LLMs from the perspective of a single practitioner can be dismissed out of hand. The nature of LLMs makes it impossible to distinguish signal from noise in your own practice
I suggest not even reading these posts. Our brains are unfortunately wired to mistake confident writing for evidence
This is absolutely a spec issue. As in there is none. Programmatic discovery and manipulation of selection ranges inside shadow roots is simply undefined, which is why we now have three different behaviours
Until there’s a genuine consensus on what is supposed to happen, the only sensible thing is to avoid shipping anything that requires text selection (i.e. any form of text editing or highlighting) in a shadow root. https://mastodon.social/@marijn/112234316153174392