DidYaWipe

Me neither. Was pretty enthused, and even more so when I found that they have a desktop app instead of being yet another Web-only tool.

Then I downloaded the app and found you can't use it without setting up an "account" and being online.

So in the end, this is more tiresome Web-only crap. Deleted.

MPEG-4 was supposed to be the solution, and was quite the bandwagon around 2001 or so. But for whatever reason, the momentum petered out and here we are with a retrograde mess two decades later.

Let's "loud quit" the asinine labels. Want to refer to an age range? There are numbers for that.

Yeah, why is the article entitled "Planetfall," when it has no apparent relationship to the game?

What does this have to do with Planetfall? I expected to land on an online version of the game, but nope.

Is there?

I know that you get the new value; but in many cases (almost every case I encountered), that doesn't help. You mention

"This is very useful for observing changes on data model that drives SwifUI from outside of SwiftUI"

I disagree, because the model hasn't changed yet. That's the crippling aspect to it: You can't tell some controller object to recompute its state based on a change to another object in the model, because you're getting notified BEFORE that object has changed.

For example, if I have an object that represents a camera, and the user tweaks a value in the UI that changes its resolution, the camera might offer a different set of values for things like frame rate.

So if I get notified that the user changed the resolution, I can't then tell the Recorder object to recompute the remaining recording time based on the camera settings, because those settings will not have changed yet.

And incidentally, I've used startObservation() in places, and it's crippled by another idiotic design choice: It only works once. It reports the first change, and then never another one. So in the onChange closure, you have to re-start the observation. Every goddamned time.

It's another great example of serving only the most illogical and obscure use case. Who the hell would expect something called "startObservation" to just quit after one change? The stupidity is just galling.

Thanks. Seems to be some kind of Audi-specific branding.

No wonder these clowns still can't put together a car radio that works reliably, let alone an automotive interconnect system; they're still using the term "multimedia." Welcome to CD-ROMs, circa 1994.

Yeah. Alpha "Motor" has been breathlessly hyping renders for years now, while declaring that their nonexistent vehicles have won all kinds of awards.

Oh, and every year there's "only three days left to invest!"

What is an "MMI box?"

And when making that stuff, turn your camera the right way. The last thing we need is more door-shaped videos.

"a new Observations struct that is created with a closure, and provides an AsyncSequence that emits new values whenever any any @Observable data changes"

Is this another asinine onChange()-style mechanism that actually means WILL change? In other words, it tells you BEFORE the value is set on the object, so you can't do jack squat with it much of the time.

That's the M.O. of onChange now, which is utterly brain-dead. Gee, I've been told that a value changed in this object, so let's recalculate some stuff. WHOOPS, nope, none of the other objects (or hell, even the affected object) can take action yet because they can't interrogate the object for its new contents.

Truly incredible that they not only defaulted, but LIMITED change-detection to WILL-change, the least useful of the two choices.

Yeah, this feature seems wholly unnecessary and possibly dumb. The example given is ridiculous.

If you can't figure out what stripHTMLTagsFromString() does, you have way bigger problems than a lack of spaces.

Back when Apple Notes was useless because it lacked categories, folders, or any other way to ORGANIZE your notes... I turned to Bento.

I can't remember if I liked it or hated it. Probably the latter, since I haven't used it since well before it was discontinued.

Yes, it's all over the mainstream news. Why post it on a tech-news site?

A makeover? This isn't the original Bento at all.

https://dbservices.com/blog/filemaker-ends-support-for-bento

That's interesting. This led me to their page, which also touted the now-free WebStorm.

Can anyone weigh in on WebStorm vs. VS Code for JS/TS development? I'm developing a back end with Deno running locally, and VS Code has been decent for debugging and using the language runtime. Would WebStorm offer any advantages?

I'd hope so.

Just the other day I saw tourists trudging around on Hollywood Boulevard, which is a major shithole. I thought that I can't believe these people aren't deeply disappointed but afraid to admit it.

Yep, that's why line-wrapping is #2. I can see why it'd be less acceptable for some languages.

I didn't make any attempt to interpret it correctly. I saw a map purporting to measure dreariness, and on it a lot of red around L.A.

Given that red usually connotes "the most of" whatever the map is supposed to show, it struck me as consistent with my experience.

When I think "dreary," I don't think about weather. I think about ugly-ass environs.

That's why I looked at the map, saw L.A. in a red zone, and thought huh there might be something to this.

Apple can't even get SwiftUI into a competent state. Creating comprehensive system-wide scripting?

I can't imagine this, and would prefer that resources be spent shoring up Apple's increasingly shitty frameworks.

What an absurd statement.

What? If you have lines that are too wide, you can

1. Change the tab width in your IDE 2. Turn on line-wrapping

This is an oft-repeated and utterly bogus argument. You can simply change how many spaces a tab is in your own IDE. And in decades of programming in IDEs from Borland to Visual C++ (since there were separate 16- and 32-bit versions) to Xcode... I've never seen one default to five spaces. Four spaces is, by far, the most common.

People who don't understand tabs are akin to those who don't understand styles: Doomed to laboriously dick around with formatting, and make work for everyone else.

FYI, it's "lose/lose."

Thanks!

Down-modded by flunkie CA administrators.

I guess you mean "not invented here..."

Yep, any opportunity to not reinvent stuff is a big win.

But I'm wary of layers upon layers. I'm thinking of how this could be combined with MQTT... it doesn't seem totally redundant.

Thanks for the info. Do they still require a working phone number? Their insistence on that is why I have never tried ChatGPT.