Ljubavi (Idoli song)
"Ljubavi" is the B-side of the last single by Serbian band Idoli.
| "Ljubavi" | |
|---|---|
| Single by Idoli | |
| from the album Šest dana juna | |
| B-side | "Ona to zna" |
| Released | 1985 |
| Recorded | 1985 |
| Genre | Pop Rock |
| Length | 3:35 |
| Label | Jugoton |
| Songwriter(s) | Vlada Divljan |
Track listing
- "Ona to zna" (2:55)
- "Ljubavi" (3:35)
Personnel
- Vlada Divljan (guitar, vocals)
- Srđan Šaper (vocals, backing vocals)
- Zdenko Kolar (bass)
- Branko Isaković (bass)
- Ivan Stančić Piko (drums)
- Boban Đorđević (drums)
- Đorđe Petrović (keyboards)
- Dragan Ilić (keyboards)
- Dragomir Mihajlović Gagi (guitar)
- Vuk Vujačić (saxophone)
gollark: I mean, it's better than C and stuff, and I wouldn't mind writing simple apps in it.
gollark: Speaking specifically about the error handling, it may be "simple", but it's only "simple" in the sense of "the compiler writers do less work". It's very easy to mess it up by forgetting the useless boilerplate line somewhere, or something like that.
gollark: Speaking more generally than the type system, Go is just really... anti-abstraction... with, well, the gimped type system, lack of much metaprogramming support, and weird special cases, and poor error handling.
gollark: - They may be working on them, but they initially claimed that they weren't necessary and they don't exist now. Also, I don't trust them to not do them wrong.- Ooookay then- Well, generics, for one: they *kind of exist* in that you can have generic maps, channels, slices, and arrays, but not anything else. Also this (https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/), which is mostly about the file handling not being good since it tries to map on concepts which don't fit. Also channels having weird special syntax. Also `for` and `range` and `new` and `make` basically just being magic stuff which do whatever the compiler writers wanted with no consistency- see above- Because there's no generic number/comparable thing type. You would need to use `interface{}` or write a new function (with identical code) for every type you wanted to compare- You can change a signature somewhere and won't be alerted, but something else will break because the interface is no longer implemented- They are byte sequences. https://blog.golang.org/strings.- It's not. You need to put `if err != nil { return err }` everywhere.
gollark: Oh, and the error handling is terrible and it's kind of the type system's fault.
References
- Ex Yu Rock enciklopedija 1960-2006, Janjatović Petar; ISBN 978-86-905317-1-4
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.