Lots of examples, gender identity and requiring ethnic studies (focusing on white male privilege, settler/colonial, putting groups into binary oppressor/oppressed). Also issues with requiring those classes vs not.
You've identified examples of values, but you have forgotten to link them to the left, forgotten to show if they are controversial and, probably most importantly, forgotten to show how schools are borderline pushing indoctrination of them.
These are two indisputable facts about our world, if you disagree you are wrong and anti-science:
1. Gender is a social construct
2. Whiteness is a social construct and in particular has been used as a bludgeon against minority "non-whites" in the United States for a very long time
If you do not believe these things you are the problem. You lack education. You lack critical thinking. You are brainwashed.
Both of these social constructs must be challenged. The first is used to oppress women and girls primarily, and the second underpins racist oppression.
Of course, I agree. But in the context of education if you reject the above (which MANY people on HN do) then you're delusional. There is nothing nice I have to say about it, and I know how dearly the HN crowd loves to clutch their pearls about the tone. It is akin to believing the world is flat, a broken ideology that should not be entertained.
Once you accept the simple facts as above, then you can finally explore the consequences.
Aircover AI | Sr. LLM Infrastructure Engineer and Sr. Flutter Engineer | San Francisco Bay Area, Los Angeles, Orange County - Hybrid or Seattle (remote)
Aircover is building the future of human-to-human conversation, powered by AI. Our software is being used at scale by the Fortune 1000. We're at the bleeding edge and need individuals interesting in working on net-new problems.
It's a smart move for Google to leverage their huge captive audience on YouTube to drive adoption. With Amazon's similar position with AWS and Twitch I'd be surprised if we didn't see a similar offering from them.
Check out Apteligent, better crash reporting as well as performance data, user behavior and business impact. As a bonus your data doesnt go into Twitter or Google's ad networks and it's COPPA compliant.
I heard great things about Apteligent, especially from larger apps and teams. Was Twitter using the data from Crashlytics for ads? I am not sure if there's a clear answer, but they are an ad company at the end of the day.
We just analyzed Android manufacturers [1] and found they tend to update in two groups: 3 months after release (Motorola, LG, HTC) and 6 months after release (Samsung, Sony, Huawei). This of course ignores Nexus devices by those manufacturers.
I'm the co-founder of Apteligent. David, I'm surprised you would describe our solution as "high level passive analytics" unless you haven't tried it yourself.
I would say the difference is our deep focus on mobile user experience vs Sentry's focus on cross platform error reporting. To understand your users this also means you need more data than just crash. For example: app load times, network data, UI latency, etc.
Apologies (edited), I meant to suggest that other solutions are generally that. I definitely haven't used Apteligent (or Crittercism), but things like New Relic (which from a glimpse of screenshots, seemed similar), I would label as passive systems.
To be clear, there is still fragmentation among devices, this shows that 93% of usage occurs on 3 operating systems vs on iOS where 2 operating systems have 97% of usage. The gap has closed significantly.
If you're going to include 2 OSes for iOS because it includes iOS 8 at <8%, then you have to include Jelly Bean at 7-8% as well, which means its 4 Android verions vs. 2 iOS versions.
If you exclude Jelly Bean, then excluding iOS 8, it's just 3 Android vs. 1 iOS.
I'm basing this on their charts on their pages for both Android and iOS.
The OS version doesn't matter as much here. There is a huge gap in API functionality betwen 2.3.x and >4.x
That's the only thing that matters for a developer as the official Android support libraries hide most of the remaining >4.x API differences.
2.3 no longer matters. Nobody uses it anymore.
With a few exceptions (maybe it makes sense for facebook with its army of devs to still target it), all the devs I know only have a legacy apk (no longer developed, just barely maintained) for their few 2.x users.
The popular minSdk at the moment is 16 (4.1) .
This gives a nice common API, the biggest roadbump in most cases is that you have to handle pre and post lollipop cases : with/without transitions, ripples, etc, ...
It is nothing compared to having to handle 2.x devices though .. the API were pretty primitive and the hardware extremely poor.. you can't develop a 2016 app and target these devices.
Of course there are exceptions. For a camera app, the Camera2 API added in lollipop might be crucial.
In most cases, the support lib does hide most of the API differences.
Many new libs are also provided by Google directly unbundled from the SDK, such as the design lib, RecyclerView or ConstraintLayout.
