Amazon had a whole paper about how bringing migrants and diversity makes unionization less likely and successful.
It's part of the point.
Also it's not just the US. Here in Europe it's the same.
Hell the government spent it's money trough the employers org training Moroccans to become programmers to then bring em in.
I knew a fair few programmers who believe this is all just for low skill low paying jobs as if paying better wages for those is impossible and as if those deserve to be undercut.
The weird thing is how this kind of plainly rightwing economic rhetoric is often masquerading as left wing.
The only silver lining in this mess is that it does seem like this was finally the push for my industry to start seriously pushing for unions. Of course, corporate won't let it come easy but I only see momentum building now.
you’re getting the logic wrong. i’m absolutely sure apple and google have direct cia backdoors. that’s what Snowden taught us and it would be delusional to think the world has changed. The bigger the company = tighter the link with power
I'm sure you're very familiar with the politics of both countries, but tell me...
How is Nicusor Dan a puppet of the EU? More than Calin Georgescu? The guy who actively tried to stage a coup? More than George Simion? Granted, there's no PROOF he's a Russian puppet, but he's a far right twat that has views friendly to Russia.
How is Maia Sandu and PES a puppet of the EU? And... let's look at BEP. Voronin, Russia friendly ex President, he was very against Moldova trying to get closer to the West. And Dodon? The guy who is being indicted for treason, who's a friend of Plahotniuc (he stole 1 billion dollars from banks and fled the country)? Yeah, sure, puppets of the EU, vs corrupt fucking puppets of Russia.
I know it's easy to look at this stuff from the outside and say, oh, yeah, the EU is interfering in elections, but there's a lot of history here that you obviously don't have. I like Maia Sandu more than Nicusor Dan (his positions on gay rights were disgusting a while back, he now just stopped talking about them), but compared to the obviousness of the Russian support for their opposition, I think the fact that the EU supports them is just insignificant.
I don't. I do remember when they were annulled after Russian interference and there were other fundamental issue with the first first round and Georgescu's campaign that broke the law.
When I say history, I mean more than just the decision, which might look like "oh, they didn't like the results", but also the events that lead up to it, the campaign. I'm not even going to go into the coup d'etat he attempted after the elections with a group of far right mercenaries, or the things that came out about the campaign and Georgescu that weren't known at the time (which, obviously, couldn't have been a factor, but confirm that this was the right decision).
I'm not sure what the accusations you're talking about are
why don't web devs just learn html and css properly, and maybe xslt for the really complex transformations then use vanilla js only when it's truly necessary?
instead we've got this absolute mess of bloated, over-engineered junk code and ridiculously complicated module systems.
For context: ramada 0.32.0 isn't a concrete thing, in the sense that glibc 2.35 is. It really means "the latest ramada code because if you were to pin on this version it'll at some point stop working". glibc 2.35 never stops working.
me too but a lot of people see it as massive overhead they don't want to deal with.
personally i pin all mine because if you don't a version could be deployed during a pipeline and this makes your local version not the same as the one in docker etc.
pinning versions is the only way to be sure that the version I am running is the same as everyone elses
I use duckduckgo and live in a neighboring country, so I know Russian well (thanks, imperialism) and have to search things in it from time to time. It's still good at those queries, so this is just an excuse.
json is sort of a gresham's law "bad money drives out the good" but for tech: lazy and forgiving technologies drive out the better but stricter ones.
bad technology seems to make life easier at the beginning, but that's why we now have sloppy websites that are an unorganized mess of different libraries, several MB in size without reason, and an absolute usability and accessibility nightmare.
xhtml and xml were better, also the idea separating syntax from presentation, but they were too intelligent for our own good.
> lazy and forgiving technologies drive out the better but stricter ones.
JSON is not "lazy and forgiving" (seriously, go try adding a comment to it).
It was just laser-focused on what the actual problem was that needed to be solved by many devs in day-to-day practice.
Meanwhile XML wanted to be an entire ecosystem, its own XML Cinematic Universe, where you had to adopt it all to really use it.
It's not surprising to me that JSON won out, but it's not because it's worse, it's actually much better than XML for the job it ended up being used for (a generic format to transfer state between running programs supporting common data structures with no extraneous add-ons or requirements).
XML is better for a few other things, but those things are far less commonly needed.
Don’t know if I would describe it as much better. I see it similar to the whole SQL -> NOSQL -> let’s add all the feature and end up with SQL. JSON undergo a similar story with the difference that we didn’t go back to XML. What I mean is to simplify and then realize what was actually missing.
But I agree for the smaller services and state transfer especially in web XML was just too damn big and verbose. But conceptually it was great.
For "I need this Python dict to exist in this unrelated JavaScript program's context space" JSON is absolutely much better. If only because you completely sidestep all the various XML foibles, including its very real security foibles.
JSON is so good at this that, like CSV, it does displace better tech for that use case, but the better tech isn't usually XML but rather things like Avro or Protobuf.
For the most part people don't add on XML features to JSON. Comments are a frequent addition, sometimes schemas, but for the most part the attraction of JSON is avoiding features of XML, like external entity validation, namespaces, getting to choose between SAX or DOM styles, or being required to support unrelated XML systems just to use another.
Again, there are problem domains where those are helpful, and XML is a good fit for those. But those problem spaces end up being much smaller in scale than the ones solved by JSON, Avro, Iceberg, etc.
But the whole point to JSON is to be nearly as dumb simple as possible so that the complexity of the problem domain will necessarily be handled in a real programming language, not by the data magically trying to transform itself.
reply