Frankly I hope they ramp it up, because maybe it'll at least open up peoples eyes to all the other insane sorts of injustices that go on.
400 karma · joined October 26, 2016
Frankly I hope they ramp it up, because maybe it'll at least open up peoples eyes to all the other insane sorts of injustices that go on.
The work day used to be 12 (or in some cases more) hours, and a lot of people fought and literally died to get it down to 8. And the expectation wasn't that it would stay there - instead, the common idea was that as productivity due to technological advances etc. would keep pushing it down to only a few hours per day.
Instead, productivity has soared and the parasitic capitalists of the world and their legion of class traitor middle managers have managed to convince people that 8 hours is somehow perfect even though rarely anybody even actually works 8 hours these days - how long is your commute? Do you get work related alerts on your phone? Coworkers/bosses messaging you? That's all time wasted thinking about work. This small group of people - probably what, no more than 5000 out of 7bn people? Are hoarding and stealing obscene amounts of ill gotten gains, killing the planet in the process and ruining probably billions of lives, while we sit here and argue about whether or not we "deserve" to work less or whatever.
I don't get it the other way around - why do people freak out about it? I don't care one way or the other whatever or not people piss in the pool next to me - its like somebody splashing you with water in the middle of a rainstorm.
>the average person has never had a good life, and probably never will
Because our society doesn't care about people, only capital. There's nothing wrong with the average person, its that the average person is born into an environment where everything is working against them.
And I think it's pretty clear that as we reach unprecedented levels of income inequality - especially with climate change being a thing - that the inherent contradictions of the system are becoming more and more obvious. The yellow vest protests are a clear example of this. If we're lucky it'll end well, but whether or not the ruling class will take control of the situation and steer us towards fascism remains to be seen.
Instead of loading up every language with stupid keywords that are meant to simplify monadic code (but only for one domain), language designers should really take a page out of Haskell or Scala's book and think seriously about unifying on a do notation/for comprehension type construct.
That way regardless of if you're working with promises or not, you don't have to worry about hacking it with && or nesting 10 layers deep with if/else.
Without fail every suckless person I've talked to either has no idea what they're talking about, or in the off chance they do they're incredibly shitty far right wing types who gripe on about women/minorities/CoCs ruining tech.
The entire police system is inherently corrupt and racist and needs to be torn down. Also, regardless of whether or not its a few bad apples (hint: given how extremely fucking common these problems are, it absolutely is not just a few) the point still stands that the "not bad" cops are still guilty of supporting their coworkers and enabling their unacceptable behavior.
China has some serious issues, but people acting like this is out of the norm is ridiculous. The US is afraid of Chinas rising influence/power and these sorts of articles attacking it are a common tactic.
Like, great - there's no explicit social credit system in the US on an app where you're barred from leaving the country because of who you're friends with. Instead, there's an implicit one where the NSA gets to spy on all your shit (similar to what happens in China), where you're arbitrarily put on a watch list or no-fly list (similar to China), and depending on your ethnicity and/or family you may get unjustly targeted by the state with no real way of defending yourself (again, similar to China).
I'd almost prefer it be done the Chinese way, because at least then the problem is obvious. As it is in the states, like half the country can't even fucking agree that maybe there might be a problem with women & minority rights, immigration, police brutality, etc.
I don't see where you get your conclusion from. For many (most?) people, they really don't have a chance to fight their landlord. Legal expenses, time, energy, etc. are pretty huge deterrents. Not sure why you can't fight a "state-landlord", also.
I'm not sure what you're asking re: what would remain. Housing as a human right, I guess? There's no good reason for landlords to exist, nor do I understand why you would want housing to be a commodity especially considering we live in a post-2008 world.
No need to get all complicated, the solution is pretty simple.
Repl driven development works very well with pure functional code and at no point did I feel an increase in loc begin to make it tedious or whatever.
The repl approach perhaps doesn't work as well in Java because Java and its ecosystem encourage writing messy jumbled code built upon unsafe abstractions.
I was receiving an error complaining about a missing prop on a component I was wrapping with `injectIntl` from `react-intl` and could not for the life of me figure out what was wrong. Searching the type error wasn't helpful, and it wasn't until I really dug down and spent about a half hour of my time that I realized it was because we had something like `injectIntl(connect(foo, bar)(SomeComponent))` instead of `connect(foo, bar)(injectIntl(SomeComponent))`
The type error did not in any way make that clear or obvious. If I had to compare it to anything, it would probably be the type of error messages you see if you play around with type level programming/dependent types in Haskell. Or the types of error messages you see when writing Clojure.
I think the most immediate and obvious pain point for me is typing HOCs. It's basically a matter of rearranging how you apply them until TS can automatically infer a type for you. At the same time, using `compose` instead of applying them individually solves that problem but results in strange types (that are different from the type TS infers if you apply the HOCs manually yourself in an order that makes it happy) that I suspect will cause type errors down the road when we convert the files that make use of it to TS as well.
As far as going back goes - it's preferable to plain JS I guess? But that's not saying all that much. I don't know - I'm sure I'll appreciate it more after this migration period is finished and things start to stabilize, but as of right now I'm definitely not enjoying it.
It seems like something that only exists due to the popularity of Angular, where I can only assume the experience is significantly better than with React.
The type system is frankly disappointing, and the errors the compiler spits out at you (besides the most obvious ones) are almost always useless or gibberish and at times even more harmful than helpful.
It's better than nothing I guess, but I can't help but feel extremely underwhelmed with it given how many people use it. Are all of the people in this thread Angular developers or something?
The Chinese rich I've interacted with are also (in my experience, at least - I don't have stats to support this) really ignorant of how bad a lot of their countrymen have it. A friend of mine's father is some sort of government official in a tier 1 or 2 city, and he's told me that the rich and poor are segregated enough that he himself didn't even realize his family was anything other than middle class until he came to Canada and saw it wasn't exactly normal to have parents who can afford 100k+ annual tuition, luxury cars and apartments, etc.
Also, if your type is something stupidly long (ex. Java) its really easy to read something like MyAbstractFactoryBeanImplBuilder while you have a bunch of stuff in your head and space out/forget something. Humans aren't good at keeping a bunch of things in their heads, so I'd much rather just have the names of these things and then types be as a reference to return to as a "oh wait, what was this thing again?" sort of deal.
The core team also finally realized how important tooling is and recently dedicated a team (a bunch of teams?) to working on language server based intelllisense which is nice.
I'd highly encourage anybody who last used Scala a while ago and didn't enjoy it to give it another shot at some point in the future. Lots of improvements over the past few years (and some really cool stuff coming up with Scala 3) make Scala IMO easily one the best languages around.
Frankly, as a Toronto area dev Doug Ford winning the election would definitely cause me to consider looking for work in the US. Toronto's in a pretty crucial moment right now wrt growth and infrastructure, and I don't really see the point staying if the party of stagnation wins - whatever tax cut they may introduce is dwarfed by higher salary + lower CoL in the US anyways.