One thing that is so painful with Stripe is the Disputes because no matter how much evidence I show, even emails with the user claiming they did it because of X, Y, Z. ToS not upheld, etc, the customer always wins.
For me, I do a cheap subscription (4$/mon, first month 2$) and one dispute costs me like 20-30$. So that one person wipes a ton of profit from me. I always try to refund them (but you can't refund a customer with a dispute in effect).
Stripe is great to get going, but has a lot of painful points.
I’d be curious too. Previous experience at a SaaS was that we never won disputes and it was too time consuming on top, so we just ate the dispute fees and refund.
I always thought things are easier with a physical product where you have a 3rd party like DHL that proves delivery was made. But at least in my tiny sample space, that’s not enough to win the dispute.
What's interesting to me is that it seems a lot of people got burned by AngularJs (Angular 1) and now swear off Angular as a whole.
Like many, I came from pre-SPA days -> AngularJs -> Angular 2 -> Modern Angular. I tried react a few times, plus React Native but found it hard. I wasn't good with a slightly different render-syntax (whereas Angular uses HTML) and every project I was on was wildly different from each other.
Modern Angular has been wonderful. A lot of the pain points people have are gone, some good parts of other frameworks (signals, single-components vs modules, etc) have been incorporated and embraced.
For what it is worth, I missed AngularJS/Angular 1 and managed to use Aurelia to avoid several versions of Angular 2+. When I did get eventually pressured into working on Angular it was a nightmare for several reasons. One of them was I got hugely burnt by Zone.js. Angular is finally doing something about Zone.js years after my warning. (Though it took Signals to push them to do it, which is another rant because Signals are just dumber Observables and Angular already has an RxJS dependency.)
> (whereas Angular uses HTML)
Angular has as complex a template language as any other major framework. The fact that it uses .html files is a convenient lie to make it seem like it is "just HTML". Its template compiler is a far more complex beast than JSX. (And it doesn't have anything like half the type safety of TSX.)
i actually started with angular 1 before it became popular. i evaluated the alternatives at the time, knockout, ember and a few others, and angularjs just looked the best. finally when angular 1 was no longer maintained i discovered aurelia, in part because rob eisenberg had an interesting story about how he got invited to the angular team because of his ideas, and how he left again because he could not actually get his ideas implemented.
it's a bit disappointing that development of aurelia 2 is slow going, but in some ways i consider that a good thing, considering how fast vue and svelte are evolving away from what they were originally.
i need to look at solid.js though. the only promising newcomer in resent years if the state of js survey is any indication.
I was more of a fan of Durandal, which was Aurelia's predecessor. It was a SPA wrapper around out-of-the-box Knockout. It seemed cleanly focused and was useful in that you didn't need to learn a different view engine if you were already using Knockout.
Following Rob's blog because of Durandal was a part of how I landed on "try to avoid Angular" and it did give me Aurelia as a bit of arsenal to say "hey, this framework is enough like Angular that it should feel comfortable to work in" for a time.
I never did end up liking Aurelia more than Durandal, but I certainly liked it more than Angular.
makes sense. i was obviously coming from angular, and as i said before, i did look at knockout and i found angular was the better choice. so i guess aurelia's appeal then came naturally. but then i didn't know about durandal, so i can't say how much i would have liked it. but this tells me that angular had a stronger influence on aurelia than i was aware of. that's not surprising of course, but still interesting.
Steep price, but honestly makes a lot of sense. Lifetime licenses are never sustainable when you own a lot of infrastructure. Plex owns the auth, the reverse proxy infrastructure (to make it dead simple to setup), and a ton of development overhead and backend licensing deals.
They obviously want to shift people to a monthly plan, but still give that lifetime. If I were to buy today vs when I originally, it would still be cost effective.
There are alternatives, so users that don't want to shell up the 150$ now can jump over to. It's closed source software and the users have the opportunity to shift (or build a competing software that meets more of their core needs).
There are some really nice enhancements in here. My favorites are obv the async runtime switching from state machine and some of the JIT Optimizations. It's always impressive how much squeeze the .NET team can get out of the framework.
Plex is aimed for a simple ease-of-use experience, so if you aren't technical enough to setup a reverse proxy, Plex offers all the authentication and proxying for you.
It's not a true self-hosted software. It just depends on what matters most to you.
I just want to throw out that you might like Kavita for a comic/book server. It's built to feel like Plex. https://www.kavitareader.com/
I do agree that Plex doesn't seem like a good fit for books and comics. The first major hurdle is the lack of a singular metadata source that Plex can hook into for metadata - although this year has shifted with Hardcover and MangaBaka. Plex also uses a filename parsing mechanism (like Kavita does) which has drawbacks since books and comics have an extremely wide variety of naming conventions and lack of good tooling.
Thanks for this. First I've heard of it. I'd prefer something more general for books (though there are comics too). I have about 22,000 titles, filenames well-constructed, that I don't have anything to serve them up remotely. I was using Nextcloud for awhile, but it's subpar.
>which has drawbacks since books and comics have an extremely wide variety of naming conventions
I actually have that part figured out. For periodicals too, like comics. The real trick with those is that it's often not that easy to find the ISSNs for them, they mostly don't list them on the inside cover.
idk about a house party once a week, but I do like the idea of having my friends invite their other friends. As I age, it becomes harder to find new friends just by happenstance. Friends of Friends usually end up becoming friends after meeting them.
It doesn't have to be a whole-ass house party, but a good low effort method is picking a tv series, putting out some snacks and watching an episode at the same time every week with an open door policy.
That's interesting, 4.6 is finally when AI started to become good in my eyes. I have a very strict plan phase, argue, plan then partial execute. I like it to do boilerplate then I do the hard stuff myself and have it do a once over at the end.
Although I have had it try to debug something and just get stuck chugging tokens.
reply