vorg

> if a patient in the study saw the word 'hippopotamus' written on a piece of paper, they could identify a hippopotamus in flashcards. But when that patient heard someone say 'hippopotamus,' they could not point to the picture of the animal

It's obvious the written word and the spoken word are stored separately in the brain. I remember once following a sign at a zoo which said "Hippo ---> ", and when we got there someone said "Wow, look at dat potamus!"

I can't tell what article this map is associated with. But it appears to be a summary of when various places on earth were first settled by each homo. Australia was first settled by the Aborigines about 50k years ago, entering via Southeast Asia. Much later, New Zealand was first settled by the Maori 800 years ago, entering via Taiwan, Southeast Asia (after the Aborigines' ancestors), and the Pacific Islands, though these migrations aren't shown on this very simple map.

> Nobody cares how many collections of 6 digits something has. 3 digits are what people care about. (Except where they care about 4

4 is a more common grouping than either 3 or 6. All of China and Japan and many places in between group their digits in fours.

And I always group the digits of hexadecimal numbers in fours.

The Aborigines of Australia migrated separately from the Austronesian people who colonized Indonesia, coastal New Guinea, the Philippines, Madagascar, New Zealand, and the Pacific Islands.

> Some people always talk down Groovy, yet the numbers speak for them self

Many of those numbers are fake. Groovy was #70 on the Tiobe index only 12 months ago, see [1], but is #16 now. How do you explain that? Groovy was last in Tiobe's top 20 about 2 years ago when the search numbers for "Groovy" from Baidu were hugely incorrect. Groovy later quickly dropped back out of the top 50.

[1] https://www.tiobe.com/tiobe-index/groovy/

The Apache project managers removed the new parser from the Groovy 2.6 betas over 6 months ago after officially canceling it and saying Groovy 3 would be the next release. But no real work has been done on Groovy 3 since then. I'm guessing they really intend releasing version 2.6 some time in the future. Perhaps they'll say "Groovy 3 is still far off and Groovy needs another release, so let's resurrect Groovy 2.6". Don't expect to see Groovy 3 move beyond alpha version anytime soon.

> The JVM is a highly-optimized, cross-platform, garbage-collected environment on which people have built much more progressive languages that lack the syntactic baggage of Java: Scala, Groovy, Clojure, Kotlin.

Apache Groovy has inherited all of the syntax of Java. When Jeremy Rayner built the Antlr 2 based syntax for Groovy back in 2005, he began with the syntax for Java, then added the Groovy-specific grammar to it. The latest version of Groovy still uses that syntax, so if Java has syntactic baggage, then Groovy has it too.

I'm picking Groovy will still have that baggage-laden syntax for a while yet. 2 yrs ago, Daniel Sun built an Antlr 4 based replacement grammar, but the Groovy project managers at Apache are taking their sweet time in rolling it along. They even had its optional preview removed from the version 2.6 beta of Groovy.

Both meanings can be expressed using a phrasal verb. To "hack into" something has the blackhat meaning, whereas to "hack at" or "hack up" something has the whitehat meaning. But to "hack" something, without the particle, only sounds right in the blackhat sense, e.g. "the hack the NSA" or "the hack a website". So I guess the noun "hacker" has the default sense someone who hacks into things/places.

Kotlin hit the sweet spot between the abtrusity of Scala and the sloppiness of Apache Groovy.

On the JVM, Beanshell has been around since the late 1990's so that's also over 2 decades. In fact, Apache Groovy was pretty much a clone of Beanshell, but with closures added, in its day.

Spring's AOP pointcuts (in its first incarnation as AspectJ) and Groovy (pre-Gradle and pre-Apache) are both over 15 yrs old. To not know those is having a skillset that's well over ten years out of date.

Good idea. I refer to Apache Groovy as "Bash for the JVM". The static typing features in Groovy were bolted on for version 2, whereas Scala and Kotlin were designed from the ground up for building actual systems on the JVM, so they're a far better choice for that.

Sounds like my story too (lost 25kg about 7yrs ago and kept it off). I generally rotate on a 1-week cycle. The only daily rules I follow are (1) never eat noodles more than once a day, and (2) eat some green vegetable/s once a day. I also never keep food in my apartment to easily avoid snacking, so some days when the weather's bad I'll only eat twice. When I go to an eatery (restaurant or canteen stall), I usually have the same meal every time, but there's about 10 different places I eat at, so I'm making the choice of what to eat when I choose which eatery to go to.

> more used than previously, though in different ways to how it used to

Are these new uses of Apache Groovy really what we would call "using" a programming language?

Although many "use" Groovy in Gradle, it's mainly 20-liners without any procedural code, so really only the parsing functionality is being used. Jenkins goes further by transforming the AST after parsing to such an extent that none of the collections-based functions work, and the runtime behavior isn't really Groovy at all. The adoption of Groovy in these uses is so dependent on the nitty gritty behavior of its Antlr 2.x -based parser that the Apache Groovy PMC seem to be stalling on moving along the upgrade to Antlr 4 in Groovy 3, keeping it in alpha mode for as long as possible, and even removing the optional Antlr 4 preview feature from the Groovy 2.6 beta.

Most other uses of Groovy out there use it like "Bash for the JVM". For building actual systems, sites use Java (with lambdas), Kotlin or Scala rather than the static typing that was bolted on for Groovy 2. Even dynamically typed uses of Groovy are losing momentum, evidenced by how few Grails 2 websites and plugins have been upgraded to Grails 3, and how few new websites have been built in Grails 3. The official download numbers for Groovy are grossly manipulated, and Tiobe's ranking for Groovy has been gamed in the past by faulty search numbers, e.g. 2 yrs ago it was Baidu giving bad results.

I suggest your view of Groovy's momentum might be skewed by what you see immediately around you, and not by overall worldwide trends.

It makes sense that it doesn't list joined words like bleary-eyed when its definition is obvious from the constituents bleary and eye, or inflected words because inflections like -ish and -ly each have the same meaning when modifying other words. But what about phrasal and prepositional verbs such as put off, put up, and put up with, where their meaning can't usually be deduced from the constituents such as put, off, up, and with ?

> we currently have 88k CJK characters assigned

If you also count the Unihan variations registered in Unicode's ideographic variation database by various Japanese outfits, encoded using the VS16 to VS255 characters after the codepoint they modify, there's another 8k or 9k unique characters assigned.

Do you expect anyone to believe the Tiobe index? They say Apache Groovy has risen from #60 a year ago to #16 now [1]. This is obviously wrong since software sites have been dropping Groovy for other JVM tech.

[1] https://www.tiobe.com/tiobe-index/

> "is-to-see" is not a contiguous unit

You can insert stuff between "is" and "to-see" (and between "to" and "see", I hope you agree) because English mostly parses into left-branching trees, which is the only reason why you can't insert stuff between "see" and "-ing". Natural languages don't liberally mix left-branching structures and right-branching ones because they're hard for people to understand. E.g. Pinker's "The rapidity that the motion that the wing that the hummingbird has has has is remarkable" is grammatically correct but not easily understandable. The contiguity or lack of it operates on a different conceptual plane to whether a "word" can be inflected or not.

> loose analogy

To take some example language from your reply, some people speak this as two words, others (e.g. some Americans) as a compound word. Because the concept of a word is not well defined, the boundary between morphology and syntax is blurred. Putting "is" and "to" noncontiguously before a verb is the same as putting "-ed" after a verb. They are both "inflections".

> There is no unit of English syntax which [...]

Here you're defining syntax around your orthographic definition of what a word is.

> "Is he really, in your opinion, to see her tomorrow?"

The opinion words "really" and "in your opinion" added into that syntactic structure parallel the manner that opinion word "bloody" is added into a lexical structure to become "abso-bloody-lutely".

> English has no inflected future tense like Latin and Romance languages. In linguistics, “tense” refers generally to how a verb is inflected

English has no inflected future tense because of the way words are usually defined. Verbs in English only have 4 types of inflections because words are defined as whatever is surrounded by spaces in writing. If we define words as the unit that carries a single beat in speaking, so "He is-to-see-it tomorrow" is 3 words, then verbs also have prefixed inflections. English then does have an inflected future tense.

The "is to" future form isn't mentioned in discussions on future tense very often but seems to have the most predetermination, whereas "is going to" and "will" indicate more volition by the doer.

> the names of all Apache® projects, software products, and their logos are trademarks owned by the Apache Software Foundation on behalf of our project communities. Note that while some Apache project names and logos are registered in the US and various countries, even unregistered names and logos are still trademarks of the ASF and should be treated with respect.

Only trademarks registered with various legal jurisdictions are enforceable, such as the "Apache TinkerPop Gremlin" name you registered. Unregistered marks used by an Apache project are simply claims on the mark, which in many cases are not enforceable. One example is the Apache Groovy project, where its PMC members erroneously claim the exclusive use of "Groovy" for their programming language, when in fact their only valid claim is to "Apache Groovy" (and its previous monikers "org.codehaus.groovy" and "Codehaus Groovy").

The link didn't work from my part of the world so I couldn't read it, but the title is self-explanatory, so I'll make a point which you may have already made. Previously constructed languages like Esperanto use vocabulary sampled from European languages only, which I suspect is why they haven't become popular. A new language would need to take words and grammar from non-European languages also, such as Arabic, Swahili, Chinese, Japanese, and Indonesian, in order to be adopted in any meaningful scale.

You could use a struct with private fields, e.g.

  type Users struct{
    dict map[string]*User
    list []*User
  }

and attach methods to both access the data and coordinatedly update both forms, e.g.

  func (us *Users) byID(id string) *User { ... }
  func (us *Users) sortedByID() []*User { ... }
  func (us *Users) addUser(id string, nu *User) {
    dict[id] = nu
    list = append(list, nu)
    ...
  }

You inadvertently submitted this twice -- there's another link ( https://news.ycombinator.com/item?id=19177937 ) for the same from 12 hrs previously.

But making the Central Valley as desirable as the Bay Area to live in would help the housing problem. Do this by building not only housing, but better infrastructure (roads, rail, schools) and create incentives for Bay Area businesses to relocate there (including the stick for those that don't).

> Was this something they were seriously expecting in the coming years?

I started high school a few months after the last time anyone walked on the moon. If you'd told me then that no-one would ever again walk on the moon in the following fifty years, I'd have told you you were nuts. The general mood in the 1970's was that humankind would start to inhabit space over the following decades, and space colonies like these would be orbiting the Earth. Instead, the only humans publicly known to be in space right now are the 3 aboard the International Space Station.

> a tribe that always specified the direction [...] eventually she acquired something like a bird's eye view in her mind

Even when the language you speak doesn't have this requirement, you can still pick up this skill. When you live for a few years in a cold square-grid city like those of northern China, you learn to always know which way is north so you don't lose direction walking around connector overpasses and subway tunnels in the winter.

The British Empire and the United States spoke the same language. Their homelands, i.e the places where they make up the majority of residents, are the same: the British Empire with its American colonies then, and the United States and its "special relationship" with the U.K. and other Five Eyes nowadays. The leaders of the American Revolution were leading British Imperialists immediately before, e.g. George Washington led the 1760's campaign against the French in the Mississippi valley.

Even a 1k line project is unmaintainable when written in Apache Groovy.

> For a lot of existing Java code, it's as simple as renaming the file to .groovy

This causes the program to run in dynamically-typed mode, much sloooower, so why do it? You'd have to add @Static annotations everywhere to get anything approaching Java-like speeds. One of the Apache Groovy project managers has long since wanted to make Groovy statically compiled by default, but that's never going to happen because they're running an unofficial go-as-slow-as-possible in the official upcoming upgrade to Groovy 3.