El Corralito del 2001 y la Burbuja Hipotecaria del 2008. ¿Alguien de verdad va a defender a la casta bancaria? Son unos delincuentes del primero al último.

Preferiría salir a robar antes que ser controlado por ellos. Así de simple.

#Bancos #Finanzas #BreakingChanges #Crypto #SatoshiNakamoto

Nextcloud v33.0.0rc4 is out! Get ready for Nextcloud 33, but remember this RC is for testing new features & finding bugs. Not for production! Expect potential #BreakingChanges.

More info: https://github.com/nextcloud-releases/server/releases/tag/v33.0.0rc4

#selfhosted #homelab

Neuer Artikel im Blog:

TYPO3 v14: Asset-Handling wird schlanker – Was sich für Integratoren ändert

https://wwagner.net/blog/a/typo3-v14-asset-handling-wird-schlanker-was-sich-fuer-integratoren-aendert

#TYPO3v14 #BreakingChanges #WebPerformance

TYPO3 v14: Asset-Handling wird schlanker – Was sich ändert

TYPO3 v14 entfernt Asset-Concatenation und HTTP Response Compression. Was sich ändert und welche Alternativen besser sind.

React-like functional webcomponents, but with vanilla HTML, JS and CSS

Introducing Dim – a new #Framework that brings #ReactJS-like functional #JSX-syntax with #VanillaJS. Check it out here:
🔗 Project: https://github.com/positive-intentions/dim
🔗 Website: https://dim.positive-intentions.com

My journey with #WebComponents started with Lit, and while I appreciated its native browser support (less #Tooling!), coming from #ReactJS, the class components felt like a step backward. The #FunctionalProgramming approach in React significantly improved my #DeveloperExperience and debugging flow.

So, I set out to build a thin, functional wrapper around #Lit, and Dim is the result! It's a #ProofOfConcept right now, with "main" #Hooks similar to React, plus some custom ones like useStore for #EncryptionAtRest. (Note: #StateManagement for encryption-at-rest is still unstable and currently uses a hardcoded password while I explore #Passwordless options like #WebAuthn/#Passkeys).

You can dive deeper into the #Documentation and see how it works here:
📚 Dim Docs: https://positive-intentions.com/docs/category/dim

This #OpenSource project is still in its early stages and very #Unstable, so expect #BreakingChanges. I've already received valuable #Feedback on some functions regarding #Security, and I'm actively investigating those. I'm genuinely open to all feedback as I continue to develop it!

#FrontendDev #JSFramework #Innovation #Coding #Programmer #Tech

GitHub - positive-intentions/dim

Contribute to positive-intentions/dim development by creating an account on GitHub.

GitHub
PHP Composer arī kaut kad jau atjaunosies #BreakingChanges
The way we're thinking about breaking changes is really silly

A major problem plaguing modern compilers is that they have no concept of time. When run on a codebase, a compiler treats it as if it had been in the exact...

welltypedwitch
Does this mean the author isn’t ready to commit to the current API and behavior? Should we expect #breakingchanges? And do the version numbers mean anything at all? Do they have a proper #releasestrategy? After version 1.0, it’s time to be responsible. Your users or developers depend on stability. First, choose a #releasestrategy—will you adopt regular releases, or only push new versions when necessary? (cont'd)

Should new warnings (logs or actual warnings) emitted given the same previous contents (user code/docs didn't change) be considered a breaking change?

https://github.com/mkdocs/mkdocs/discussions/3818

#python #mkdocs #breakingchanges #warnings

Yes
30%
No
50%
Depends
20%
Poll ended at .
Warning logs and strict mode · mkdocs mkdocs · Discussion #3818

Since many (if not most) users of MkDocs use strict mode (locally or in CI) to assert there's no issue within their docs, when a plugin updates its logic to emit more warnings given the same previo...

GitHub

@shom
So it sounds like "Installed Web Apps" or Web Apps you add to your home screen are now breaking in #Apple 's next #iOS #beta

I use #Printables , #OpenAI , #Octopi, my #Asus Router, #Facebook, and #CommonSenseMedia apps this way.

#BreakingChanges

.NET platform is considered to be stable platform but from version to version there are changes that are considered a breaking ones. When updating to the new version do you check what are the changes that might impact your project or just update & YOLO? I do remember one case, long time ago that updating to .NET Framework 4.6 caused a lot of issues and resulted in digging through documentation and framework source code finding that one switch that could revert back to the old behavior - Switch.MS.Internal.DoNotUseCulturePreservingDispatcherOperations.

#dotnet #breakingchanges