Hacker News new | past | comments | ask | show | jobs | submit | pskisf's comments login

Malo periculosam, libertatem quam quietam servitutem.

- Thomas Jefferson


Roughly translates to: I prefer liberty with danger to peace with servitude/slavery.


The right to be insecure is one of the least appreciated in our time [1].

[1] https://www.ted.com/talks/eve_ensler_what_security_means_to_...


> "Malo periculosam, libertatem quam quietam servitutem."

malo ... quam ... ⇒ I prefer ... to ...

Preferring what to what? This is why all other words are in accusative singular as simple enumeration:

periculosam ⇒ dangerousness

libertatem ⇒ freedom

quietam ⇒ quietness

servitutem ⇒ slavery

Hence I would take his statement as: "I prefer dangerousness and freedom to quietness and slavery."


I prefer dangerous freedom over quiet slavery.


periculosam and quietam are adjectives (the comma is wrong)


Thank you for the correction.


And perfectly translates to: Better dangerous liberty than quiet servitude.

Not sure why you needed to make such an awkward rough translation when the concepts are clear, the idiom known and the sentence so short in the target language, which is the language of the author as well, thus sharing bias in its latin...

But I think this sentence is itself dangerous in its shortness, it almost makes you believe it's a discrete dichotomy rather than, as usual, a loooong gradient between two extreme, with orthogonal concerns adding to it to make it a zigzag. Better very rich in a quiet dictatorship than middle class in a chaotic old democracy, for instance. Or better poor in a clientelist theocracy than poor in an industrial dictatorship.

It doesn't really make sense in the end, since freedom and servitude are not related to danger or safety. You can have all together, at different time or degree, for different people and geographies, regarding different slice of concern (freedom is so so vague, for instance).

"Better have what you can tolerate for what you can afford, than something unaffordable or untolerable", is probably more interesting to understand the compromises real people make everyday, but I guess, so obvious we prefer to dream of a dichotomy :D


I don't know the quote, I was just translating the Latin for people.

I have to say though, since you come off as quite rude: It doesn't "perfectly translate" to any single thing in English.


The issue is not whether they're intrinsically orthogonal or principle components, but that men make them so.


The slaveholder and rapist Jefferson deserves the Noble Prize in Hypocrisy for his ramblings about freedom and liberty.


https://pski.net/2011/11/01/parkshark/

ParkShark was a parking space sharing iOS app. The technology was sound but the market timing was a little early. We were even talking to some larger delivery companies about a business-side component. The product failed because the two founders, myself and a friend, are engineers through-and-through. We just didn't have the passion for the business side of things to really make it happen.


I was a master of Atari Video Olympics on the 2600 system. Time to come out of retirement?


Pah!! I was master of Daley Thompsons Decathlon!!


I still program the 68K today in K&R C. I recently released a Dropbox client for Tandy XENIX.

http://pski.net/trs-box-xenix/


TRS-XENIX was Tandy's implementation for their Model 16/6000 MC68000 based line of business machines. Here's a video of my working Tandy 6000 system.

https://www.youtube.com/watch?v=mM1IH8frd_U


The TRS-80 is still alive! Everyone come listen to our TRS-80 focused podcast TRS-80 Trash Talk

http://www.trs80trashtalk.com


You're doing it right for your application! MySQL or PostgreSQL would most probably be slower and introduce a lot more overhead as they are client/server oriented systems. Don't listen to those armchair architects!


True from my experience as well. If you're going to invest in a Data Scientist, you want the cachet of having a Phd in that role.


Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: