There were a lot of things i really liked about coldfusion, like how easy it was to build reports, and how easy it was to get started. cfdump is still one of my favorite debugging tools. Everything else, not so much :)
Egyptian is its own branch of the Afro-Asiatic languages, not particularly close to any Semitic language and today preserved in the form of Coptic as a liturgical language.
Ethiopian (presumably referring to Ge'ez) is a Semitic language but not particularly close to Arabic, and certainly not an Arabic dialect.
I don't think anyone knows what Trogodyte was. It may have been related to one of these other languages or it may have been totally different.
Hebrew, Arabic, and Aramaic (of which Syriac is a dialect) are all somewhat close but not mutually intelligible (they're more different than the Romance languages).
Median and Parthian are both Northwestern Iranian (Indo-European) languages, but it's not clear how similar they would've been at the time. Regardless, they're far from "arabic dialects", not sharing any common ancestors with Arabic within the last ten thousand years or so.
I don't know if you missed that she also spoke Koine Greek, but I think you probably know it's not an Arabic dialect.
Plutarch apparently corrected "Trogodyte" to "Troglodyte." [1] Which piques my interest even more -- she spoke "cave dweller" language? Looks like Herodotus uses the term to refer to a group who lived on the shores of the Red Sea, so that would make sense geographically.
Trogodyte really reminds me of the word troglodyte. I have to wonder if it was a dismissive term for a language spoken by a people considered primitive that she was said to speak.
Certainly not. This was hundreds of years before before the Arab/Muslim conquests. Perhaps they had Semitic roots, but consider Hebrew and Syriac (still spoken in small measure today) -- it would be absurd to call them dialects of one another.
Your net salary would be about 2900 euro monthly.
Then you'd need to pay for an appartment, it would be at least 400-500 euro.
Then you have to eat and sometimes buy new clothes since it's a cold country :) This would cost you maybe another 500 euro.
So you could save about 2000 euro each month.
Very neat. But the question is, how they pay the cost of the server? I mean, do you think a web service without any API keys, subscriptions, etc. is reliable?
I'm shocked to hear more and more people running an HTTP api from a $5 DO instance. It's enticing enough for me to learn, but I want to know, what makes golang so scalable?
I love the idea of just serving a production HTTP API from a single go file.
It's not DO. It's scaleway C1 arm server, even cheaper.
Golang produces native code with very good runtime with green threads which makes it very easy to do async programming and write efficient network code. But language won't save you from inefficient algorithms and dumb code of course.
> I love the idea of just serving a production HTTP API from a single go file.
You may have mistaken by single Go file in my service but it is actually a lot of code included spread across several libraries.
In order to write this service I had to write my own open graph library, oembed library, html parsing library etc..
!!! PHP MySQL extension doesn't support placeholders so everyone has to escape params before mysql_query and then put escaped params inside query string.
Of course if there's used mysqli or PDO then need to use placeholders but in other case - there is actually no choice for developer.
So I'd rather not call most of those - "vulnerabilities".
They're not functions, they're macros: functions that are called with their arguments unevaluated, and return code to be evaled in the environment of the call.
If you use a product and never caught a bug there then it might be that you don't need new version of the product?
In other case you'll be looking to fix that bug / contact product owner and you will eventually know if its abandoned / needs maintainer.
Was it something you were interested in? Replaced an alternate you were working on?
I find it hard to believe that a project you didn't create became something you actively wanted to support. On top of that, if the old maintainer really walked away completely, and they don't answer questions, you're walking through the dark.
The project I'm talking about is Postgres.app. It's a GUI wrapper around a PostgreSQL server, so there wasn't a lot of code; maintaining it mainly means I need to make new binaries several times a year. I didn't need a lot of help from the previous maintainer. (But I have rewritten most of the code since I started maintaining it)
It just was a great fit; I work on a PostgreSQL client; so it seemed like a good idea to help people get a server running too.
Late reply (this has dropped to pg 6), but here's to you . Our team uses postgres.app, and I know of a number of others who do too.
From my standpoint, it is shocking that such a popular and great gateway into the PG world is in this situation. Complex, enterprisey software is now just drag-n-drop and develop. Postgres.app is really good stuff.
You don't have a donate link, but if you're selling your front-end, please promote it.
