3 ms·
They're nearly unreadable on desktop, too. The prose is incomprehensibly jargon-heavy, I literally have no idea what it's talking about.
by SwellJoe 6mo ago
They're nearly unreadable on desktop, too. The prose is incomprehensibly jargon-heavy, I literally have no idea what it's talking about.
- david_p 6mo agoI feel the same. I have no idea what “CDP” and “WAF” means in this context. I feel awkward about all this probably-LLM-generated prose that does not respect me enough as a reader to explain acronyms and give context.
- BandButcher 6mo agohate to tag along on this take but i agree "...browser automation framework..." was about all i understood and even then it had me guessing if it was talking about an alternative e2e testing framework like cypress, selenium, playwright.....and somehow I was right lmao (i think?) but literally all the other jargon there had me stumped. I'm still afraid to google a getParameter(0x9245) probe Likewise, the text does come across to me as LLM heavy (with a spice of pizzazz), but even as a dev who uses playwright I doubt I would change after seeing this. To OP: not convincing enough. Maybe this is targeted towards super users who are deep in the weeds of various browser automation framework internals. A better marketing approach towards someone like me who just uses this to test my apps e2e and be done with it, would be to have simple cliches like: "10x faster than playwright", "Same API", "Did we mention....SUPER FAST!?" I might call bs on that, but I'd be more likely to try it out.