363 private links
Des fichiers .http normalisent les appels d'APIs
A way to document a web component (an element manifest per web component).
The first release!
This seems to be a new version.
A Swiss-army app for developers
Project: https://github.com/skatkov/devtui
PNG renders top to bottom but the interlaced mode increase significantly the file size. WebP too at 28%.
AVIF has a progressive flag for it. It creates two layers. One at 1/8th resolution and minimum quality and one at full resolution and good quality. The first layer has 5.8kB as example, and the full image is 151kB. It's still experimental with avifenc.
JPEG XL (abbreviated JXL) renders on Chrome at 39% of the file.
The AVIF image provided as example is 56.4kB, which is incredible for a more than HD image.
For many images, there's little benefit to progressive rendering (the fox with many details is an exception). So progressive rendering is often a mix of good and bad luck.
The author claims JXL progressive rendering promises won't work, because there is a significant lag between each of the progressive rendering steps. It can work efficiently with srcset for example.
JXL still looks promising, but the AVIF progressive rendering of the fox is somewhat better than the 17-27kB alternative of JXL.
Note: a post-processed blur on a scaled down image results in 2kB. 10kB makes the image "acceptable" for the human eyes. The image is still pretty good for previews. The post-process blur would need to be part of the format, rather than left to something like CSS to make JXL.
and because it's an entirely separate image, the decoding overhead is zero if the browser doesn't see a benefit to displaying the preview. As in, in cases where the browser has the whole file, it can just skip the preview.
I will have to look after the AVIF format, because it seems to be the best of Webp (20-30% better compression), GIF (with animation) and better image quality than JPEG.
See the german wikipedia page or the english one
If JS fails to load, a keyframe remove the effect provided by JS in 2 seconds.
I totally agree.
If you complain that you have a problem with #Windows
and are unhappy that people on Fediverse always bring up #Linux
when you come here to post your complaint, I have a question: instead of here, have you tried the #Microsoft
support or forums?I mean at some point the "I just want Windows to work" is a fair and understandable point, but it will just be shouting in the wind if you don't bring your complaints to the people and company making it.
And I say that as an IT tech, I know how it works: if there's no support ticket about a problem, there's no feedback proof, and therefore the problem officially doesn't exist.
EDIT: to be very clear, I'm not writing all this with the intent of presenting MS forums and support as the best way to solve your problems with their products.
It's more that, as someone who deals with how tech support is handled on a daily basis, as I mentioned above, companies have processes for all that, and I can guarantee you that when it comes to handling feedback, they follow them strictly, especially when it comes to being held accountable for unwanted features or overall problems.
Users are being unhappy with ads or AI features and complain they can't deactivate them all? "Where are the tickets at our support to back that up?" is gonna be their answer. And we all know most of us, most of the overall user base never bother with that, leaving the gates full open for Microsoft to be like those aren't issues for the majority of users.
If windows is so problematic, then GNU/Linux can be the solution
Qu'est-ce qui est le plus embêtant en arrivant sous linux?
A) 4% Le changement d'interface
B) 59.4% Le manque de support pour Photoshop ou autre application spécifique
C) 11.6% Le rapatriement des données (contacts, favoris, etc...)
D) 25% autres
En autres, on retrouve:
- le passage à la ligne de commande
- pression sociale: Télématin n'en parle pas, le vendeur expert de chez Darty y connaît rien, le tuto ne marche pas sur Linux. La personne se retrouve illégitime et en insécurité par pas compétente.
The return value is unclear:
- The old API treats zero as false (parameter not handled)
- The new API expects an error code (zero is success).
- To add some fun, any non-zero result is passed to ERR_PTR() and used as a pointer for further parsing. Well, (char*)1 is neither IS_ERR_OR_NULL() nor a valid pointer…
:root {
--w: calc(100vw/1px); /* screen width */
--h: calc(100vh/1px); /* screen height */
/* The result is an integer without a unit! */
}A version with better support:
:root {
--w: calc(100vw/1px); /* screen width */
--h: calc(100vh/1px); /* screen height */
/* The result is an integer without a unit! */
}Microsoft Teams führt demnächst eine Funktion ein, die automatisch den Arbeitsort von Mitarbeitern über die Büro-WLAN-Verbindung verfolgt.
- Use longer passwords
- Drop complexity requirements
- No more forced password resets
- Maintain a password blocklist
- Eliminate security questions and hints
- Use modern security tools (MFA, password managers)
Un pastiche sur l'argumentaire en faveur de l'IA.
Un autre commentaire similaire à propos du fast-food: https://mamot.fr/@krazykitty/115428219040400965