392

As a Samsung user, I couldn't tell ya. I've been clicking cancel when it popped up weekly for two Samsung phones in a row.

Is the video not one long science experiment? With you confirming your one textile experiment resulted in a tear?

Also accepting gmaps work, if only it could preemptively cache the return trip for any trip longer than an hour, so that I'm not stuck with no service trying to remember how I got there.

If only folks wrote software with this in mind.

Have you worked in the industry? Would love to help ya with all of the "easy" infra parts that you're talking about, but indeed that secret sauce that decides what to actually trade is the part I can offer zero help in :-)

They might not be saying it's perfect in all cases, maybe just giving the line of thinking that landed us at Katy highway :-)

Tove2d editor demo?

Civil design software?

Have you considered hearing aids for the tinnitus?

Which hearing aid company?

If you believe adding it up linearly is valid, and you care about the results, you should be using more efficient storage software.

Besides memory use I'm not sure why his approach isn't easy for everything you suggested.

Want to group undo actions? It's pretty easy to define arbitrary grouping algorithms on the sequence of recent state snapshots, which yields...a smaller sequence of state snapshots :-) a nice composeable idea.

To show redo after an undo, store recent undo triggers in the state, and if there is undo in current state, show redo with a list of older mem states to jump to. This repr also makes it easy to wipe out redos when doing a redo-breaking operation like editing the doc.

Memory use can indeed become a problem. But if/when it does, there is probably some obvious trait of the sequence of recent states that makes it easy to compress. Like for example that it's 99% the same contents, after a small edit. Or that one edit type dominates. Or that folks don't often care if they can't Ctrl+Z through 8GB of typing.

I think most programmers would gain by not dismissing simple approaches out of hand as too simple.

If writing it off for memory, write out the math for the size of the state and the allotted memory. This is not the era of computers that our languages were invented in; the page size your CPU fetches from insanely fast SSDs can be 4kb. And it can do a lot of that in a blink. Trying to shift runtime work (that the computer does) back to compile/design time (that the dev does) can cripple a system's performance in the short run (for coding/delivery time) and long run (for performance after pointer chasing)...luckily most of the time it doesn't matter anyway :-)

Anything can fail, at any time. The best we can do is mitigate it and estimate bounds for how likely it is to mess up. Sometimes those bounds are acceptable.

This is where s2.dev could in theory come to the rescue. Able to keep up with the streaming bandwidth, but durable.

Sqlite can be run in process. Latency and bandwidth can be made 10x worst by process context switching alone. Plus being able to get away with n+1s could save a lot of dev time depending on the crew, before Claude (tho the dev still needs to learn that the speed problem is due to this and refactor the query, or write it fast the first time)

Why spend Anthropic developer time on charging you less when an MVP impl can charge you $1 for indexing a simple small Helm chart?

Why are you having project design meetings about details as low level as the in-memory representation of data in a program?

Look up "how to reduce salt" on YouTube. And remember, you can lead a horse to water, but you can't make him drink.

Installing delta locally may ruin the GitHub UI for you

Keep watching the movies, you will love the next one :-)

I've poked around three of those links and still not found an accessible good reason. But I am excited to try this, having never used this language before. It rolls into the language a perfect abstraction for deterministically simulating software. See Antithesis's big promises for more. I'm curious to see if this model of flows can be ported to other languages.

That seems an easy fix until one gets nervous about working a month just to release a single -purchase game engine. That's a journey that you can take but you might at least consider a license.

There is simplicity of interface and then of implementation. If you try uv you will find it is both convenient and easier to understand than competing solutions, because everything _just works_ and you find the proof of how it works waiting in your `git status`. You can be assisted in knowing that it just works because its install takes no time and no system setup. It is slick.

Just like real trading :')

Plenty of folks out there can't afford any treatment. This kid has it seems every form of treatment known to man and his dad is trying to make it more convenient for him, with the added benefit that this may make it cheaper/easier for the rest of the world. His level of risk tolerance improves the world and will cause his son no problems, while also avoiding learned helplessness.

Somehow Malloy always gets called out in these threads but not PRQL.

https://prql-lang.org/

I constantly get "memory" notifications from Google photos, to a degree that I suspect is a bug. It's more frequent than any other notification from my phone. It didn't used to be this way.

I think you and I are at the same point in Godot progress. I have chosen to do everything in one scene and leave the code where I first put it when experimenting. It's my project, I'll find the code when I need to change it. Lots of crazy overabstraction on YouTube tutorials by people who are not software engineers but who think obfuscating working code makes them so. Let's sadly look away from why our industry gives them the impression that that's a good idea. I will finally have to learn separate Scenes when I give up on one level with teleports and shift to loading, which may be never.

I watch clickbait Godot tutorials on YouTube on 2x speed in my spare time. When I stumble into a problem that I suspect has been solved before, like your resizeable platform problem, I go to YouTube and see if I can find a reference. For your case, I think you're looking to create a Tool, maybe. You'd need to define your platform as a programmaticly sized node using either tile maps or that texture thing that lets you define the corners, the fill texture, and size from there.

But if it were me I'd lift the code for the platform out of the node that sizes it. Then you can just hand edit each platform, and link the platform to the controlling node (or whatever relation you see fit to use).

It's important to focus on the game over the infinite ways you could structure code in an environment of such high flexibility. At least coding your game with bitmaps in C you can't get lost in trifles, you'll just spend more time reimplementing and understanding the basics. See raylib.

No one ever told Deming that value couldn't be measured accurately for a particular business.