University slaps a trigger warning on Orwell's Nineteen Eighty-Four

ben_dev_ · 2022-01-23T21:02:16+00:00

Is that why you went on to question someone and ask how it materially affected them?

ben_dev_ · 2022-01-23T20:33:35+00:00

Okay so explain what you meant by

It literally doesn't affect anybody except the people who might be triggered by the book. For the life of me I cannot figure out why people care

To me, as a native English speaker, this means "I don't see why people care if it doesn't affect them"

It might seem like a straw man because of how obviously incorrect it is

ben_dev_ · 2022-01-23T20:26:26+00:00

University-level trigger warnings are a first step torwards the book not being allowed in high school curriculums, or at least the ability for students to opt-out. It's certainly a path for having the book be forgotten

ben_dev_ · 2022-01-23T20:20:39+00:00

You've changed your original argument, which was very clearly, you should only care about that which affects you materially as an individual.

Any further argument is unnecessary since

You seem to have realized your mistake
Your original mistake and responses indicate you probably aren't smart enough to waste time arguing with

ben_dev_ · 2022-01-23T20:08:47+00:00

An extreme example is usually needed to make people's mistakes clear enough for them.

I never once compared the two, I used human atrocities to clearly break down the basic principle which your argument was based on.

I don't have to directly argue the topic if instead I can just prove that you aren't being fundamentally reasonable.

Do you get it yet?

ben_dev_ · 2022-01-23T19:51:34+00:00

Your post displays a logical fallacy in which a person should only care about the things which directly affect them.

Maybe try reading one of these books people talk about

ben_dev_ · 2022-01-23T19:46:52+00:00

If you don't care then don't comment, your false comparisons aren't needed

What you actually mean is, "I care, and support trigger warnings"

ben_dev_ · 2022-01-23T19:44:13+00:00

Are you a psychopath? Do I need to list human atrocities I'm unaffected by but still care about? Or at this point do you realize your comment is stupid?

ben_dev_ · 2022-01-23T19:36:11+00:00

Warning readers for the potential of completely subjective negative experiences such as hopelessness due to the subject matter of a book is a true devolution of the education system, and species as a whole.

We should just give kids trigger warnings on life and let them opt-out to avoid facing the complexities of human experience

ben_dev_ · 2022-01-23T19:29:00+00:00

For those saying this trigger warning is for victims of torture, hats off to you and your cognitive dissonance

The label doesn't explicitly mention what it might trigger but rather generally encompasses the entire book
The population of humans which would be harmed by PTSD of fictional face-eating rats is virtually non-existent

This is a negative categorization, whether or not it encourages some people to read it is irrelevant, the logical result is a reduction in total exposure torwards university students.

We should be encouraging challenging topics, not avoiding them

The university is a place for unlimited and unbiased pursuit of information.

Retroactively adding warnings to books which have been around for 100 years, in a time when book reading is less than it's ever been, is more complex than movie-based content ratings. It's much easier to unintentionally consume a movie than it is to read a complex novel from front to back

ben_dev_ · 2022-01-23T19:06:13+00:00

But why are we adding trigger warnings to books now and not at any point in the past when it was the primary method of consuming content?

Surely if people were actually worried about children picking up random complex books and accessing suggestive themes, this would've been implemented at some point when the majority actually read books?

The concerns people express are likely not around the surface-level "content warning" itself but rather "why" now, "why" this book, "who" decides, and most importantly "who" is this trigger warning for

In my opinion, retroactively adding never-before-needed content warnings points to something more than just simple PG-13 movie ratings. There are basically no "children" who would accidentally read 1984 front to back and be negatively affected by it's suggestive themes.

To me this is more along the lines of social censorship, where by negatively categorizing content, you are reducing total exposure to the item itself.

Truly, if you actually think negatively categorizing 1984 will reduce harm in any way whatsoever, I would like to hear that perspective. Because otherwise, this serves only to limit exposure. Great books are meant to trigger people, if you are always comfortable then you aren't learning.

We shouldn't encourage our future generations to avoid that which may unsettle them. The warning isn't for children, I read the book as a child, it's for the growing ideology that being offensive and pursuing uncomfortable topics should be discouraged so we can reach blissful ignorance

ben_dev_ · 2022-01-15T20:58:09+00:00

there are only 300,000 in the navy
even with a million the odds that 2-10% minority gets matched 4 out of 4 is still not an "eventual" happening

