552 karma · joined December 1, 2024
What quantization are you running for these? Like, you cant just run the "real" ones on your laptop right?
Wouldn't the performance of Qwen3.6-35B-A3B be drastically different if its quantized to 2b, 4b, 5b, etc? And also be effected by who did the quantization?
When I do something "heavy", my 9800x3D will kick on the fans and start making lot of heat. This is fine when I'm intentionally doing say a transcode, but if I'm just querying syntax it could get pretty annoying. Do you "feel" it? I know that will be pretty machine dependent.
Lies?
They even list it in the user guide https://remarkable.guide/guide/access/ssh.html along with an "developing software" guide https://remarkable.guide/devel/index.html.
Maybe other tablets are like that too, to be honest I'm too poor to swing the 700-1000$ for what I can cover with an paper note pad (with the bonus of being able to comfortably sit my coffee cup on it, use any pen or pencil, rip pages out, drop it, forget it somewhere, etc etc) to buy one but at least it seems like a product I would support.
Yes, I'm using RADV :)
Proceeds to literally loop around 6 times.
> users are still served only by the proprietary driver [...] An open source Vulkan driver on Windows opens up a number of possibilities: a shared codebase across platforms, easier debugging and experimentation, faster turnaround on fixes, and a path for the community (e.g., game developers) to report problems or contribute improvements that benefit everyone regardless of operating system.
To me, the argument against a proprietary driver seems extremely weak if you're running Windows anyway, but I guess they see it more that if more game devs can run the RADV driver, they can get wider testing (or a simpler story for devs to test at least) and backdoor improvements into the Linux side?
I guess I dont understand the "a shared codebase across platforms, easier debugging and experimentation," comment. Shared RADV codebase? Or shared game engine code, at least the specific parts of the engine that target Vulkan x Radeon (how big is that really?). Similarly I guess "debugging" here is tracking down odd ball RADV bugs where you could then run it in windows to see if its a linux thing or a RADV thing?
He searched his pockets. No more coins; nothing.
“I’ll pay you tomorrow,” he told the door.
Again he tried the knob. Again it remained locked tight.
“What I pay you,” he informed it, “is in the nature of a gratuity; I don’t have to pay you.”
“I think otherwise,” the door said. “Look in the purchase contract you signed when you bought this conapt.”
In his desk drawer he found the contract; since signing it he had found it necessary to refer to the document many times. Sure enough; payment to his door for opening and shutting constituted a mandatory fee. Not a tip.
“You discover I’m right,” the door said. It sounded smug.
From the drawer beside the sink Joe Chip got a stainless steel knife; with it he began systematically to unscrew the bolt assembly of his apt’s money-gulping door.
“I’ll sue you,” the door said as the first screw fell out.
Joe Chip said, “I’ve never been sued by a door. But I guess I can live through it.”
- Ubik
The nature of them being basically forced to inherit the module name means its pretty obvious that `MyAppWeb.Admin.Components.EmailValidator` is in the `MyAppWeb.Admin.Components` module. I also think it probably strongly depends on how much JS you actually have, most of my liveview apps have it "here and there" to enhance something or minor DOM fiddling, if you are booting react components everywhere and have some other pile of existing js code, its probably not so good.
I dont think its inherently any more insecure than another method, you just have to recognize that clients can create malicious requests to `handle_event(my_event, params, socket)`, just like you might to `my_action(params, conn)`. It's also pretty painless, normal, to just crash on bad data, it will only effect that one naughty lv process.
You could also send "control" signals to the phoenix liveview process via the same socket but I dont think that actually as much surface outside of heartbeats and closing the socket.
Commercials, 45 – 60 mins
"Standing Around" & Stoppages, 65 – 75 mins
The Halftime Show, 25 – 30 mins
Replays & Commentary, 15 – 20 mins
Actual Football Action - The ball is live and in play, 11 – 16 mins
versus what it says about AFL, Actual Football Action - The ball is live and in play, 80 mins
"Time-Off" Stoppages, 30 – 40 mins
Commercials, ~15 mins
Scheduled Breaks, 32 mins
Wonder how that effects the social dynamic of watching games, I imagine you have more time to "shoot the breeze" during an NFL game. It's also not apples to apples comparison as my understanding of NFL is that it's probably shorter but more packed intervals, setup -> crunch, setup -> crunch. AFL can have a bit of back and forth to it maybe.Also this says nothing of on-ground and around-ground ads which I always found depressing, which I guess must exist in all sports.
Can you expand on what you mean by stale? I don't get how an artefact-producer can get "stale" besides literally out-of-data information which I dont think you mean because you mention fable.
https://windupstories.com/books/pump-six-and-other-stories/
Also I guess Silo / WOOL by Hugh Howey is perhaps closer to what you wrote literally but probably not quite the vibe maybe.
I know its all volunteer work and extremely not fun at the moment, but it feels weird to not even have some sticky-no-reply on the AUR sub forum with a list of compromised packages. You have to instead try and scrape them up from around threads like here or reddit.
> information above is fucked. For example
I imagine at some point writing "fucking" was rebuffed, or maybe you can write "fucked" but not "fucking", or there was some time between those paragraphs.
> https://www.amazon.com.au/stores/author/B001H6Q2TE/about
> This is awkward and a little creepy. They tell me I have to do it for promotional purposes, but I've already got a blog. I've already got a website. Being told that setting up an author page on fcuking Amazon is essential to success? A company that treats us all like such goddamn children it doesn't even allow us to correctly spell an epithet with a venerable history going back 900 years or more? That just sucks the one-eyed purple trouser eel.
>
> Also the bio information above is fucked. For example, my work has only appeared in 36 BoY collections, not 350; the noms and awards info is out of date too, but apparently it was all written by some publishing house and I can't change it from this interface.
>
> Still, here I am. But if you're really all that interested, go check out my actual blog/website. Google is not your friend (any more than Amazon is), but at least it'll point you in the right direction.
>
> I'm the one on the left, by the way.
Hell yeah brother.
Wonder when it was written and what it would say if written today.
There has always been "unpluggers" [0] amongst technologists, but the vibes are bad and getting worse. I feel like that is getting more common between "normal" people I know, but maybe outside of my country town bubble its not happening.
I was thinking we're only one or two big influencers away from a cascade, but then the ultra-influencers are never really going to commit because its their livelyhood and saying throw your phone away is self-limiting on the viral aspect.
I guess we're just stuck under the boot.
^0 https://biggaybunny.tumblr.com/post/166787080920/tech-enthus...
I am also halfway through Old Gods on my own time. What I find interesting is how different in tone his books can feel. It is a bit of a sprawling question on what to read though, besides "all of it" which is often not so helpful.
One day I will trick her into listening to a Le Guin.
If you want a picture of the future, imagine a DJ playing Here Comes the Sun— forever
- self hosted
- works offline (mostly)
- "just md" BUT
- scriptable or extendable by lua, rendered in page, eg `${1 + 1}` outputs `2`, but you can do a lot more, such as query pages and tags with a LINQ type query interface.