Any programming language these days should ship a decent rfc5234 API in the standard library, so you do not get these kinds of problems in slightly different fashion for each and every library/program.
448 karma · joined July 24, 2024
Any programming language these days should ship a decent rfc5234 API in the standard library, so you do not get these kinds of problems in slightly different fashion for each and every library/program.
To be fair, almost any form of one-on-one exchange looks really effective when you contrast it with the average badly-moderated, way-too-many-peoples-time-wasted-if-you-ask-questions, no-prepared-agenda, in-person meeting.
One contrast I find more impressive is the valuable advice I received from people.. already dead for years. Skipping possibly helping 2 or 3 additional novices, by instead spending that time on refining a quick reply to one person into a reusable misconception-untangling guide. Useful to 100 more, for years to come.
IMNSHO, if a company is not even encouraging such soft-skills via the easy pickings (like turning their buzzword-infested PR slopstream back into a proper technical weblog), they are not missing a key - they got too many locks confining available expert knowledge.
This meme needs to stop. Knowledge transfer from experts to novices is way too important to be left to chance. And thanks to pre-pivot StackOverflow we even have considerable data on how much better it can be done, at least for white collar industries. Reducing the effort of experts to give advice, and enlarging the audience benefiting from a singular effort to write it down is orders of magnitude better than chance.
https://apnews.com/general-news-801aa30308b24b459251c60d569d...
No pop-up is needed to reject what is already banned union-wide. Therefore, a banner that is trying to collect my explicit+specific+informed+voluntary consent to partially lift that ban is not a "pop-up that lets users reject". Its a "pop-up that lets users surrender" some of their rights & freedoms.
Nowadays with AI slop websites all over the place, plus formerly legitimate newspapers not attributing sources & edits either, this may not seem that special. But w3schools earned their reputation when that was exceptionally rude. Also, straight up wrong all over the place. But that is more of a symptom. And to be fair a lot of the software back then was straight up wrong, too. Tough job documenting the reality of the WWW correctly while IE was around.
Even better than any such marker: Rearranging so the acronym (e.g. LGTM, NAK, ASAP) or greeting/valediction is the last word, ticking off both the formalities and the EOM marker simultaneously.
I was looking for the x86-specific rant, and did not find it. You'd think that team would have had something to say about architecture complexity.
But also no: even if they spent years catching up they would not reach the level of not-sucking that .deb get without extra effort, as a result of decades of policy ossified into the supporting tools. Such as the strong expectation that apt deals with packages that can be (re)built from their declared inputs and share common build-essentials. Whereas snapcraft does not even provide the tools yet to easily rule out building from ephemeral inputs or merely-accidentally working rust versions.
secure enclaves, secure virtualization, trusted execution environment, trusted platform, confidential computing, protected execution, LaGrande, protected launch, hardware attestation, ..