ePrivacy talks about "information stored in the terminal equipment", which includes any information you can get from the device. For example the user agent, location, and operating system. It's not about the information itself being essential or not, but what you do with it: is it for essential purposes (consent not needed) or non-essential purposes (consent needed).
Yes: the location information on the browser. You cannot access it for non-essential purposes without user consent. See
Article 5 / Statement 3 in the ePrivacy directive[1]
The eDirective states that the browser and device information (like the URL) is private data and you need a permission to access it for non-essential purposes such as analytics. This is why Simple Analytics also needs a cookie banner, contrast to what their marketing says.
Really curious to hear your findings! We're happy users of Badger, but we have never looked it's internals. I guess you can list the differences you've found without using a bad mouth. Thanks in advance.
https://volument.com might be a good pick since it focuses strictly on conversion optimization. It attempts to measure the more general conversion flow, known as the AIDA funnel (awareness, interest, desire, and action).
This feels like a response from a seasoned backend engineer. Seasoned frontend developers value user experience and design — thus the tendency to go "back to static" and rarely back to WordPress.
Hey, we at Volument (volument.com) are using Redis as the primary datastore. We are extremely happy we chose that option. It gives us everything we need: extreme performance, scalability with customized sharding, stability with sentinels, and most importantly: a fantastic data model that is enjoyable to work with. We don't need to add anything extra to our stack if we later need a pub/sub system or realtime support for our custom chat app for example.
We use a custom Go-based system to collect the crazy amount of analytics that easily exceeds our memory, but for the core business logic, Redis is a top-notch choice. We actually build our whole CRM on top of Redis: https://volument.com/blog/the-power-of-simple-crud
True. However, according to "The State of JavaScript" [1] Jest is the most popular option these days and it is chosen because it is simple, lightweight, fast, and easy [2] — all of which are the reasons one would choose Baretest.
Good points. Just want to point out that comparing with a basic "sum" function measures the performance of the test runner and leaves out the time it takes to run the application code. Baretest has little overhead so it is good for testing the actively developed code with the `only` function.
With Baretest all the custom things you do like transpiling TS or rendering React is done outside the test runner. This way it can test cases of any complexity.