SuperCard was actively developed until a few years back.

https://en.wikipedia.org/wiki/SuperCard?wprov=sfti1

An old laptop has a built in UPS too!

a UPS has a battery that is safe under failure, a laptop usually doesn't.

Eh? I'm using an old MacBook as a home server; I kind of naively assumed that there was a whole load of protection circuitry and firmware controls in there that would turn it off before it expands or the magic smoke comes out.

Do you have experience otherwise?

There may or may not be a whole load of protection circuitry.

Whatever it is that is or is not present, we still get this: https://www.reddit.com/r/spicypillows/search/?q=macbook&type...

I’m also Australian, and have exactly the same answers.

Actually, my fridge has a cold water thing, which has an inline filter built in. But I don’t choose to filter the water as such.

I guess I have to ask…

Is that a real sponsorship read?

Is any of it real?

The marching, the crowd cheering?

Maybe I'm doing it wrong, but I've regretted my previous choice of using the Draper Gem and Decorators when coming back to old projects.

I found Decorators just obscured display logic away in an inconvenient way.

Might've been wise at the time, but nowadays I think the recommendation is to use View Components to package up view logic.

(I'm personally so-so on VCs; I think the core idea is pretty good but I'm not super sold on some of the implementation details - too OOP, not enough `yield`)

That's an important distinction!

There's a difference between not intellectually understanding something and not being able to refactor something because if you start pulling on a thread, you are not sure what will unravel!

And often there just isn't time allocated in a budget to begin an unlimited game of bug testing whack-a-mole!

To makeitdouble's point, how is this any different with an LLM provided solution? What confidence do you have that isn't also beginning an unlimited game of bug testing whack-a-mole?

My confidence in LLMs is not that high and I use Claude a lot. The limitations are very apparent very quickly. They're great for simple refactors and doing some busy work, but if you're refactoring something you're too afraid to do by hand then I fear you've simply deferred responsibility to the LLM - assuming it will understand the code better than you do, which seems foolhardy.

Especially with refactoring, it tends to be tedious and repetitive work that is slightly too complicated for a (regex) search replace.

A lot of repetitive slight variations on the same easy to describe change sounds pretty good to ask an LLM to do quickly.

I can relate to that!

The existential depression cycles that make me wonder why I’m even bothering to do the things that used to bring me joy, or at least keep me occupied, are exhausting.

JetBrains used to develop AppCode:

  AppCode

  A smart IDE for iOS/macOS development

  AppCode is no longer available as a commercial product as of December 14, 2022.

  https://www.jetbrains.com/objc/

It seems that Fleet will support building XCode apps. It looks like a big regression from AppCode. As of today Fleet doesn't compile my macOS app. I try regularly on new updates. No alternatives, unfortunately

Fleet will also most likely get abandoned as people who pay for an IDE highly prefer the older one and people who want VSCode use VSCode

I also think any revival of AppCode is also dead as JetBrains is all in on Kotlin everywhere. iOS multiplatform support hit stable recently.

JetBrains already announced it is no longer targeting Fleet as its iOS strategy for Kotlin Multiplatform. Instead it will be realizing its strategy through IntelliJ IDEA and Android Studio.

What's Fleet?

It likely doesn't help the ObjC part of that story, but they moved the Swift part out into a CLion plugin https://plugins.jetbrains.com/plugin/8240-swift

Regrettably I didn't see that they did anything with the ObjC part, choosing to /dev/null it

Objective-C has been supported in Clion for years: https://www.jetbrains.com/help/clion/objective-c-c-support.h...

Unfortunately, even that isn't supported any longer. I do a lot of server-side Swift development and would LOVE to be able to ditch Xcode for CLion and the Swift plugin.

The quote below demonstrates the warped thinking and perspectives!

Why not put the AI in a bunker with an off switch?

The idea that you would choose to release a technology that could be dangerous, whilst assuming you can hide in a bunker and be ok is astoundingly cruel and naive.

From the Article: “Once we all get into the bunker—” he began, according to a researcher who was present.

“I’m sorry,” the researcher interrupted, “the bunker?”

“We’re definitely going to build a bunker before we release AGI,” Sutskever replied. Such a powerful technology would surely become an object of intense desire for governments globally. The core scientists working on the technology would need to be protected. “Of course,” he added, “it’s going to be optional whether you want to get into the bunker.”

That’s a shame!

I haven’t used Swift UI in a couple of years, but I always thought the basics of it were excellent.

They got the declarative API foundations right I thought.

Shame it’s still flakey.

The preview used to crash constantly last time I used it.