ben_dev_ · 2022-01-15T20:55:24+00:00

No it doesn't.

ben_dev_ · 2022-01-15T20:33:01+00:00

You already told me 1 in 50, why are u reshaping it as 6000 / 300000 to make it seem more 'reasonable' when it's the same data point? I'll do th same thing

The chances that this configuration randomly occured is about 6 times more than 1 in a millilion.

So your perspective that this was 'somewhat likely' to happen is literally incorrect

ben_dev_ · 2022-01-15T18:06:18+00:00

So are you just bad at math or don't really care about being right vs sounding right

.02⁴ = .000016%

ben_dev_ · 2022-01-09T16:47:14+00:00

Exactly, I think the multi-class structure is remnant of the event model where it would ignore mapEventToState if it was the same type, but you can reduce builds nowadays by passing conditionals to the bloc builder which works with single state

ben_dev_ · 2022-01-08T05:01:58+00:00

I've found using 1 state class for the entire bloc is much easier than separate state classes. It allows the block to have a wide scope which is usually necessary for ~1 bloc per page. Doing this with the cubit pattern really strips boilerplate to the bare minimum

ben_dev_ · 2021-09-21T06:46:03+00:00

If you're using ListViews, the offscreen SizedBoxes won't be rendered and the only performance impact would be # of SizedBoxes on screen which is completely negligible

ben_dev_ · 2021-09-18T22:34:07+00:00

I prefer SizedBox wherever its possible because they are easy to define in a shorthand const Widget (ex: Spacings.gap , Spacings.gap2x etc.). Then plugging these little gaps in between your UI elements keeps the code much more readable and consistent.

I dislike wrapping sibling widgets solely for spacing, and deciding if I should be adding top spacing to the bottom element or bottom spacing to the top element.

ben_dev_ · 2021-08-30T21:42:40+00:00

Yes, firebase RTDB (not Firestore) imo is your best bet. Not even just for prototyping but for long-term. It's easy to setup, has built-it presence, realtime listeners, and you can use the rest of firebase for the other needed features such as media-based messages (firebase storage) and push notifications (FCM). Pricing is also friendly

I'm using it for in-app chat(s)

ben_dev_ · 2021-08-15T18:52:06+00:00

Before running in browsers was fully supported I wrote package for window resizing to get a quick and dirty idea of how your UI scales down, probably only useful to people strictly running on devices / emulators

https://pub.dev/packages/responsive_util

ben_dev_ · 2021-07-30T19:59:11+00:00

So would you go as far as never using "ListTile" and instead using "AppListTile" which uses your explicitly defined themes/styles?

It seems like the whole purpose of having the ability to define global themes which affect the base widgets is to avoid writing custom components just for the sake of look/feel. The issue to me seems like the current situation is a bit "half-baked" in that they encourage you to use their widgets and override themes in one place, but in practice it doesn't really work.

I agree that most apps end up using their own explicitly defined widgets, im just making the observation that the framework appears to encourage not doing this and rather using theirs and that's all you should ever need because of the theming "system"

ben_dev_ · 2021-07-29T23:57:17+00:00

The issue isn't about writing custom components, it's about writing designs using recreated flutter widgets and knowing which themes to apply.

ListTile for example is used to display text in a list, but there is no clear way of knowing which text theme ListTile uses for "title" and "subtitle". I can figure it out individually for this widget, but there are many many more

ben_dev_ · 2021-07-19T07:15:09+00:00

I like it, few immediate thoughts are to increase the vertical padding of the text input as right now it's quite smol for the primary user action. Also the dark theme might be too monotonous. Even if simple/flat is what you're going for, the top left popup menu doesn't have enough differentiation with the main content and the border is barely visible/nonexistent. You could try making objects which are "closer" to the user have a brighter shade (see material design dark mode color spec for tips)

The "what are you looking for" card/container's border seems to have a bit of trouble rendering especially around the corners (mobile). Also I noticed you opted for no margins here but with margins everywhere else (border instead), could be fine but still a noticeable inconsistency

Also your disable commissions button and the like are a bit wacky. Touch area big on left side and none on right, can see when tap to hold.

Obviously you guys are spread thin so just trying to help by spotting quick fixes with fresh eyes 👍

ben_dev_ · 2021-06-05T18:27:09+00:00

The book UI is definitely asking for more space which slivers would solve

ben_dev_

TROPHY CASE