This is pretty refreshing to read. "Its just linux", seems to ship with SSH/root terminal enabled (over USB at least, with a simple way to enable networked access), built in webserver, just uses systemd for service control, etc.
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.
> 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.
I have good news: they (RM2s) are often available on ebay for much less. People buy them thinking they're getting something like an android tablet, but they do nothing out of the box apart from showing docs and taking notes. Sometimes they're returned immediately for a full refund, but often they sit in a drawer, untouched, till they get offloaded on ebay for - comparatively - peanuts, letting us scoop them up and breathe new life into them (koreader rocks, to start with).
Yeah I got an RM2 cheap off there and I’m very impressed. It only really does one thing but it does it well. Personally can’t really see any reason I’d need a more powerful one, the latency is great already. Maybe for the front light.
They are quite hackable, but a lot of the mods rely on some funky QT hacking… it’s all a bit kind of undocumented. I was able to get Codex to get full Chromium running in a chroot and render the screen via Xvfb though which was pretty cool and is somewhat usable, so I guess most things are possible with determination
Yeah, koreader is great. As long as you're fine with greyscale, the rm2 size is great for comics and textbooks. Most ereaders are way too small for both.
I have a Kobo that was kept unused in a similar state for a few years until I decide to build an SDK platform to develop and deploy apps on it. My Kobo does not support apps on its Linux platform.
I have been using it to read HN, as an RSS reader over my news and blog sources, generate audiobooks on topics I want to understand with ElevenLabs, Exa and OpenAI and listen via connecting its bluetooth to my speakers and even as a remote Claude Code & Codex approval sidekick.
It is amazing that a $100 device with a single core and 512mb RAM can do so much and run for so long.
NickelMenu is fantastic for adding custom buttons and some extra. We use it to display the Cobalt entry button on the stock Kobo interface.
This SDK provides more of an android/iOS type framework to use underlying hardware like bluetooth, wifi, battery and a bunch of UI components for creating complex apps with eink rendering, notifications, managed windows, OTA updates, a simulator, a sidekick mode for your apps and more.
The original CTO, Martin Sandsmark, was a heavy Linux user and made some incredibly based choices for remarkable. If you look in the right places on the internet there are some really cool images of remarkable hacks he was showing off to people for fun.
> 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?
> 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?
Are you using an AMD driver?
Let me share my experience. One day, you wake up and your GPU driver is gone for no reason. I'm not even joking here—the recent driver update broke the driver for many users. Launch Battlefield 6, and your driver is... gone. A new driver update comes out... Launch Battlefield 6, hard freeze. Improvement. I'm still running an older "blessed" driver version for this reason, and I'm scared to update.
I had an rx 5700xt where one version worked on bf4 but it didn't work on doom eternal. Meanwhile the version had unusable performance when streaming my game to friends. So any time I wanted to play games with friends I had to reinstall an older version. This stayed an issue for months with no communication from AMD.
My current rx6900xt meanwhile has quite a few other stalls and crashes, and doesn't get any of the cool rocm support the 7000series gets.
So my next gpu will be an nvidia. Paying over a thousand euros for a gpu, only to get your support dropped after 2(two!) years of shoddy drivers is just unbearable.
I understood shoddy drivers in the R series, Vega(another lemon i bought) as well, AMD was flat out broke. But by now they surely have some money left over from the ryzen success to make their gpus at least stable.
Russia has attempted to jam Starlink satellites but with very limited success. The problem for Russia is that the constellation is enormous and uses highly directional phased-array radios which are naturally resistant to jamming. They can temporarily jam a few birds over a limited area but don't have the resources to effect sustained denial. We might eventually see them escalate to kinetic strikes on the satellites.
You are right about drones, but Starlink etc is still used a lot by forward deployments of troops. Afaik it has revolutionised the ability to contact these deployments. But I'm not an army guy
> Sure beats opening some ancient project and seeing some mix of Vite, Vitest, Oxlint and Oxfmt and a bunch of other disjointed stuff (I migrated that one over to also use the newer stack).
I mean if I see those in N years, I'll be happier than with the older stack that came before them - the jank levels seem to generally be decreasing with every next attempt to get things right!
The door refused to open. It said, “Five cents, please.”
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.”
I quite like the colocated JS. I much prefer to define a components "hook" code inside the component. I think you could abuse it, I would never put colocated JS just in some template to include it "just to avoid writing a js file" but for keeping `email_validator.js` code right next to the `email_input` component, its quite nice I think.
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.
There is some propensity to forget that you're basically making a REST API because its all "in my process, responding to messages", it feels like you're writing your regular server side render controller. But really instead of `PUT /create/post` its `websocket.send("create_post", {})`, so you need to understand that if you only want to operate on `user_id=1`, you need to not just accept `{user_id: 1, ...data}`.
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.
Wow, I have no idea how accurate it is, NFL is not in my country, but google says there is about 11-16 minutes of actual play??
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.
A game is 60 minutes, broken into 15 minute quarters. The play starts, the clock starts. The televised game is almost 3x that, but at least most of that is actually part of the game flow. Each play is basically a 15 second sprint.
The stat you read is flat out inaccurate. There are 60 minutes where the clock is running, and the vast majority of that is with the ball live and in play. I would say something like 45+ minutes out of the 60. Also, in fairness I've been to a couple of NFL games, and the commercial breaks tend to happen when the game clock is paused by the flow of the game anyway (team calls timeout, referees are reviewing a play, and so on). It's uncommon for the game at the stadium to be stopped waiting for the broadcasters to show their commercials.
> The stat you read is flat out inaccurate. There are 60 minutes where the clock is running, and the vast majority of that is with the ball live and in play.
You are completely wrong. I know that's what your intuition feels like from watching games, but if you actually get a stopwatch out and clock it, you'll see it's much closer to op than what you posted. Very close in fact.
If you don't believe it, find a actual game and time it. I did this on a game.
For example from the 8min mark to the 2min warning (6 mins of clock time) there were only 2m15s of action. Only 37.5% of the clock time was action. And that was an extremely conservative time. It was the 4th quarter, had multiple scoring plays, and multiple timeouts - essentially everything possible to do to stop the clock and still it maxed out at < 38% of the clock was actual game time. If you instead do this for a full game (not the end of the 4th quarter), and especially games that aren't close and you'll see it's way less. Definitely not what you're expecting.
Football is a tiny amount of "action time" as compared to "clock time".
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.
reply