Fan of #rustlang? Read about how our sans-IO data plane architecture reliably powers Firezone's connectivity stack across all kinds of devices:
https://t.co/tb5ZDADr1w
@mitchellh@KagiHQ Same, I've switched a month ago and there is definitely less SEO spam and even results on rank 8+ are often interesting. I keep thinking "I would have never found this page on Google/DDG".
@nikomatsakis @rustlang The main reason for this are breaking changes: Opting in to previews as described in the blogpost means compilation breaks for my users. That is likely a no-go for anything > 1.x like tokio but probably also for many crates < 1.0 that already have an ecosystem (for example `log`)
@nikomatsakis @rustlang Similar to how `unsafe` stays contained, perhaps? To be honest, I would not use previews if it means my users have to opt-in to it too. I would want to experiment in isolation.
Happy to share that this week I successfully defended my phd thesis @WU_econ! And this is a great opportunity to say thank you: thank you to all of my collegues and friends at INEQ - especially to @nessilech & @EmanueIList 🥰
@LilithWittmann@TLKGillespie Aber AN und AG stehen doch jetzt schon in einem ungleichen Machtverhältnis. Klar hat es Mehrwert aber der wird höchstwahrscheinlich nicht dazu beitragen dieses Machtverhältnis fairer zu gestalten.
Basically what I'd want is:
$ ./test-runner --url=http://localhost:8080 --test=./tests/login-workflow.ui-test
Where `test-runner` will start the headless browser etc.
Does something like that exist?
What do people use for automated UI-tests of @htmx_org websites? Is selenium still the way to go? I liked Cypress but don't really want to go back to a JS stack again after I am finally getting rid of it with @htmx_org :)
Ideally, the test runner is language-agnostic to the backend language (currently Java) because I am planning to rewrite that too and would like to keep the tests.