Daniel F

You can still run the group check and include the necessary js/css files, or set the JS variables only when it’s needed.

That said, you can also use always JS and CSS to manipulate the output.

Since it's a Raffle item, where you're in control of the class, you can do whatever you want with the menu.
But for other applications, where you'll have to use the UIItem Extension, you're able to place it at the beginning or end

Since it's a Raffle item, where you're in control of the class, you can do whatever you want with the menu.
But for other applications, where you'll have to use the UIItem Extension, you're able to place it at the beginning or end

That said, you can also use always JS and CSS to manipulate the output.

Yea, it's already in the Content\Item and Content\Comment class, you'll just call it in your template or override the method in your content class if you want to add something own.

Yea, it's already in the Content\Item and Content\Comment class, you'll just call it in your template or override the method in your content class if you want to add something own.

It depends on what you’re trying to achieve, but devs can indeed to do a lot with help of GraphQL, REST and webhooks.

The capability to change how most stuff in IPS works and enhance it with own features/apps isn't going away.
What changed is how things have to be done. Some changes will be much easier, others will be probably annoying as hell for people who are used to how the hooks worked in v4, some will think that it is a huge step backward, but as Matt said, it had to be done, to provide a much more stable and faster-improving code base for v5, because we'll be able to alter or even deprecate methods, method parameters and even deprecate complete (internal) classes much faster, which also 3rd parties and clients will benefit from.
With v5 I'm really expecting fewer "A new community release with some huge under-the-hood BC breaking changes is here, all my apps are now broken and need to be updated ASAP" scenarios.
 
Code listeners are a quite common pattern used in modern applications, most php framework use this approach today. It's the perfect balance between none capability to change the core behavior via 3rd party code and the too-powerful proxy autoloader which we had in 4.x, which as powerful as it was, had also way too many problems.
I've read about concerns about missing event locations which were common in v3 and that it took ages to have new hooks implemented => Keep in mind that we have now a monthly release cycle, so I'm quite sure it's not going to take now that long to ship improvements as long as they make sense and fit into the general vision of the product.

The capability to change how most stuff in IPS works and enhance it with own features/apps isn't going away.
What changed is how things have to be done. Some changes will be much easier, others will be probably annoying as hell for people who are used to how the hooks worked in v4, some will think that it is a huge step backward, but as Matt said, it had to be done, to provide a much more stable and faster-improving code base for v5, because we'll be able to alter or even deprecate methods, method parameters and even deprecate complete (internal) classes much faster, which also 3rd parties and clients will benefit from.
With v5 I'm really expecting fewer "A new community release with some huge under-the-hood BC breaking changes is here, all my apps are now broken and need to be updated ASAP" scenarios.
 
Code listeners are a quite common pattern used in modern applications, most php framework use this approach today. It's the perfect balance between none capability to change the core behavior via 3rd party code and the too-powerful proxy autoloader which we had in 4.x, which as powerful as it was, had also way too many problems.
I've read about concerns about missing event locations which were common in v3 and that it took ages to have new hooks implemented => Keep in mind that we have now a monthly release cycle, so I'm quite sure it's not going to take now that long to ship improvements as long as they make sense and fit into the general vision of the product.

I was just curious to know if most people just use the base IPS with the official apps and don't care about using third party apps/plugins.
That is indeed an advantage. And third party developers will also save some trouble because there is less risk of new IPS version breaking their apps.
If it's something that needed to be done, i guess we will all survive like it happened in the past with other major changes.

The capability to change how most stuff in IPS works and enhance it with own features/apps isn't going away.
What changed is how things have to be done. Some changes will be much easier, others will be probably annoying as hell for people who are used to how the hooks worked in v4, some will think that it is a huge step backward, but as Matt said, it had to be done, to provide a much more stable and faster-improving code base for v5, because we'll be able to alter or even deprecate methods, method parameters and even deprecate complete (internal) classes much faster, which also 3rd parties and clients will benefit from.
With v5 I'm really expecting fewer "A new community release with some huge under-the-hood BC breaking changes is here, all my apps are now broken and need to be updated ASAP" scenarios.
 
Code listeners are a quite common pattern used in modern applications, most php framework use this approach today. It's the perfect balance between none capability to change the core behavior via 3rd party code and the too-powerful proxy autoloader which we had in 4.x, which as powerful as it was, had also way too many problems.
I've read about concerns about missing event locations which were common in v3 and that it took ages to have new hooks implemented => Keep in mind that we have now a monthly release cycle, so I'm quite sure it's not going to take now that long to ship improvements as long as they make sense and fit into the general vision of the product.

1. You should all cool down and wait for the upcoming news and also the final product before getting in such a  panic rage.
2. Please see my reply in the SEO topic:
3. See the first point. We're listening to feedback and implementing changes based on it, just like Esther and Matt implemented changes today based on the provided feedback.
4. I think you're all way too scared.
There's still so much that can be done, it's 2023, and there are other ways and solutions than to edit files..
ALPACAS! I'll repeat very very slowly just for you: AL PA CAS

1. You should all cool down and wait for the upcoming news and also the final product before getting in such a  panic rage.
2. Please see my reply in the SEO topic:
3. See the first point. We're listening to feedback and implementing changes based on it, just like Esther and Matt implemented changes today based on the provided feedback.
4. I think you're all way too scared.
There's still so much that can be done, it's 2023, and there are other ways and solutions than to edit files..
ALPACAS! I'll repeat very very slowly just for you: AL PA CAS

1. You should all cool down and wait for the upcoming news and also the final product before getting in such a  panic rage.
2. Please see my reply in the SEO topic:
3. See the first point. We're listening to feedback and implementing changes based on it, just like Esther and Matt implemented changes today based on the provided feedback.
4. I think you're all way too scared.
There's still so much that can be done, it's 2023, and there are other ways and solutions than to edit files..
ALPACAS! I'll repeat very very slowly just for you: AL PA CAS

1. You should all cool down and wait for the upcoming news and also the final product before getting in such a  panic rage.
2. Please see my reply in the SEO topic:
3. See the first point. We're listening to feedback and implementing changes based on it, just like Esther and Matt implemented changes today based on the provided feedback.
4. I think you're all way too scared.
There's still so much that can be done, it's 2023, and there are other ways and solutions than to edit files..
ALPACAS! I'll repeat very very slowly just for you: AL PA CAS

1. You should all cool down and wait for the upcoming news and also the final product before getting in such a  panic rage.
2. Please see my reply in the SEO topic:
3. See the first point. We're listening to feedback and implementing changes based on it, just like Esther and Matt implemented changes today based on the provided feedback.
4. I think you're all way too scared.
There's still so much that can be done, it's 2023, and there are other ways and solutions than to edit files..
ALPACAS! I'll repeat very very slowly just for you: AL PA CAS

Not sure about your first example, but the "Delete All System Logs Button" won't be a problem at all!
As Matt or Esther said, just wait for our further blog entries, especially about the new UIExtensions

I have updated the dev guide with some additional information, so any 3rd party devs which are interested into utilising this in their applications and plugins should already be able to implement this on their own to have it ready once 4.6.10 is here