Just want to add that the AT Protocol IETF working group has been formed, and the PLC directory independent organization and board has officially been established. I’m at the closing talk for this years Atmosphere Conference as I write this and it’s really an incredible community of devs.
I'm excited to see communities of developers working to build things that are meaningful and matter to regular people, which ATProto seems to have more of than some other ecosystems in decent tech land. And where else could you attend an awesome workshop on "Hospicing Social Media?"
the law in the UK doesn't require any of that. It didn't even required Apple to do it. Ofcom is praising Apple for doing it even though it was not required. Social Networks need to do it.
This UK law does not apply to OSes. It applies to online platforms. The author ran into this problem because using the iPhone required an Apple account, which could be used for something that the law applies to, but Apple didn't want to implement lazy verification and instead required verification up front.
That depends on if you live in a jurisdiction that lives or dies by free speech, and if it considers code speech[0]. Forcing you to implement age verification is effectively forcing you to speak things you don't want to say, which isn't free speech.
Apple has to do age verification because of dumb laws, but they decided to do age verification in a dumb way.
The author tried to go along with the age verification system with five different cards and failed five times. For an account that's older than the legal age that would need to be verified in the first place, mind you.
There are many ways to do age verification, most of them bad, but that's why most companies complying with these laws use multiple methods.
nevermind the apologist. his paycheck is paid by people that have capitulated to the same bullshit. and you know what they say about people learning lessons whom have a financial incentive not to.
Indeed. There has been zero political opposition to these laws. Apple isn’t going to pay the fines on our behalf, so we need to get organizing if we don’t like this.
ah, yeah; I guess organization looks like complete capitulation and then commenting on the effect elsewhere with a sturdy shrug "whatcha gonna do? we're all just so powerless". fighting the good fight.
ah, cool! great to have such a loyal ally that snark and cynicism wilts their enthusiasm to such an extent. how would we ever get rid of age verification laws without your "dropped at the first sign of someone not being nice to me" supportive commentary and shrugs?
Wasn’t that the Lit framework? It was okay. Like a slightly more irritating version of React.
I recall the property passing model being a nasty abstraction breaker. HTML attributes are all strings, so if you wanted to pass objects or functions to children you had to do that via “props” instead of “attributes.”
I also recall the tag names of web components being a pain. Always need a dash, always need to be registered.
None of these problems broke it; they just made it irritating by comparison. There wasn’t really much upside either. No real performance gain or superior feature, and you got fewer features and a smaller ecosystem.
The point of Lit is not to compete with React itself, but to build interoperable web components. If your app (Hi Beaker!) is only using one library/framework, and will only ever one one in eternity, then interoperability might not be a big concern. But if you're building components for multiple teams, mixing components from multiple teams, or ever deal with migrations, then interoperability might be hugely important.
Even so, Lit is widely used to build very complex apps (Beaker, as you know, Photoshop, Reddit, Home Assistant, Microsoft App Store, SpaceX things, ...).
Property bindings are just as ergonomic as attributes with the .foo= syntax, and tag name declaration has rarely come up as a big friction point, especially with the declarative @customElement() decorator. The rest is indeed like a faster less proprietary React in many ways.
Kind of? Lit does add some of the types of patterns I'm talking about but they add a lot more as well. I always avoided it due to the heavy use of typescript decorators required to get a decent DX, the framework is pretty opinionated on your build system in my experience.
I also didn't often see Lit being used in a way that stuck to the idea that the DOM should be your state. That could very well be because most web devs are coming to it with a background in react or similar, but when I did see Lit used it often involved a heavy use of in-memory state tracked inside of components and never making it into the DOM.
Lit is not opinionated about your build system You can write Lit components in plain JS, going back to ES2015.
Our decorators aren't required - you can use the static properties block. If you think the DX is better with decorators... that's why we support them!
And we support TypeScript's "experimental" decorators and standard TC39 decorators, which are supported in TypeScript, Babel, esbuild, and recently SWC and probably more.
Regarding state: Lit makes it easier to write web components. How you architect those web components and where they store their state is up to you. You can stick to attributes and DOM if that's what you want. Some component sets out there make heavy use of data-only elements: something of a DSL in the DOM, like XML.
It just turns out that most developer and most apps have an easier time of presenting state in JS, since JS has much richer facilities for that.
Dont get me wrong, I'm a pretty big believer in interop, but in practice I've rarely run into a situation where I need to mix components from multiple frameworks. Especially because React is so dominant.
Reactivity isn’t the problem. Reactivity is one of the few things that helps reduce the complexity of state management. GUI state is just a complex thing. Frontend development doesn’t get enough cred for how deeply difficult it is.
I mean, the competition isn't setting a high bar, between the guy complaining about 'white people not having a homeland' and the other guy peddling addictive stuff to teens and AI slop to their grandparents.
That said, I have genuinely been enjoying Blue Sky. It has 'enough' for me. There are a bunch of YIMBYs and urbanists. The mayor of my city and one of my city councilors are there. There is starting to be a bike racing community. There are some good local journalists.
I read your other comment; I hope your optimism is warranted.
reply