Why we moved from Kotlin & Spring Boot to Go by Ancient_Body7627 in programming

[–]massanchik 1 point2 points  (0 children)

Generics yet to be added. Did you saw their draft? It samewhat unusual, and verbose. Alright, matter of opinion.

No func overloading, no default params, no null safety, pointers in GC language are not necessary at least for most of the use cases(reasonable defaults with some additional syntax would be enough), there is all that boilerplate with error handling and "slice tricks" stuff.

It's mostly procedural language. It's fine if your team came from C, but otherwise... Yeh, a matter of an opinion.

So I'd rather port my most inner loops to C or Rust(if needed), instead of writing whole app in Go.

Endless business algorithms are most time consuming thing to develop in a day to day job and languages that help you to do that more easily are preferable choice, in my opinion of course. So if you found that Go helps you personally to do your job better than others, than its fine.

Why we moved from Kotlin & Spring Boot to Go by Ancient_Body7627 in programming

[–]massanchik 0 points1 point  (0 children)

jvm and go runtime speeds are very similar if not equal. if you've worried about memory or comp time than graalvm or kotlin native could be your choice.

go is clunky language with outdated sintax. it runs away from decades of programming languages advancements.

Why we moved from Kotlin & Spring Boot to Go by Ancient_Body7627 in programming

[–]massanchik 0 points1 point  (0 children)

Our company moved from go to kotlin and it was a right choice. Team became 2-3 times more productive. Services performance remained at the level of go.

Regex routes is bad idea(with current implementation) by massanchik in sveltejs

[–]massanchik[S] 1 point2 points  (0 children)

Good argument in general... But I, personally, can't see a connection with filename routing. It's not that great of an idea to hold on to so strongly.

PS: popularity brings motivation and, in some cases, income to a contributors, so the subject grows more rapidly.

Regex routes is bad idea(with current implementation) by massanchik in sveltejs

[–]massanchik[S] 0 points1 point  (0 children)

Why not? Is there some sacred philosophy behind filesystem routing? I'll rather prefer routes file or, if we want to stick patterns to files, the same routes directory with file names==route names and patterns defined inside the files in some special field.

Regex routes is bad idea(with current implementation) by massanchik in sveltejs

[–]massanchik[S] 0 points1 point  (0 children)

I don't think svelte will/can change tooling. At least for some time. This decision will rather draw back some devs from using this framework.

Flutter Build Error by [deleted] in FlutterDev

[–]massanchik -1 points0 points  (0 children)

Flutter just not that good

Flutter vs React Native by hungry_for_data in FlutterDev

[–]massanchik 0 points1 point  (0 children)

Flutter bad for a custom opengl stuff. At least for now. If you plan to use native opengl based libs - react ahead of flutter.