When I've seen GA used or recommended to people, it's because their use case is tracking the marketing performance of their website.
Tackling the privacy focus for GA is great, but they're a good deal of products out there that already fill that niche, not to mention the requirements of the privacy crowd usually being a venture into itself.
If you wanted to make it relatively competitive for marketing, the simplest addition would be adding labelling via regex for referrers.
is from your live demo referrers, and makes it difficult to actually assess the amount of traffic from Baidu. Using a regex label means that users can break down traffic from Paid/Organic marketing fairly quickly, and start to build up dashboards they can use.
If you ever extended it to allow multiple labels for each hit, could re-run the regex over past data, and could build reports off it, you'd easily have a benefit over GA that would start to wean the marketing crowd off it.
Ran into this issue with a crate that uses CUDA in Rust - how do you hang onto the pointer to CUBLAS/CUDNN so that all CUDA functions use the same pointers and also it goes out of scope at the end of execution.
The big problem is the second part - lazy static doesn't allow you to run destructors, and this is one of the few times you really need a custom destructor to tell Rust to kill the CUBLAS/CUDNN pointers at appropriate times.
Ended up connecting it to a struct so that the destructor could be tied to the object rather than anything else, but lazystatic's (lack of) story around destructors definitely created a bunch of problems that weren't apparent until we started finding memory leaks.
Google Analytics has a fair amount of filtering by default - including bots/spiders.
Went to Plausible's website, it makes no mention of this type of blocking. That 13% could be eaten into significantly by removing that type of activity.
More convincing would be matching up activity across sites, and seeing for what sessions they differ. If this was a decrease in users who had significant sessions (>30 secs, for example), there'd be more meaningful conclusions to draw.
>Not totally related, but R has a great polymorphic dispatch of functions,
Dispatch in R is generally fine, but I see a great deal of UseMethod calls, and switch statements for types in the libraries I've worked with, which OTOH is just users using tools badly, but OTO R should enforce using a particular tool to solve problems. And R is particularly bad at enforcing anything, which is why we're left with S3, S4, and R6.
There's also the FFI issue across the board for Python/R where functions frequently barely clean naked FFI calls and leave it a complete mystery what's going on under the hood. I think R is generally worse at it though, where I've had memory leaks and sigterms that aren't visible in RStudio.
I do like the functional programming though. I had an excuse to use multi.argument.Compose from the functional library recently and it made me wish I had things like that to hand in all languages
I've heard this suggestion fairly frequently - that people use Rust as a wrapper over C++ bindings to add in safety to the C++ underneath.
Mostly regarding using BLAS etc in Rust rather than C++. It seems a little pointless as the unsafe nature is within the underlying code, so it only santises input/output.
"people use Rust as a wrapper over C++ bindings to add in safety to the C++ underneath."
Adding a thin wrapper over an insecure library won't magically make it secure. That's why pure Rust or pure Swift versions of various algorithms and functionalities are worth so much - guaranteed memory-usage correctness.
The EPM is particularly worrying as AlphaStar can focus on multiple areas of the map at a single time.
A common strategy in GM is to attack on one front with your main army and drop a small amount of units into the back of their base. The opposition has to decide between spending their focus on the main battle or the dropped units.
AlphaStar doesn't have to worry about this - there's no gap between focusing on the front and the back at anything similar to a human.
Players usually use add hotkeys for camera positions to allow them to move around the map fairly fast. We can imagine a human player in this scenario responding by going
* Some actions to move army/setup
* Use pre-existing camera hotkey to go back to base, view situation
* Setup a new unit group
* Move unit group to base to head off attack
* Move workers to avoid economy loss
* Go back to battle
* Setup camera hotkey for battle
* Flick between two battles as needed
* Move workers back
If AlphaStar can view the two locations without that lag or without setting up new camera hotkeys for movement, there's a definite and sizeable advantage before we get into the amount of EPM involved. An action that is setting up a hotkey is significantly less valuable than one using a spell/moving a unit/attacking.
"All Cops Are Bastards" - It's to do with all individual police officers, who could be perfectly moral upstanding citizens, being complicit with an institution that has done terrible things.
It's more of a reaction to the idea of changing an institution from the inside.
It's not too much to expect an article entitled "What is a ket?" to explain what a Ket is.
Your point is arguable if it was instead "How to implement a Ket in Rust", and even then it's a bit vague. I left with the same feeling that it was a bit barebones in terms of definition.
So it is unclear if this is data that is provided to Facebook servers but not accessible to Facebook, similar to options for Google's Analytics platforms, or if it is harvested by Facebook by permission of the app creator. Both options being shady, as it's not told to the user, but this video feels more like it's saying Facebook is actively tracking people, not App Designers are giving Facebook permission to track you in exchange for marketing analytics.
The data that is being provided is significantly too high, and the user should be made aware, but this video seems to only discuss it being API calls to the Analytics interface when using the app.
I'd definitely expect there to be API calls when using an app, but how User ID tracking is done is probably the most potentially dangerous part here.
Does Facebook Analytics for Apps segment the data from that of Facebook or combine it? Is there any policy even stated that says it's not used for other things. I would suspect, but have not looked, that all the data is combined together and used for selling ads and in other ways.
If that is the case, an app that is using it to get analytics for themselves is also sending lots of data to Facebook to be used for their other purposes.
Is this information transparent to anyone? This can lead to the tracking failing GDPR or other laws.
Now, if it was only analytics for apps for the benefit of the app owner and not shared... things might be different legally speaking.
Of course IANAL and they may have much more to say.
It's pretty! The Basecamp styling is really clear, and it's nice to see the interface on display
There's a few unanswered questions that I hope it's helpful to point out;
* Importers -> If I want to switch, how long will it take me to move from a potential system (Excel, Google Sheets, Salesforce, etc) into Wobaka?
* Integrations -> If I send an email can that come from my Outlook Gmail and be shown? Can I see emails from my colleagues towards a contact if they want to?
* What does a workflow look like? A gif of going from New Contact -> Adding them into an Org I'm talking to -> Sending the first message would do a lot here.
* How do I engage with my colleagues? Can I tag them in tasks, or pass things along to them?
> The Basecamp styling is really clear, and it's nice to see the interface on display
Promising. Anyone who seems to take inspiration from Basecamp is worth at least 30 extra seconds consideration in my book.
Basecamp is the company behind Rails and they were IMO one of the driving forces that made Ajax accessible and web application developement enjoyable.
Their UX was (and probably is) good, and their business philosophy flies right in the face of "unicorn or nothing" which means I wish more people would learn from them. Heh, I realize I'm probably not meant to say that here, but based on previous experience I expect it to be tolerated : )
- Signed: a Java (and other languages) developer that is happy for Rails
Tackling the privacy focus for GA is great, but they're a good deal of products out there that already fill that niche, not to mention the requirements of the privacy crowd usually being a venture into itself.
If you wanted to make it relatively competitive for marketing, the simplest addition would be adding labelling via regex for referrers.
i.e. - Some users want to be able to group Baidu, Google, DuckDuckGo, into a single bucket for comparison. Some users want to break them down into common market segments by country. "https://www.baidu.com/link?url=FyYbCZqj65Vc7A4XeSNrOcQCS2qFX...
is from your live demo referrers, and makes it difficult to actually assess the amount of traffic from Baidu. Using a regex label means that users can break down traffic from Paid/Organic marketing fairly quickly, and start to build up dashboards they can use.
If you ever extended it to allow multiple labels for each hit, could re-run the regex over past data, and could build reports off it, you'd easily have a benefit over GA that would start to wean the marketing crowd off it.