• 1 Post
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle


  • First, persistency. You data lifecycle may not be directly proportional to your applications lifecycle. You may need it even after the app is shut down.

    Second, RDBM systems provide a well defined memory/storage structure and API - “structured query language”. This enables you to easily query your data and acquire suitable views that are beneficial for your applications purposes.

    Third, It’s always better to outsource your data layer to a battle tested, and trustworty database then trying to reinvent the wheel.

    So this paves a road for you to focus on your business logic than splitting that focus for the data layer and business logic.


  • I see that the problem arises from the "visionary, but lower experienced newer developers (compared to the past generation) " trying to fix a world where “don’t touch it if it works crowd who has seen all old timers” built, by putting each layer over the older one. It has all the capabilities, but there is no “single vision”, no “well defined api”.

    Old established paradigms are being broken. Some conventions are forgotten, new tooling and perspectives are being built.

    Sure this means there is an unfortunate clash is happening.

    I can’t say if this is a better, or wiser world or not, however I can only say this is the way now. You can adapt, try to embrace and push forward things or you can try to stay away and become one of the legendary Cobol developer crowd. We know they are there in the wild, but we can’t find them.




  • That’s really unfortunate and a bad service provider for you. If there is nothing that can be done for that service, you don’t need to use that browser as a daily driver, but can just use for the services that you mention. And you need to keep nagging the service provider for support.

    This is not just a browser war. It’s a war over your rights, your control over your choices, your privacy, what software and hardware you can use. You are already feeling how that affects your life daily, consider this in a mass attack on you.

    WEI will enable service providers to decide what firewall you can use, what addons you can have, what version of the browser you can reach their websites, what antivirus software that you need to have, what cpu architecture, which tablet … This list can go on.

    sure this won’t start in this manner right away. But I can assure you it will evolve towards more control service providers have on you.














  • I rechecked the current spec. It does not fully cover what a user agent can ask to the attestor ( “content binding” to be defined). So we can assume this attestation spec is defined at the attestor.

    Of course this does not mean attestor can not have different profiles to attest for.

    So your comment even though is possible, just not defined yet. Which we can - I believe - rightfully assume will be in the final spec or implementation.