Artur Minosyan
Artur Varkezovich Minosyan (Russian: Артур Варкезович Миносян; born 4 August 1989) is a Russian professional football player of Armenian descent.
| Personal information | |||
|---|---|---|---|
| Full name | Artur Varkezovich Minosyan | ||
| Date of birth | 4 August 1989 | ||
| Place of birth | Novorossiysk, Russian SFSR | ||
| Height | 1.78 m (5 ft 10 in) | ||
| Playing position(s) | Midfielder | ||
| Senior career* | |||
| Years | Team | Apps | (Gls) |
| 2007 | FC Spartak-UGP Anapa | 22 | (0) |
| 2008 | FC Krasnodar-2000 | 15 | (0) |
| 2009 | FC Chernomorets Novorossiysk (reserves) | ||
| 2010–2013 | FC Chernomorets Novorossiysk | 87 | (9) |
| 2014–2016 | FC Volga Nizhny Novgorod | 57 | (4) |
| 2017 | FC Torpedo Moscow | 8 | (1) |
| 2017–2020 | FC Chernomorets Novorossiysk | 45 | (2) |
| * Senior club appearances and goals counted for the domestic league only and correct as of 9 August 2019 | |||
Club career
He made his Russian Football National League debut for FC Chernomorets Novorossiysk on 4 April 2011 in a game against FC Gazovik Orenburg.
He made his Russian Premier League debut for FC Volga Nizhny Novgorod on 10 March 2014 in a game against FC Amkar Perm.
gollark: Tape Shuffler would be okay with it, Tape Jockey doesn't have the same old-format parsing fallbacks and its JSON handling likely won't like trailing nuls, no idea what tako's program thinks.
gollark: Although I think some parsers might *technically* be okay with you reserving 8190 bytes for metadata but then ending it with a null byte early, and handle the offsets accordingly, I would not rely on it.
gollark: Probably. The main issue I can see is that you would have to rewrite the entire metadata block on changes, because start/end in XTMF are offsets from the metadata region's end.
gollark: I thought about that, but:- strings in a binary format will be about the same length- integers will have some space saving, but I don't think it's very significant- it would, in a custom one, be harder to represent complex objects and stuff, which some extensions may be use- you could get some savings by removing strings like "title" which XTMF repeats a lot, but at the cost of it no longer being self-describing, making extensions harder and making debugging more annoying- I am not convinced that metadata size is a significant issue
gollark: I mean, "XTMF with CBOR/msgpack and compression" was being considered as a hypothetical "XTMF2", but I'd definitely want something, well, self-describing.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.