When I started using a Mac in 2009, MacPorts, Fink (and I think there was another I can't recall the name) simply wouldn't work for me. They would take very long to build what I wanted, there weren't nearly as many packages as was in Debian/Ubuntu, and many were old versions. Worse, many build attempts would just fail.
In that scenario, brew worked like a charm. It was quick, had most or even more packages than Debian/Ubuntu and they were newer. Failure to install was rare.
Then, Apple started yearly release of OS X, and that both broke brew and my system hard, so I started investigating and found out about the many "shortcuts" that brew took and how it violated systems components. I was dismayed, and abandoned brew for good.
So, I stood a period where I would use many of my tools inside a Ubuntu VM, until probably 2013-2014, when for some reason I tried again MacPorts, and I don't know why, but that time it was much more reliable, and because of Apple's insane atm SSDs with 2 GB/s bandwidth, install became quick enough. Packages were still somewhat lagging behind in available versions, but the variety of them kinda reached the levels of what was in Debian/Ubuntu, so it was good enough for me.
Then, the killer feature, I found out about macports variants and selectors, which I find the most awesome thing to this date in package managers (I haven't tried nix, still, it might be magnitude better in that regard). No needing to use rvm, pyenv, custom installs of gcc messing with make/autotools, and the only sane way of compiling various Haskell projects (before haskell-stack).
I don't know when they introduced it, but I believe MacPorts will build the common variants of the more-used packages. So, if you install a package with the default variants, you'll get a binary download instead of building from source.
But indeed; fast SSDs, parallel compilation, and modern CPUs really help!
Truth is much simpler. The rain volume was unanticipated, no matter what government was there, the catastrophe would still happen.
As you wrote, the left governed there for decades, and no adequate containment for this event was built, nor it was built by the following center-left following governments. There was never a right or far-right government there since the 70s. Unless you are referring to Bolsonaro, but then it would be weird since he’s already superseded by the worker’s party by a year and a half now.
> As you wrote, the left governed there for decades
This is false. Quoting from my sibling comment:
Not quite. The state of Rio Grande do Sul had 2 PT (Worker's Party) Governors: Olívio Dutra (1999-2003) and Tarso Genro (2011-2015).
RS's capital city Porto Alegre had a much longer PT administration (Starting with Olívio Dutra in 1989, ending with João Verle in 2005).
> no adequate containment for this event was built
I came across a document from Porto Alegre's administration in 1992 [0] (first time with the Worker's Party in office, under the always thoughtful and overly intelligent Olívio Dutra) where they do an extensive analysis of the anti-flood systems in place, options on how to improve them and how important participation of civil society is in these processes.
[0] https://www.dropbox.com/scl/fi/y02s8cvxf6qts3ktgc70q/PREVENIR-O-MELHOR-REM-DIO.pdf?rlkey=eqfzhu1pmxx6x288fskhtihy0&st=2tfc9iu1&dl=0
> There was never a right or far-right government there since the 70s
This has to be a joke. Aside from those administrations I cited, everyone single one of the others has been right-wing.
you quote verifiable historical facts and sources! you will be downvoted to hell by the extreme-right-who-think-themselves-as-smart-centre. bon voyage my friend.
I completed the CompSci X-Series of MITx on edX, and Software Engineering for IaaS, from BerkeleyX. They were so awesome that I can only think they phased them out because it was such a bargain. Practically, the courses allowed me to change career and to be well positioned.
Well, you're probably at least sortof right. Once the bloom went off the MOOC rose, edX got sold off to an EdTech company. In general, universities decided that shoveling money and effort into the MOOC pit didn't do a lot to further their mission. MIT mostly continues OCW as sort of a sideline. I don't know how many resources actually go into it at this point.
I once worked in a lab where all computers had its own electrical stabilizer, but they were so poor that probably they did more harm than good. When someone turned on a stabilizer, the nearest CRT monitors would distort for a second, then flicker and colors would be degraded.
Luckily, my place was by the wall, so the effect was diminished, but it gave me big headaches. I lasted only 6 months in that company this being the biggest reason.
The stabilizer was triggering the degausser on the CRT. Turning on speakers or putting cellphones where a call was coming in would sometimes do this too.
Where I worked containers just gave the data scientists superpowers at finding corrupted Python runtimes. I don't know where they got one that had a Hungarian default charset, but they did.
In that scenario, brew worked like a charm. It was quick, had most or even more packages than Debian/Ubuntu and they were newer. Failure to install was rare.
Then, Apple started yearly release of OS X, and that both broke brew and my system hard, so I started investigating and found out about the many "shortcuts" that brew took and how it violated systems components. I was dismayed, and abandoned brew for good.
So, I stood a period where I would use many of my tools inside a Ubuntu VM, until probably 2013-2014, when for some reason I tried again MacPorts, and I don't know why, but that time it was much more reliable, and because of Apple's insane atm SSDs with 2 GB/s bandwidth, install became quick enough. Packages were still somewhat lagging behind in available versions, but the variety of them kinda reached the levels of what was in Debian/Ubuntu, so it was good enough for me.
Then, the killer feature, I found out about macports variants and selectors, which I find the most awesome thing to this date in package managers (I haven't tried nix, still, it might be magnitude better in that regard). No needing to use rvm, pyenv, custom installs of gcc messing with make/autotools, and the only sane way of compiling various Haskell projects (before haskell-stack).