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".
> I think the Opus and Fable design (that I saw for a short while) have gotten stale
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.
I think they mean the style these tend to put out is becoming noticeable in too many places and therefore the resulting frontends feel stale, ie not "fresh" or unique
Pump 6 and Other Stories has a few in that vein, sort of. Eg there are no petrol engines, instead compression springs, treadle operated computers, etc. There are some pretty grim stories in there, some may find them distasteful.
Chiming in to second this, Pump Six and Other Stories left me with a deep, deep sense of dread after I finished reading it. Highly recommended, such an underrated collection.
It is a bit disappointing to not see any mention anywhere official.
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.
> 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.
> 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?
> author page on fcuking Amazon is essential to success
> 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.
We must, at some point surely, reach an inflection where even everyday people are sick of this shit and start smashing their phones right?
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.
Most people I know who are bombarded by worthless updates every minute either ignore them but don't bother to disable any or are glued to their phones anyway, so they are beyond help.
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
reply