Why didn't VK make their own RESTful API?

Question

API

I am planning to redo the API of one project and wondered why VKontakte did not begin to make their API RESTful? Instead, they have designated a set of "ends" that can be accessed by both POST and GET.
For example, VK has separate methods wall.post , wall.get, wall.edit, wall.delete. According to the REST specification, instead of them there could be one end wall, and, depending on the HTTP method - respectively, POST, GET, PUT, DELETE - creation, reading, editing and deletion would be performed.
What do you think could have caused such a decision by VK?

Answer 1

Well, at least because many of their addresses accept values ​​as options that will not fit into the get parameter. For example 1000 user_ids in the users.get method.

Answer 2

There, half of the API call options simply won’t fit into restfull

Answer 3

For example, historical and chronological reasons + looking back at their internal architecture.