Seems interesting. HN seems to be a buzzing hotbed of Kotlin stories since the Google announcement. I can't help but feel that it looks a lot like Swift on the JVM, without some of the nice data structure literals for maps, lists, etc.
In my experience, Golang's Windows support is actually fairly poor. I think it is largely to do with the clunky interface that is CGo. I found Rust to be less "warty" by a large margin with good library support in a lot of areas. Your mileage may vary, of course.
This is not what I experienced so far. I use Golang on both Linux and Windows (50/50) and I didn't have any problems. What are you referring to exactly?
As I said, YMMV but the biggest standout that I remember was trying to play sounds using the windows API. There weren't any packages our team could find that really did it correctly, the one that everyone pointed to leaked memory like crazy and it was hard for us to track down since it relied on bouncing back and forth between C and Go so frequently (making malloc/free lifetimes difficult to follow because C can't know what things have been GC'd by the Go runtime)
> please break down these pleasant chunks of unreadable code into model properties and use them here and anywhere else where you have such kryptonian blocks. Good code is readable, semantic, and easy to follow and update. I pitty the poor soul who would have to participate here with you :). I, for one, would probably delete and start over to spend less time. I know there are situations where it's unavoidable but this one clearly isn't the case. Python really is beautiful, Python is english...write me some poetry please.
> You have a lot of repetitions of datetime objects that can be stored in a variable. You have a lot of comparisons on the object that can be stored as model properties. Separate them and let these methods breathe please. This looks like callback madness in js. I can't even follow the parenthesis to grasp the flow of conditions here. Even my IDE formatter left me.
Wow. If I saw someone code review like this on my team, they would get one warning. If this behavior was repeated, then they would be fired. There is no place for condescension in the team, even from Senior -> Junior level developers. If anything, this is a great stepping stone for (kindly) teaching a jr. member how to refactor into code that is more readable. Unnecessary jabs like "i pity the poor soul... clearly this isn't the case... looks like JS... even my IDE formatter left me..." and snide hand-wavy remarks like "python is english.. write me some poetry" are only useful to stroke e-peens and push people down publicly.
What would have gone a lot further, in my opinion, was refactoring the code then sending it to the jr. dev and telling them that you refactored their code for them. Tell them that - if they'd like - you'd be happy to walk through the changes and explain why those things were helpful/useful. It's not a contest about who can write the best "poetry". It's about getting along, helping each other, and getting work done.
Jr. devs, if you are reading this, please don't despair. I promise that all teams aren't this bad to work on. There are places where you don't have to be afraid to be the butt of a joke in an HN post and you will actually learn things. If your team is more like the one in the post, you're much better off just leaving for your own sanity.
Not just enriching, people are blowing Apple out of the water in regards to adding new capabilities to the iPad. This app makes the swift "playgrounds" look even more laughable.
Just ran into this and was about to post it - Wow. Looks really good. It seems like he embedded an IL interpreter to get around the AppStore limitations. Amazing work.
This is really great stuff. I've been working on a small 2d SDL project in C++ and this has given me a lot of pointers, as well as opened my eyes to the power of Nim for tasks like this.
It seemed somewhere in between C and Python. Really cool.
