Weebs

I may be off, but the heart of the issue to me is that the internet is beginning to resemble the world at large, because the world at large realized that the internet was another vehicle for profit.

The goals Mozilla has mentioned here are important, but I don't think they quite get at the crux of the issue: the rulebook our society plays by is structured in a way that the development of these symptoms is almost inevitable.

The hard thing is you can't really begin to point out these structural issue without people shutting you down: saying that's the way things have always been (it's not), there's no other way (there is), denying that it's even a problem, or that it's something we just have to deal with.

Until we are structured in a way where we can work for the benefit of each other and ourselves, on our own accord, on our own time, this is the slope of the hill we'll keep rolling down.

Let's build open ecosystems and push back, but it is imperative we recognize the game is slanted against that.

Is there any way we as a community of users can help ensure Firefox remains viable in the event that Mozilla can no longer provide enough support?

It seems a shame that such a loved & enjoyed project might fall wayside without significant financial backing. I would say I would love to help, but I have no domain expertise in browsers/rendering, or how I would develop enough to contribute.

It's not either or, you don't have to have individual ownership for properties. A landlord can be replaced by a neighborhood cooperative that redirects the value produced from the building back into the community (schools, public service funding, etc.)

Private ownership and rent contracts is only one way of many to solve the problem of granting access to space without outright purchase.

Also, providing a service and extracting value from others work aren't mutually exclusive. Consider this: a foreign organization extracts natural resources, refines them, sells the new product back to the localsy (and other outside communities) for large profits that are mostly redirected outside of the native community.

I would clearly call that extraction, the fact that they also provide a service to the community doesn't negate that.

Because landlords are trying to profit off of the conditions created by the broader local community. They make a bet on which space created by the community will allow them to extract more rent than the cost to maintain the building and pay the loan, and later sell the property for more than they paid.

Tenants are either members of the community who want a home, or are trying to provide a service to the community.

One group is trying to speculate on the value others will provide and get a cut, and they're able to do this because as they've ensured scarcity of affordable space. It's extraction

The race issues are part of the financial theft. Racism is used as a tool of division to keep the poor fragmented, people are rightfully trying to destroy that tool.

This actually isn't fully true, we don't digest all kinds calories equally. Generally speaking, yes, the most important factor in body weight is the total amount of calories consumed. Whether they are proteins, fats, complex carbs, or simple carbs, and when you consume them during the day, effects how much of that energy actually gets stored in the body.

https://www.strongerbyscience.com has an article somewhere on this, and it's not well tested yet, but we're starting to see some scientific evidence to back this up.

Yeah, uh, let's not lump in child abuse with addiction. I'm also going to call bullshit on shaming addicts benefits society.

I'd argue you're right, but when you're programming in something like Haskell that guarantees certain constraints are met just by glancing at declarations, these tools become less essential.

In FP, I tend to look at implementations to understand what they'll produce

In OO, I do this, but I also need to know _how_ since they might be changing the current context I'm working in. It's not enough to know that X method produces Y, I also need to remember that calling X implicitly modifies Z when I'm referencing Z

In an FP environment X can't modify Z outside of his context, so I don't have to care about how he produces Y. The cost of this is that someone needs to own Z and functions need to additionally return the new Z, but I think that explicit hierarchy helps in guiding towards a more understandable architecture

It's probably not common, but for me the answer lies here:

> I don't recall seeing them used as substitutes for classes or vice versa for years at this point

I had a fairly large school project developing a JavaScript application back before ES6, and kept searching for a better way to structure my code because I found it awkward using prototypes + binding this for events. Eventually I found a hidden golden nugget of a tutorial that showed me how to do it with closures and I was in awe that it somehow wasn't the norm (and obviously how cool it was to build objects out of functions!)

I think for FP it should be added, that the state is explicit and has a clear owner. Eventually someone has to replace the old value with the new value in the call chain

What's really interesting is Rust arrived at a similar destination, I assume as a natural byproduct of pushing for memory+thread safety. State isn't discouraged, but you get explicit owner(s) of data who lend it out to others who are readonly by default, and explicit when they will modify the reference you gave them.

After picking up functional programming < 2 years ago and using it constantly at work, I definitely have to say I disagree with GP that OOP is easier to understand.

I think there's a lot of value in the concepts of OO's message passing, and exposing an interface that encapsulates some internals. It's a tool I regularly use in FP even with immutable types

Imperative OO to me though is plain difficult to do correctly, and shouldn't be the primary way that your encouraged to write code. It's much more difficult to track dependencies and who touches what in an imperative class, and you end up digging around the file before you can even know what you have to keep in your head.

With FP, you generally have pure functions that take in some state and dependencies, and produce a new state. Everything you need to know related to how that function behaves is explicitly given to you, and it's trivial to test the code. You can do this in imperative OO too, but you're nudged in that direction by default.

I do think there are cases when imperative code and imperative OO make a problem easier to represent/understand and faster to execute, but I like to keep those sections small and easy to fit in your head, delegating most of the logic to functions. The imperative OO is mostly some glue to bring the business logic to life.

We use JS but that code base is significantly smaller than our .NET base.

I can only imagine there's a ton of massive ASP.NET MVC + a bit of jQuery internal apps still chugging along too

As someone who has tried that, eventual depression. Sitting around doing nothing is awesome until it isn't

I took a over a year off from working two years ago, and it probably took less than 6 months for depression to begin setting in. By a year I recognized how awful and lethargic I felt, and when I started working again a few months later I was ecstatic to get out of bed at 6:30am to actually go do something every day. In the past this is something I would've loathed, but it was so much better than sitting around all day playing games.

I can't speak for others, but I know personally I need "work" to be happy. I don't think it has to be a job at an office, but something to make me feel like I'm contributing and striving towards something useful & bigger than myself.

Getting the same issue on the Master Thesis template in Firefox 71.0

I have this for any similar sound or physical sensation. I can't stand the noise of grinding or my girlfriend filing her nail. Similarly sensations like a nail file against my nails is probably even worse

I don't think it has anything to do with the sensations themselves, just my brain perceiving the stimulus as abrasive / piercing. It causes some kind of psychological pain, and weirdly I did not have this problem until my mid-20s.

Any tips on finding hackerspaces, online or IRL? Particularly in regards to art installations. It's something that's been on my mind recently :)