Mastodon Feed
Reblogged by fromjason ("fromjason.xyz 🖤"):
NickAEsp ("Nick Espinosa") wrote:
Yes, Your Phone Mic IS Listening!
#News #TechNews #Technology #surveillance #PrivacyMatters #Facebook #Google #Amazon #Meta
Mastodon FeedMastodon Feedpzmyers@octodon.social ("pzmyers 🦑") wrote:
My day went splat, literally.
https://freethoughtblogs.com/pharyngula/2024/09/04/an-unusually-long-day/
Attachments:
Mastodon Feedfromjason ("fromjason.xyz 🖤") wrote:
Who are your favorite #bloggers?
Drop their names and web addresses ⬇️
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
@owa So if you want a future where HTML doesn't suck and where the warts in Web Components get ironed out and where we might be able to take on platform-backed data binding or SVG-custom-elements, then you need to support @owa.
Apple has continually demonstrated that it is functionally anti-web, including up to the present moment. The only solution is true competition.
I wish it wasn't so.
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
@owa All of this adds up to an assumption by competitors that Apple isn't up for expanding the web to solve important needs that come from frequent developer requests. The *massive* gap in capabilities that Cupertino maintains is just as apparent in DOM and HTML as in advanced features. They *still* won't implement `is`, and `elementInternals` was trench warfare.
It's painful to really push on expanding HTML and web capabilities because Apple will fight it at every step. And everyone knows it.
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
@owa But I'm sure that Apple spending more to defeat browser engine choice than to engage with developers [1], while materially misleading regulators [2] and leaving critical features in a totally broken state [3] and failing to keep pace in general [4] is just a giant misunderstanding. Could happen at any megacorp that makes $20BN/yr skimming off the web!
[3]: https://webventures.rejh.nl/blog/2024/web-push-ios-one-year/
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
Apple understands that the web is a reach platform, and that its Achilles heel is a failure to deliver everywhere. Maintaining a hard cap on web capabilities is strategic.
If developers could just build a single compelling experience from a single code-base, they wouldn't need Apple's distribution channel, which would mean they wouldn't need to pay Apple taxes.
And this is why Apple's fighting @owa tooth and nail, going as far as to fund astroturf "developer" groups and mislead regulators.
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
Because competitors know they can't ship new features to the wealthy developers and decision-makers that user the iOS products with their badges on the bonnet, the incentive to deliver new capabilities to developers on other platforms deflates.
Again, for Apple, this is working as intended. And they don't even have to put that much of a thumb on the scale. All they have to do is to "just ask questions" in standards conversations; muddy the waters in public and defuse progress in private.
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
The last point is really insidious: Apple and the Android team really, *really* wanted to keep the web from disrupting the cozy mobile duopoly, and through interlocking and reinforcing moats have made it nearly impossible for the web to break out and challenge the app store and native frameworks.
This is working-as-intended. Apple's attempt to kill PWAs earlier this year showed intent, and the fallback position they've taken since (that they don't have to open them up) is indefensible.
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
Folks are surprised to learn I put as much, or more, blame for the terrible state of frontend today on browsers as I do the JS community.
Browser vendors failed to put their money where their mouths have been on performance, paving endless open field to create induced demand with every JS engine tweak, rarely stopping to ask if what they have done has actually lifted the average.
Also, the last 15 years of neutered engine competition (thanks, iOS) has lowered vendor ambition for the platform.
Mastodon FeedReblogged by fromjason ("fromjason.xyz 🖤"):
molly0xfff@hachyderm.io ("Molly White") wrote:
The Internet Archive lost its appeal in the Hachette case. What a huge, devastating loss for all of us.
Mastodon FeedReblogged by fromjason ("fromjason.xyz 🖤"):
nixCraft ("nixCraft 🐧") wrote:
The Internet Archive Loses Its Appeal of a Major Copyright Case https://www.wired.com/story/internet-archive-loses-hachette-books-case-appeal/ Next, all AI companies should also lose access to copyrighted books and art. Why are tech bros allowed to breach copyright? The law should be applied equally to all.
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
@heydon And, indeed, we can see that even a *very mild* price on UI latency -- via the extremely generous INP thresholds that went into effect earlier this year -- are proving to be more than the "DX" narrative bait-and-switch can handle. If a breeze that gentle can topple your whole roadmap...maybe there wasn't anything there?
The whole sociotechnical edifface *can*, for most classes of site, be a hollow promise devoid of additive value.
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
@heydon It absolutely *is* the case that path dependence and unpriced externalities have caused important sections of the economy to fundamentally destroy value relative to what they "create"!
Accounting tricks can make bad things look good for a long time. It's *entirely possible* that the net net of the last decade's over enthusiasm for JavaScript has been more costly than it has been valuable.
Which is to say, you do not have to accept that popularity == value.
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
Multiple times since @heydon's epic React video dropped, I've had conversations that have bottomed out at *"yeah, well, lots of people choose React, so it must be popular for a reason"*.
This is true! It can be popular for *many* reasons! Nothing about this acknowledgement requires stipulating that those reasons be *good* or based on complete information.
If Eugene Fama can acknowledge that Efficient Markets don't actually exist, so can you.
Mastodon FeedReblogged by fromjason ("fromjason.xyz 🖤"):
molly0xfff@hachyderm.io ("Molly White") wrote:
People have gotten so used to the existence of the Internet Archive’s web archive that they forget how revolutionary and subversive it is. The idea that that is somehow safe while the book lending was not is completely flawed. They were just up against a more powerful group.
Mastodon FeedReblogged by fromjason ("fromjason.xyz 🖤"):
timnitGebru@dair-community.social ("Timnit Gebru (she/her)") wrote:
louis@indieweb.social
for harassing anyone who describes Israel as the genocidal, apartheid, colonial entity that it is, and describing the type of election interference & harassment by AIPAC on Israel's behalf, mostly against Black congresspeople, as antisemitic, and targeting accounts that do so for mass reports, suspension and harassment.
See thread👇
https://dair-community.social/deck/@egg@kolektiva.social/113070659317824474
Mastodon Feedisagalaev ("Ivan Sagalaev :flag_wbw:") wrote:
I liked this leveled, informed explanation of the difficulties around gendered pronouns https://www.youtube.com/watch?v=Kh22m1QG6i4
Mastodon Feedslightlyoff@toot.cafe ("Alex Russell") wrote:
Stop defining "developer experience" as "the inner loop while I'm writing code after spending an hour installing node_modules".
Setup time is "developer experience".
Upgrade toil is "developer experience".
Memoise-everything-after-weeks-debugging-stray-rerender toil is "developer experience".
Belated, frantic code splitting side quests are "developer experience".
Mastodon FeedReblogged by cstanhope@social.coop ("Your friendly 'net denizen"):
rek@merveilles.town ("R E K") wrote:
"The productivity myth suggests that anything we spend time on is up for automation — that any time we spend can and should be freed up for the sake of having even more time for other activities or pursuits — which can also be automated. The importance and value of thinking about our work and why we do it is waved away as a distraction. The goal of writing, this myth suggests, is filling a page rather than the process of thought that a completed page represents."
Mastodon FeedReblogged by cstanhope@social.coop ("Your friendly 'net denizen"):
testobsessed@ruby.social ("Elisabeth Hendrickson") wrote:
It just occurred to me that the phases in waterfall software development could just as well have been named after the stages of grief:
1. denial (requirements and design)
2. anger (implementation)
3. bargaining (functional testing)
4. depression (alpha & beta testing) and
5. acceptance (release)
Mastodon Feedpzmyers@octodon.social ("pzmyers 🦑") wrote:
Is the third week of the semester too early to burn out?
Mastodon FeedReblogged by fribbledom ("muesli"):
Interesting. According to Brent Spiner (the actor who plays the android Data in Star Trek: The Next Generation)
it was Patrick Stewart's UK pronunciation of his character's name (day-tah instead of the US's dah-tah) that made this pronunciation canon, and
the character of Data and the popularity of Star Trek has led to "day-tah" now being the common pronunciation in the US, too.
https://youtu.be/xeqTMTOxid8 (π min)
#StarTrek #StarTrekTNG #TNG #data #pronunciation #English #EnglishLanguage
Mastodon FeedI mean, what else would a PORtable moNITOR be called?
via @qbi
Attachments:
Mastodon FeedReblogged by keul@fosstodon.org ("Luca Fabbri"):
lukito@gamedev.lgbt ("Lukito") wrote:
“We created a self-opening fridge with an AI camera that tracks what you put in and take out.”
Please for the love of any and all deities I am PROSTRATE on the floor begging you for fair energy prices and accessible public transport I do not need a fridge incorrectly guessing what is in my 17 Tupperware containers and refusing to open because I haven’t paid my monthly £24.99 subscription of “Fridge Door Lock Plus” :neofox_melt_sob: :neofox_melt_sob: :neofox_melt_sob:
Mastodon Feedcstanhope@social.coop ("Your friendly 'net denizen") wrote:
Starting my morning with a bit of silliness and a good beat. "The Time Machine (Dr. Evil Trance Mix)":
Mastodon Feedjsonstein@masto.deoan.org ("Jeff Sonstein") wrote:
and please tell me again how they are classified a 501c(3) tax exempt non-partisan organization??
https://www.theguardian.com/us-news/article/2024/sep/04/christian-election-poll-workers
Mastodon Feedjsonstein@masto.deoan.org ("Jeff Sonstein") wrote:
seems reasonable
Mastodon FeedFirefox will reconsider supporting JPEG XL if they get a Rust implementation:
https://github.com/mozilla/standards-positions/pull/1064
This is a very good news for web standards:
https://mastodon.social/@kornel/113078862354601952
and will fix a blocker that is hurting adoption of JPEG XL.
The reference implementation has unfortunately been written in C++ just as browser vendors started looking into migrating away from C++ for security reasons, and saw the C++ codec primarily as a big new attack surface.
Mastodon Feed#WebStandards need two independent implementations of every feature.
This proves that the spec is actually possible to implement, and makes it possible to verify that the implementations are interoperable.
It makes uses in the wild much less likely to depend on bugs in a particular implementation, which makes it possible to upgrade or replace implementations without creating painful bug-compatibility problems.