There is a corporate side with other features that has never been free. I pay for it because it's great.

I'm not sure if you're purposefully misstating it at this point or not. Several people have corrected you and you seem to double down incorrectly each time.

My experience with writing and royalties is just so different than this author's experiences.

If you write bad code that creates a bug, I expect you to own it when possible. If you can't and the root cause is bad code, then we probably need to have a chat about that.

Of course the goal isn't to be a jerk. Lots of normal bugs make it through in reality. But if the root cause is true negligence, then there's a problem there.

AI makes negligence much easier to achieve.

It's a pretty nice system, actually.

Obviously things take as long as they take. I've always been an educator of this back to the business leadership. In my experience, most business people truly have no freaking clue how a product gets built and code gets shipped.

Giving proactive updates (meaning not the day it was expected to be done according to last update) are important part of a professionals working life. There's always a tension between business and engineers. Engineers just generally don't do that well with tension and try to minimize it, or complain about it.

It's not binary.

Also, you do realize that writing is taught in an incredibly formulaic way? I can't speak to English as second language authors, but I imagine it doesn't make it easier.

I would spend similar time debugging this if I were the author. It's a pretty serious bug, a non obvious issue, and would be impossible to connect to the ffi fix unless you already knew the problem.

I interpreted that to mean they may not have permanent US immigration issues vs "being deported".

"You're right, keep it on the 2028 roadmap"

That would be my experience in tech at least.

I'm not sure if it should be salvaged?

It was drying in the chemistry back office and there must have been a draft. It exploded during a silent study hall.

Somehow they let us remake it for class that afternoon. We tried to put it on the floor as a joke, but our teacher was wearing sandals that day (no lab). She wasn't happy about it.

I originally got the idea (and prank idea) the previous year from a retiring chemistry teacher.

Preface: I'm generally an AI skeptic.

There are a LOT of people who are doing "business work" for a living, which is significantly different than hands-on coding. AI gives these people a way to just automate all of the (maybe necessary) work that they don't want to do.

The final product being 80% good enough is fine. It is done and doesn't require them to spend time on something they don't want to do.

More often than not, it is at 80% today.

People that know enough to care will know within 1 second what the article is about.

"Soft real-time" is probably the correct term here, but that is actually more confusing for 99% of people.

"Interactive" is not descriptive. "Duplex" is certainly not obvious.

I'll state it again although I don't have good faith in this conversation: because the majority of people don't prioritize (or even believe in climate change), the tactics are going to be different than other social issues.

Literally look up any polling on the matter for "proof."

You can push for change while also recognizing that others don't respond well to it. Why? Because you need to adjust tactics to get the outcome you want.

Blindly "spreading hope" is just as lazy imo as saying everything is futile.

You have to live in the world the way it is, not the way you want it to be.

And let me be very direct: I'm close to positive the approach you've shared will not work. Sorry. It will be too late by the time people get onboard (when it's clear that the medium-term negatives will outweigh shorter term costs).

Do I wish it wasn't that way? Yes. But what if it stays that way? Is there a solution then?

I'm not saying the fight shouldn't be had. I am saying that—at least in the USA—change doesn't really appear to be a priority unless the $ is there.

I know there are paradigms to handle that now, although the details get complex in practice. For example, the idea of a "portal" in react is actually really important for layering modals and popups properly, but it can be difficult in LiveView.

The biggest single challenge I remember hitting was dynamic recursive forms (for example a logic builder). It took a lot of effort to get right.

I built my (unfortunately) failed startup using LiveView for ~18 months. It was actually really good to work with and a great product experience.

I ended up integrating React into it as well for some particularly complex / mature libraries (react-grid-layout, WYSIWYG editor). Pretty seamless connection to backend LiveViews, and I tried to keep everything in LV as possible.

The biggest difficulty was hitting problems that I had solved 50 times in React, and had to solve from-scratch in LiveView. Once I figured out a problem, I could re-use it easily.