Golly if only the configuration wasn't made this way on purpose exactly to cause this exact problem.
977 karma · joined March 24, 2012
Golly if only the configuration wasn't made this way on purpose exactly to cause this exact problem.
intentionally allowing huge billing by default is scummy, period.
Have you ever wondered why `tar` is the Tape Archive? Tape. Magnetic recording tape. You stream data to it, and rewinding is Hard, so you put the list of files you just dealt with at the very end. This now-obsolete hardware expectation touches us decades later.
If you want to experience what your app is really like for the vast majority of real world people, go get a cheap monthly prepaid phone and try it out. Using the modern web on them is a complete nightmare. The screens are physically small and low resolution. The phone I had to use for a year and a half is 800something by 500something, which is literally first generation Android era resolution from over ten years ago. Information density matters. Huge buttons that get in the way are not merely frustrating, they are a design mistake and a demonstration that the designer is out of touch with reality, just as you seem to be here.
Please, get a crappy phone, get a crappy chromebook, make sure your app isn't frustrating to use for people that can't afford new, fast things.
Recently former homeless person here. The Republicans in Congress refused to renew the Lifeline program in 2023 and the replacement is objectively worse in every single way.
> Not all choices need to be subsidized.
Ah yes, being homeless, a choice. I hope it never happens to you.
This is just as likely to be an RCE as it is to be a backdoor. Calling `include` on a file the user can write to is just asking for it. This has been a known footgun for decades.
Y'all might find the term "correlated subquery" helpful here.
When I want them, I always get them. Sometimes I get them when I don't want them. Sometimes it's even my fault, not the result of the query planner looking at me sideways.
Steve Inskeep did 30 minutes with Steve Bannon this week. They did a piece with Chris Rufo yesterday (he's the guy that got right wing media to start freaking out about CRT, and then DEI). But please, do go on clutching your pearls about the WORST POSSIBLE THING EVER: PROPERTY DAMAGE!! Nope, not civil rights violations or gleefully platforming some of the most objectively harmful viewpoints on modern politics, nope, it's PROPERTY DAMAGE that is absolutely the most important possible thing to get upset about.
First, there are three different ways that orders can come in. 1) Tight integration into the POS system. 2) Through a separate parallel physical tablet. 3) Something spits out something on a printer.
There are opportunities with 1 and 2 to do some sort of feedback on how busy things are. I know for the tablet option that at least for some restaurants they are able to indicate how long the order will take.
But half the places I get to have no integration, they just put the ticket on the pile and it's done when it's done. A couple places that do this in particular also don't even start the order until the driver shows up, on purpose. The app will tell the customer I'll pick it up in 5 minutes no matter what. There's a chain that does prep work in front of the customer, but certain locations will not make pickup/delivery orders if there's anyone in line in the shop. I stopped doing deliveries there.
You'd also think that places with the potential for awesome metrics making pickup timing a breeze would be fast food chains, right? Nope. Not a single iota of smart integration whatsoever.
I've found that keeping customers in the loop as to what's happening with their deliveries ends up keeping them happy, even if it's gonna be slow. I suppose some things never change.
I'm on the Oregon state health plan, which requires you to cycle through any of the standard ADHD drugs before they'll let you prescribe the long term versions.
The lowest dose of adderall (sp idk) didn't do much for me, but the next level up silenced the distraction demon pretty well. I ended up trying ritalin next, and am currently on the second highest dose of the long term extended release version.
I was able to notice adderall's stimulant effects, but I didn't notice ritalin's. That got me in trouble on the second day of taking the high dose long term one, or should I say it got me in trouble at 5 AM the next morning. Folks, always modify your full screen games to include a real time clock. It's important.
For now I find it to be acceptable. I've adjusted my schedule to make sure I take the meds on time and go to bed on time. Additionally, thanks to it I now have enough executive function to not only make a schedule but actually be able to mostly stick to it.
Again, this stuff can be life changing. If you have the opportunity, go a month or two with all of the major drugs to see what they do for you. I'm 44 and could have been diagnosed and on meds at 11. Don't wait.
A sufficient dose of a medically prescribed stimulant medication quiets him down enough to usually ignore him, for me. It's been literally life changing. My lack of concrete executive function cost me the job of a lifetime.
So, thanks Matt. Your code may not have aged well, but it touched millions and millions of people.
Every volunteer counts.
Source: David Pitts, who worked on the platform. https://www.cozx.com/dpitts/ti990.html
But that is the very way that they are defined through our historical understanding. The 990 platform, established in 1973, not the 80s, is 16-bit, with 16-bit words and 16-bit pointers.
For anyone that didn't get the context, it's the 99/4 design that has this weird RAM layout. The 990 architecture itself can use any (16-bit) word in memory as the starting point of the 16 registers. Developers have been known to use and abuse the workspace pointer to slide around the "window" on the registers.
The window itself also uses the top three registers to link back to the previous workspace, status, and PC, if you use the proper instructions to branch and return. While there is no stack*, you can still crawl back through those references and get the state of each call.
It's a really cool little architecture, hobbled by the 16-bit address space and how slow it was to keep the registers in RAM. Nowadays I can pick up a 1MB memory chip that's faster than the native bus speed for a few bucks, but that wasn't anywhere near the case in the late 70s and early 80s.
*: The 990/12 minicomputer features the PSHS and POPS instructions, which take a pointer to a definition of where the stack lives and how big it should be. These instructions are not implemented in any production processor, but the platform makes it possible to emulate these instructions in software transparently... as an actual explicit instead of accidental feature in the later few iterations. The 990/12 itself was microcoded on a set of four daisy-chained programmable 4-bit bit slicers so they didn't need any of that nonsense.
Just to make sure, this is what we used to call multi-master, right?
(This is not a "why did they change it" post. Do not make it into a "why did they change it" post.)
Back then, there wasn't a reasonable reliable cross-browser way to get single pixel collapsed table borders. If you wanted to have such a thing, you'd need to nest the table inside another table with a single cell for the background color. But Netscape had awful table rendering performance. The more content in the table, the longer Netscape would take to sit there and render it, scaling disproportionately. The nesting just made it worse! This was also in the days before reflow. If you resize the viewport, Netscape would redraw the entire page from scratch!
I don't like this whole "getting old" thing.
> the majority of CoC documents have been templated and written by one particular in-group of people who share extremist beliefs, and so it has been instrumentalized to drive their communities further into extremism and exclusionary tactics which eject people who believe differently or have dissenting political views.'
> [...]
> And that is why Codes of Conduct are vehemently opposed by people of good will, because they are designed to push an agenda and exclude individuals, not to keep the peace or make safe environments.
Lordy lordy lordy, what a mess. Let's zoom out a bit and add some context to what you've said here. The original open source CoC drama happened because one trans person got tired of being targeted with anti-trans harassment.
One of the primary arguments made against CoCs since then have matched yours in both spirit and even exact wording, as an attempt to frame harassment as "free speech" and shield harassers from the consequences of their own actions.
Your post copies, thought for thought and sometimes word for word, arguments from that time that were created by people that desire to silence and eliminate trans voices.
The real giveaway that demonstrates this is the "eject people who [...] have dissenting political views" thing. This specific talking point was invented to frame the mere existence of trans people as a thing of politics that is open to debate somehow. The emphasis of "one particular in-group" attempts to elevate trans peoples' attempts to stop being harassed for existing as some grand crusade by a strong united front of some kind.
So, for anyone that reads this thread before it's nuked from orbit, the post I'm replying to is the core counterargument from the anti-CoC crowd: they want to be allowed to be bigots and experience no pushback, nor suffer any consequences.
There's always going to be a minimum level of complexity. Sometimes that minimal level calls for throwing a PHP script up on some shared hosting provider somewhere. Sometimes that minimal level calls for an Enterprise-level design with ten layers of abstraction because you need to be able to individually unit test every aspect.
Being aware of where and when to introduce complexity is half the battle.
1) Only ever use it from a desktop browser with a sufficiently configured ad blocker. The mobile apps are intentionally designed to pull you out of the thread with only a single line of text delineating where it does so and no way to actually continue with the thread. It's a miserable experience and the people responsible should be ashamed of themselves. They try to pull the same bullshit on the website but it's more obvious there.
2) Twitter has two reply modes. Direct replies are put under the post they're replying to, much like normal linear forum discussions. But then there's retweets. They create a new thread, quoting the previous thread in the topic starter, so to speak... and unlike the standard linear model, the topic starter is done by top posting, with the quoted bit below.
- Call the "the make a clip button got pressed" function a few thousand times
- Monitored the opacity of the quantum compute section and automatically called the right bits when they'd be most effective and never when they'd be ineffective or counterproductive
- Automatically calls the "entertain" bits when the swarm gets "bored" for maximum AFK-ability
- In the late late late game, allow factory production for only the length of a single setTimeout as to not overproduce factories and throw the entire balance off
If you haven't read the one where he installs Linux on a hard disk, here it is: https://spritesmods.com/?art=hddhack