Fuck Swift is garbage. 😡

How did such a promising language turn into such a steaming 💩??

This may be controversial but I think open-sourcing it may have been a huge mistake.

Why is it that virtually all new languages in the last 25 years or so have a C-like syntax?

- Java wanted to sort-of knock off C++.
- C# wanted to be Java but on Microsoft's proprietary stack instead of SUN's (now Oracle's).
- Several other languages such as Vala, Scala, Swift, etc. do only careful evolution, seemingly so as to not alienate the devs used to previous C-like languages.
- Not to speak of everyone's favourite enemy, JavaScript…
- Then there is ReasonML which is basically an alternate, more C-like, syntax for OCaml, and is then compiled to JavaScript.

Now we're slowly arriving at the meat of this rant: back when I started university, the first semester programming lecture used Scheme, and provided a fine introduction to (functional) programming. Scheme, like other variants of Lisp, is a fine language, very flexible, code is data, data is code, but you get somewhat lost in a sea of parentheses, probably worse than the C-like languages' salad of curly braces. But it was a refreshing change from the likes of C, C++, and Java in terms of approach.

But the real enlightenment came when I read through Okasaki's paper on purely functional data structures. The author uses Standard ML in the paper, and after the initial shock (because it's different than most everything else I had seen), and getting used to the notation, I loved the crisp clarity it brings with almost no ceremony at all!

After looking around a bit, I found that nobody seems to use SML anymore, but there are viable alternatives, depending on your taste:

- Pragmatic programmers can use OCaml, which has immutability by default, and tries to guide the programmer to a functional programming mindset, but can accommodate imperative constructs easily when necessary.
- F# was born as OCaml on .NET but has now evolved into its own great thing with many upsides and very few downsides; I recommend every C# developer should give it a try.
- Somewhat more extreme is Haskell, with its ideology of pure functions and lazy evaluation that makes introducing side effects, I/O, and other imperative constructs rather a pain in the arse, and not quite my piece of cake, but learning it can still help you be a better programmer in whatever language you use on a day-to-day basis.

Anyway, the point is that after working with several of these languages developed out of the original Meta Language, it baffles me how anyone can be happy being a curly-braces-language developer without craving something more succinct and to-the-point. Especially when it comes to JavaScript: all the above mentioned ML-like languages can be compiled to JavaScript, so developing directly in JavaScript should hardly be a necessity.

Obviously these curly-braces languages will still be needed for a long time coming, legacy systems and all—just look at COBOL—, but my point stands.

So my friend had an idea for a game and asked me if I could help him develop it. Now, he understands how the code works and can even write quite a bit himself. On several occasions (including today) this happened:

*writes code*
*tests code*
Me: Hmm... this isn't working like it's supposed to
Friend: It looks pretty good, maybe check to see if everything is in the right order
*checks code*
*tries alternative solution*
*checks again*
Me and friend: Well this is even worse than before
*presses ctrl+z a lot to go back to the original*
*opens new project*
*writes new code for same purpose*
*checks code*
Both of us: IT WORKS!!!
*checks again just to be sure*
Both of us: IT STILL WORKS!!!
*compares new code to original code*
Me: It's the exact same code with different variable names!!! Why did this not work before?
Friend: No idea
*puts new code into main program*
*it still doesn't work*

Reasons Java makes me cry sometimes

Im taking an AP class for Java at my school. (AP is like an honors class). But there is an standardized test throughout the US that everyone takes. But it's so annoying because you are not allowed computers on the test so you have to HANDWRITE all of your code. So the way we "practice" for the test is in our class is we use a buggy ass program called greenfoot which is worse than writting in notepad because it crashes every 5 mins but only on Windows computers and since I go to a school and everyone it a retarded they all have Macs so my Windows laptop is a "non issue" like wtf. So now I just use intelij and tell the teacher to fix it but our school has a code where teachers are not allowed to touch laptops so he's just stuck right now.

Forgot to mention that the reason why we use greenfoot is because there is no auto fill features not even closing brackets automatically which "makes us learn better".

Also all of our tests are hand written which is annoying.

Worked all my life in C++/Java and for the first time in Android, finished the android app (ffs that's one messy framework)... now they give me an old macbook and send me into swift/xcode, I have been trying to connect two text fields and a button for 90 minutes, getting furious knowing I have to finish this app all over again for ios, please tell me how fucked am I? Is it better or worse than Android when it comes to a learning curve? I've googled this and usually it's fanboys fanboying, has anyone done both and has any advice?

P.S. I'm young and still tend to learn fast, but man this is really giving me shit, especially the IDE and interface builder which I despise as a concept, rather just write code instead of dragging and dropping...

GWT... And you know what is worse than that... SmartGWT.

Combine it with a client in government sector in French speaking African country who has an iPhone for 'his testing' and wants site to show french text on IE6 and newer because it's a government project and that's where shit must run.

Those who created it, I appreciate their intentions. But, you write things in Java, compile it and then separate the UI part and backend part. And if something breaks, which happens in most of the cases, no you can't just right click and 'inspect element'. Because it is IE 7! Now you try it out again, compile it, place it separately and wish your luck, which also sucks most of the time.

...and yeah, don't forget to clean cache in browser. I remember the time when to refresh content on Facebook, I used to clean cache and then refresh.

I'm a backend developer now, shit still sucks, but at least a lot of things are logical. I have a very high respect for UI developer, I really do, especially those who develop for Internet explorer.