This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-12
Channels
- # adventofcode (49)
- # announcements (22)
- # beginners (33)
- # calva (5)
- # clj-kondo (6)
- # clojure (30)
- # clojure-europe (6)
- # clojure-japan (1)
- # clojure-nl (9)
- # core-logic (17)
- # data-oriented-programming (1)
- # datalevin (1)
- # datomic (2)
- # gratitude (2)
- # jobs (2)
- # kaocha (8)
- # lsp (1)
- # malli (8)
- # meander (8)
- # off-topic (18)
- # rdf (1)
- # re-frame (4)
- # reagent (16)
- # releases (1)
- # sci (1)
- # sql (1)
- # tools-deps (4)
- # xtdb (3)
Is there any search engine where when you type in "XYZ" in the search bar, the first results are company XYZ"s website, rather than XYZ competitors bidding on adword "XYZ" ?
I know on Google you can search for ex: site: and results are limited as you'd expect. Not sure if/how this passes the adword test though.
So the F1 Season has concluded. No spoilers in the channel but go nuts in a thread here if you like
we're chatting in yesterday's thread
with spoilers :)
Given querying data that changes a browser clients UI should be triggered by the URL, when if ever, would you use react's use-effect hook? Is one question i'm pondering on as part of a larger st of issues. The bigger complication seems to be that a browser url is 2 things. 1. it points to a place in the browser application 2. it declares a query to a server that needs to be fulfilled. This would seem to imply the browser is just a cache of the data to be fetched, but it's not. which is likely why the added complexity, because the browser app is more then the data model it's relying on. But maybe we could design in a way such that the divergence was more obvious and when they are aligned there is less friction? I was watching Rich's talk "are we there yet" and trying to fit his concepts of time progression onto the browser client and server relationship in some way.
> it declares a query to a server that needs to be fulfilled.
There are applications where that's not the case - when you don't care about SSR and SEO, your server can respond with a blanket index.html for all requests and it's your SPA that would then make sense of that URL.
I believe this ties into it having two roles. If the url isn't significant one or the other of the items listed i would be curious how its being used.
It is significant - just not to the server. The UI decides what to do with the URL.
The URL sometimes can be too poor an abstraction to put all the apps state inside. Also a state machine might also need the transition data on top of the next state. Most advanced SPAs will be extremely cumbersome to build with unidirectional flow.
Eg imagine a social app where you can hover on a username to see a status, profile pic etc, you have to fetch stuff on hover. Do you change the URL? Or do you just fetch as needed as an effect?
@U7PBP4UVA that's why i'm fascinated by it, because it seems to serve many purposes but none particularly well.
i have been waiting for a while that somebody woudl build a totally new user interface library based on canvas and it's 2d/3d graphics instead of flying with the old old html forever .... let's see how many more years š
accessibility is an issue there
good news. the future is nigh! ā¢ https://docs.flutter.dev/development/tools/web-renderers already supports rendering to canvas ā¢ If you're simply looking to dump html in favor of a more sane graphics/event model, check out https://github.com/lelandrichardson/react-primitives ā¢ Most game libraries can already support canvas in addition to other render targets My library, https://github.com/phronmophobic/membrane, can render to basically any medium that can draw shapes, text, and images. One of the built in renderers is for webgl canvas. @U02N27RK69K, I'd love to add renderers that optimize for accessibility, but I've had trouble finding resources to figure out what that would look like. I know there's https://www.w3.org/WAI/standards-guidelines/aria/ , but that seems mostly oriented towards a CYA approach to saying that your UI is accessible rather than actually building an accessibly usable UI. If you know of any good resources, I would love to check them out.
accessibility exists on a spectrum and applies to so many situations that it's hard to nail it down as just one thing. it's helpful to me to imagine if I had to rely on only keyboard for navigation, or if I had very limited or no eyesight, or if I couldn't hear, what can I do to the site to make it still accessible to me.