Hacker Newsnew | past | comments | ask | show | jobs | submit | colatkinson's commentslogin

Your version of glibc is too old. Mint 19 is based off Ubuntu 18.04, which ships glibc 2.27, whereas this binary seems to require symbol versions first shipped in glibc 2.34.

You'll have to compile from source, or update your distro to a maintained version. Ubuntu 22.04 ships glibc 2.35, and so Mint 21 should work.

Mostly commenting because while this isn't really a tech support channel, being able to identify glibc version mismatch errors comes up extremely often, even in this day and age.


The old Tappan Zee was basically a perfect encapsulation of "dumb midcentury infrastructure decisions."

1. Built to last only 50 years to save on materials (as the other commenter noted).

2. Built over literally the widest possible part of the Hudson because the governor got in a pissing contest with the Port Authority and wanted all the tolls to go to the state, which wouldn't have been the case had it been built like 2 miles south where the river is narrower.

3. Designed with zero redundancy, such that a "critical fracture could make the bridge fail completely because its supports couldn’t transfer the structure’s load to other supports." [0]

So yeah if we're being real, 50 years was quite optimistic.

The new Tappan Zee is apparently supposed to last 100 years, though given the incidents with substandard materials being used, as well as ever-increasing traffic, who knows.

That said, driving over a bridge 10 years past its planned EOL and being able to look down directly to the water through gaps in the concrete was always a nice feature though -- who needs coffee when you've got that to get your heart rate up!

[0]: https://en.wikipedia.org/wiki/Tappan_Zee_Bridge_(1955%E2%80%...


"dumb midcentury infrastructure decisions."

Keeping in mind that mid-century Japan and Germany were in ruins and the possibility of nuclear annihilation of urban centers very much at the top of many people minds. 50 years may have seemed an optimistic survival rate of built structures at the time.


God yeah it's like a hypothetical version of the AirTrain that isn't a huge pain. Last time I flew out of JFK from Manhattan IIRC the easiest way was to do the E or LIRR from Penn to the AirTrain anyway, so might as well streamline the whole shebang.


Adding on to the other comment, multiprocessing is also kinda broken on Linux/Mac.

1. Because global objects are refcounted, CoW effectively isn't a thing on Linux. They did add a way to avoid this [0], but you have to manually call it once your main imports are done.

2. On Mac, turns out a lot of the system libs aren't actually fork-safe [1]. Since these get imported inadvertently all the time, Python on Mac actually uses `spawn` [2] -- so it's roughly as slow as on Windows.

I haven't worked in Python in a couple years, but handling concurrency while supporting the major OSes was a goddamn mess and a half.

[0]: https://docs.python.org/3.12/library/gc.html#gc.freeze

[1]: https://bugs.python.org/issue33725

[2]: https://docs.python.org/3.12/library/multiprocessing.html#co...


Re (1), are there publicly documented cases with numbers on observed slowdowns with it?

I see this mentioned from time to time, but intuitively you'd think this wouldn't pose a big slowdown since the system builtin objects would have been allocated at the same time (startup) and densely located on smaller nr of pages. I guess if you have a lot of global state in your app it could be more significant.

Would also be interesting to see a benchmark using hugepages, you'd think this could solve remaining perf problems if they were due to large number of independent CoW page faults.


Replying to my self: it seems one poster case was Instagram and their very large Django app: https://bugs.python.org/issue40255#msg366835


If you don't mind I'm super curious as to what approach you ended up taking. Did you use rules_foreign_cc to build the ninja files they generate? Or generating BUILD files directly? Or something completely different? Sounds like a really cool project!


Same, I’m curious too!


This is a super common setup in my part of NYC (minus the elevator). It seems to work fairly well, especially since it makes it viable to have lots of buildings in a row with minimal wasted space between them.

It's definitely not the densest design possible, but it certainly seemed to let them fit a lot of fairly spacious 1-2 BRs in not a lot of space back in the early 20th c., and the height can scale up pretty well (though the elevator probably becomes at least a soft requirement above 4-5 floors).


I'm thinking more of a 10-floor building because I stayed in one with family in Buenos Aires that was like that several times.


For anyone else who immediately thought, "I've gotta try that!" and hit compilation errors: there appears to be a more maintained fork at [0].

And if you're on a 64-bit system, you'll want to make sure it finds the 32-bit libc and libm binaries (see [1]). On Arch, the following worked for me:

    ./build/movcc -L/usr/lib32 test.c
[0]: https://github.com/xoreaxeaxeax/movfuscator

[1]: https://github.com/xoreaxeaxeax/movfuscator/issues/39


Not sure if you're aware, but ransomware insurance is already a significant industry, and the contracts usually stipulate that the client company undergoes some type of regular auditing.

From what I've heard, insurance companies are actually kinda souring on the business because it's incredibly bad from an actuarial perspective: many of those targeted are SMBs (i.e. they're not paying the kind of premiums that would make it worthwhile), but even for large corps as time passes the odds of a ransom event approach 1. I mean, can anyone think of a large non-tech enterprise that doesn't have that doesn't have that one load-bearing Windows Server 2008 machine in a closet?

So to an extent, this seemingly represents the industry collectively declaring that even massive monthly insurance premiums are insufficient for companies to get their security posture together, and so they're trying to cut it off at the source by making ransomware as an endeavor unprofitable.


> that one load-bearing Windows Server 2008 machine in a closet

Hah, that is literally how an old employer of mine got hacked and ransomwared big time.


Yeah to be honest I think approvingly quoting the author of "The Fascist Manifesto" probably well exceeds the cutoff for "dogwhistle." At this point the only thing left is for a16z to start a youth brigade and invade Ethiopia.


Marc did a podcast chatting about tv shows with fascist and white supremamcist Richard Hanania, so maybe I shouldn't have been as surprised as I was to see that.

https://www.huffpost.com/entry/richard-hanania-white-suprema...


This is very troubling, because Hanania is a genuine white supremacist.

But it turns out he hid it well, and that HuffPost expose only came out two years after the Andreessen podcast, so it's reasonable to think he didn't know.

And on the podcast Andreessen makes a pretty strong criticism of the Right (as well as the left):

> And the main principle of the right is that it hates the left. This is the old Buckley thing: the role of conservatism is to stand athwart history yelling stop. Which from the right you view as all social change happening around us is from the left, driving things further to the left. They’re all leading societies in directions the left thinks they should go, and that those things are bad because they’re against tradition, history, the way things have always worked and things that have been proven.

> So I think technology kind of gets trapped up in this dynamic. To your point, the left hates technology because they hate capitalism because they hate markets because they’re anti-egalitarian, we kind of slot naturally into that critique. And the right hates technology because it seems like technology is a tool of the left.


In what way did he hide it well? I’d best describe the story as “racist has a secret life where he’s even more racist”

https://twitter.com/RichardHanania/status/165754101074508185...


> In what way did he hide it well?

I don't know - I'm just going off the HuffPost article you posted where they exposed it ("Unmasking Richard Hoste").

> https://twitter.com/RichardHanania/status/165754101074508185...

Again, this was after the HuffPost article came out, and after the Andreessen interview.

I'd note that Hanania also interviewed Steven Pinker who I don't think anyone has accused of being a racist even by association.


Pinker associated with known racist Steve Sailer and there’s plenty of articles calling his views on IQ race science.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: