You were a medical researcher or librarian or astrophysicist.

Now you work in a factory making plastic toys.

Sounds kind of soviet, really.

This account’s is. You are way more than that!

It’s all about your behavior, not your politics

It explains the downvotes.

OP is a queue flooder who made a name for himself as a _____.

there’s that whataboutism we talked about

I think the onus is on you to express what your journalistic standards, source selection criteria, and research processes are; since you have taken a position as a profligate poster.

Such high traffic deserves community scrutiny.

What work did you do, and do you do on the 20-30 reposts per day to prove that you are not disseminating such content?

This tactic won’t work either. Try again.

Appeal to rules and “due process” isn’t going to work like it did a few years ago.

You showed up bulldozing articles day 1. No one thinks you’re just some everyday community member who needs to be protected from the mean old mods.

LOL, no, the message I’m sending is completely different from that.

You’ve operated this account for 30 days and originated over 600 posts with it. Now you’re going to whine about how hot the kitchen is?

Who talks about that? Only right wing propaganda outlets.

hilarious how he has to establish his “I hate immigrants“ creds before getting to the point

This reply looks like some “get discouraged and angry” bullshit right here. Of course repeating the targeted message of the month about Democrats. And a wild falsehood about the homeless rate in the US.

You can say you’re running Java and write components in Kotlin or Scala, no one knows after the module is published!

Connect people back to value systems instead of aggressively debating specific issues.

For example, when we think about Jesus Christ’s teachings, why are we erasing the nation’s historical decision to help the poor, sick, and hungry - an action executed by the most greedy, vain, and boastful people on earth?

There is a bit more overhead when you can’t just overwrite a value in memory. But cpu time and memory space are some of the most cheap and straightforward resources to scale up compared to engineering time to resolve consistency bugs.

There is also a performance hit associated with mutexes or locking required to ensure mutable structures are updated consistently, and many high-scale systems have moved to append-only logs and copy-on-write semantics - structures that leave already-written data in place - because mutability/locking doesn’t scale.

Oh, regarding copying data - immutable collections are based on https://en.m.wikipedia.org/wiki/Persistent_data_structure - when a change is applied, you get back a reference to a new data structures where as many inner references as possible are shared with the old one. So, all the parts that didn’t change, are not copied.

For something like a Scala case class (similar to a record), o.copy(membername1 = newvalue) returns a new object, with a new membername1 reference, but all other member references are the same as the copied-from object. So it’s a shallow copy with minimal changes.

you might see how default immutability as a policy makes this more predictable and able to be reasoned about - any mutable object in an object graph that has a shared reference in a copy may surprise you by suddenly changing state.

Of course, that’s the situation everywhere, all the time, in default-mutable languages. How many people set a default value of a Python function argument to [] or {} and were baffled when things started breaking because the instance of the default value was mutated?

AWS S3

I guess, as a Scala enthusiast, it’s second nature to me - Scala incorporates immutable-by-default into its design so there are accommodations for it (.copy() methods on case classes, well-thought-out operators and methods on collections, “val” bindings, expression-oriented syntax).

It also lets you have normal OO classes and mutable vars anytime you want them, so you’re not stuck in a corner like you may sometimes be in Haskell if you don’t know the applicable FP pattern.