This breaks down because Tailwind is not monetized, is completely free, and hasn't indicated it won't be.
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.
It adds accountability, which is unfortunately something that ends up lacking in practice.
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.
Pragmatic has an inhouse book compiler. Most authors write in markdown and there's some special XML features you can use as well for it. Of course code linking is a first class feature.
That's a strawman. It is not really related to the main point and I'm not sure of the point you're trying to make (maybe that tension exists?)
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.
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 read it just fine and everything made sense in it.
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.
The article makes it sound as if there were govt negotiations to have them sent home. It is light on details though, but with that many people of a friendly nation / corporation I imagine they get treated differently.
I interpreted that to mean they may not have permanent US immigration issues vs "being deported".
Maybe my position on this is obvious, I honestly don't know a lot of how others see it.
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.
It uses long polling over http. To be clear it's not restful http, but it's not websockets. I believe that Chris doesn't believe it's important for most people so there are no directions right now. Could be wrong there, I'm not Chris.
Page changes are still initiated by the client in LiveView (although can be server initiated)
LiveView is just channels under the hood. Once you consider that, long polling may seem more obvious
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.