Well these are well written security vulnerabilities with reproduction steps. It's hard to tell if it's an AI discovering or a user using AI to find issues. But suddenly, I'm having an influx of issues where-as for the past 5 years, I received maybe 5. Just this month, I've been hit with 5 low effort vulnerabilities (all very small, unlikely to expose anything of value).
But it's very hard to maintain these in addition to the release work.
I don't get what you're saying. You're frustrated that Open Source projects were used to build these AIs and that OS devs (or devs in general) are paying to use AI.
Then you say you had money that you used to donate(?) to OS and have cut that because of the frustration?
Open source just means sharing the source code for people to learn off or have the ability to customize on their own. I don't think there is any need to be frustrated about that (now if it was copyright/private of course).
What does "fast" even mean? I always see people talk about performance and wonder, what kind of applications are they building where they are seeing a massive gap in performance between frameworks?
I'm pretty sure in this late game, all the frameworks are more-or-less the same in terms of render performance. Angular has a lot of cool tricks (with these signals) that allow for only re-rending what changes.
Signals are a privative data structure in Angular, hence core. Signal-based forms are part of the Forms module. You aren't using forms, you don't get the overhead.
Really excited for this. I've been dying to use signal-forms and resources since they were experimental. Once I got on the signal train, I could never go back and having to use RxJS for forms became a major pain point.
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.
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.
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.
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.
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.
This is exactly what got me to actually pay. I had a side project with an architecture I thought was good. Fed it into Claude and ChatGPT. ChatGPT made small suggestions but overall thought it was good. Claude shit all over it and after validating it's suggestions, I realized Claude was what I needed.
I haven't looked back. I just use Claude at home and ChatGPT at work (no Claude). ChatGPT at work is much worse than Claude in my experience.
Now doing that with PDF would actually make it challenging.
Annotation system (with pics): https://wiki.kavitareader.com/guides/readers/epub/#annotatio...