You can imagine a version of the world where designers structure their designs in a way that can easily export to e.g. a vue component, and along with the base structural layout they define different UI states it can be in, with animation timelines. Designers should be able to specify every aesthetic variable, and developers just program the business logic to fill content tags and toggle designer-defined states.
You’re probably already aware of it, but for generative design tool inspiration check out Grasshopper. It’s for building geometric algorithmic designs based on various inputs and constraints. It also has some tools for exploring permutations / genetic algorithms.
I'm confused. For me, a major selling point of DoH is it hides DNS queries from your ISP, which has detailed personal information about you. And if you're locked into Comcast, you're operating with completely eroded trust from the get-go.
Clearly, DNS statistics are extremely valuable to Comcast, or they would not have engaged with Mozilla to get back the data, nor would they have raised hell with Congress.
I would not have expected an organization like Mozilla to sign a data deal with Comcast, even if Comcast is now theoretically restricted on how they use the data.
Mozilla cannot enable one provider by default. People already complained that Cloudflare was initially the only choice.
Users at the moment are expected to choose their provider anyway.
This deal is about Mozilla picking Comcast by default for Comcast customers. This is essentially as if they'd be using the network's default, because Comcast is the network's default already, being what people get via DHCP.
They can always choose a different provider. And Mozilla apparently struck a privacy deal with them too.
I understand the arrangement. From a Comcast user’s perspective, very little has changed, depending on how much trust you assign to a “we promise” privacy agreement. Are Comcast users better off than default? Yes. But decoupling DNS from ISPs which sit in such a privileged position is, for me, 85% of the threat model.
I’d like to read more about how the choice will be presented to users, beyond about:config. I’d also like to understand more the community’s reaction to Cloudflare default.
What if there was a round robin setup between neutral operators? Pairing Comcast users to Comcast just seems like a wtf move.
It’s not guilt by association, it’s guilt by action. The action of deciding to work for the company with such a mission / clientele. Especially in a role requiring enough technical knowledge to know what’s going on.
I think CS, in that era, was free if you had a HL product key. It was a community mod and even when it transitioned to a boxed standalone product you could still download it if you had a HL key. CS: Source was also a free upgrade.
Uh, what? It’s changing the UI to hide parts of the URL.
Look, I’d prefer it the other way too, but we have to choose the right words. The thought process shouldn’t be “I’m mad, what else makes me really mad like this? Oh yeah social justice workers. This UI change is therefore like social justice work.”
If anything, there's, from my experience, a good overlap between the SJW types, and the people who push for accessibility/ a11y as the cool kids call it, as it sorta falls under the inclusion initiatives.
EDIT: I was clearly disagreeing with the parent badmouthing SJWs wrt accessibility...
No, you’re just assuming it is because it’s next to the word SWJ.
The parent's point is that someone who would self-identify or otherwise be described as SWJ would more likely push for greater accessibility to a fault rather than reduce it for aesthetic reasons. The attack on “SJWs” in the grandparent is misguided because it misunderstands their motivations so completely that it’s clear that the term is just meant as “people I vaguely don’t like and I feel have it out for me somehow.”
Thanks, at least someone got me! I was trying to call out randomly blaming people who, if anything, would be on their side, but it seems like most people misunderstood me.
AMP is just _bad_, IMO. Content regularly is broken till you visit the actual site, sites don't follow my dark mode preferences, and interactive elements don't translate that well sometimes.
It feels like someone printed out a website to a PDF and decided that was good enough to serve!
It’s a number of factors. School programs are biased against embellishment so there isn’t really a craft in the profession around those kind of stylistic detail, especially at graduate level. BIM software also plays a role. The trade is forever streamlining itself technically, and construction systems with their CAD part catalogs thin out selection. Depending on the development goals, throwback details may not fit with how they plan to market the building.
And pretty much all of the above contribute to added costs of perusing embellishment on the core and shell. Lack of design techniques, construction know how, and off the shelf options will drive prices up. Developers would prefer to spend money on interior build out because it sells sq footage.
