f = x -> raise if
x :: int => IndexError x
otherwise => ValueError x
Complete with pipelines, of course: "> {}: {}".format "Author" "stop using stale memes"
|> printThe first 3.5” drive I ever had was in an LC II. Before that I had only used a 5.25 in a PC XT or something like that. Being able to have it suck a disc in or ejecting a disc and having it pop out with that great mechanical noise was fantastic.
Because my age I thought all drives were like that. The first time I used a Windows PC (3.0?) I was surprised that you had to push the disc in by hand and that it didn’t just show up on the desktop in Windows. I had to be introduced to the concept of drive letters. Seemed relatively barbaric to young me.
Of course within about two years I was asking for my own PC for all the great games. So that didn’t last all that long.
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).
this region have been governed by workers party since forever. zero floods. well, small ones that overridden the dams.
last extreme right elections put an extreme right government in that region since a long time. zero maintenance on "fake climate change" things. this is the result.
it's one hundred percent like Texas power grid. hence why the right wing sock puppet accounts are pushing flat earth level disinformation.
reality is always more boring.
and as always, if you even acknowledge the nonsense, the trolls win.
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.
Would love to hear some success stories if anyone has any!
We had a similar problem at one of my first jobs where I was a programmer and backup network support guy. One employee was having a problem with his CRT monitor flickering. It was very subtle, but just enough to drive him nuts.
So we replaced the monitor with one that worked fine on another machine. Same problem. We tried replacing cables, power cords, and did a bunch of other troubleshooting things. Problem persisted. Eventually we replaced his entire computer. Same problem.
Finally I put his computer and monitor on a cart with an extension cord and wheeled it out into the hallway. The problem went away. It turned out to be bad electrical shielding in his office.
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.
Python always had deployment issues, IMO. In Java, 99% of all library dependencies are pure JARs, and you rarely need to depend on native libraries. You can also assemble an executable fat JAR which will work everywhere, and the fact that the build tools are better (e.g., Maven, Gradle) helps.
Compared with Python, for which even accessing a RDBMS was an exercise in frustration, requiring installing the right blobs and library headers via the OS's package manager, with Postgres being particularly painful. NOTE: I haven't deployed anything serious built with Python in a while, maybe things are better now, but it couldn't get much better, IMO.