Earlier quoted context omitted.
Have you gone to production with it yet for your backend? Curious Android dev here.
Not yet, but zero issues so far. Currently running Spring Boot 2M7 on AWS EB just fine. I was surprised how smooth it went.
Re: Moving from PHP to Go and Back Again
271–280 of 281 posts
Re: Re: Moving from PHP to Go and Back Again
#272Earlier quoted context omitted.
When a language is set loose to the world it belongs to its users, and whatever they decide to do with it. Anyone is free to just fork Go and do whatever they feel like with it, regardless of what Rob thinks. That is the beauty of MIT license. So given that Oberon is accepted as a systems programming language in computer science, with multiple published papers and books across two decades, heavily used in OS research…
Your concerns have already been answered. Most succinctly stated by two points. 1) A lot of things work, it doesn't make them good ideas. 2) Go doesn't meet the strictest litmus tests of a systems language, never did, never will. It's only a systems PL only if you relax your definition of what it is. Go's own creator says it's not and if any one person is the authority on this topic it's him. There are platforms that…
I only care about what Computer Science books and ACM SIGPLAN papers accept as systems programming languages, not random opinions in online forums.
Thankfully both of our opinions are meaningless to Go users.
Re: Re: Moving from PHP to Go and Back Again
#273Earlier quoted context omitted.
But when the language/tooling enforces it, you've made language choice a proxy for style choice. A large part of what makes me stick to Ruby over Python for example, is that I can't stand languages with significant indentation. It may seem minor, but it isn't to me, to the extent where I avoid Python whenever I can. When your language enforces formatting like that, people will choose or choose away the language over…
> A large part of what makes me stick to Ruby over Python for example, is that I can't stand languages with significant indentation. More like 'consistent indentation' methinks. I still have nightmares about trying to merge some GSOC student's code from their branch to trunk where the indentation was all over the place, it was so bad that lint couldn't even figure out what the hell they were up to -- well, I think li…
Re: Re: Moving from PHP to Go and Back Again
#274Earlier quoted context omitted.
But when the language/tooling enforces it, you've made language choice a proxy for style choice. A large part of what makes me stick to Ruby over Python for example, is that I can't stand languages with significant indentation. It may seem minor, but it isn't to me, to the extent where I avoid Python whenever I can. When your language enforces formatting like that, people will choose or choose away the language over…
Go enforces a style because all code, written across different teams and organisations, should look the same so anybody can pick up anybody else’s code and read it with ease. There are no differing styles in different libraries. It’s very harmonic. What I can’t stand in other languages is the Laisser-faire attitude regarding styles. Some people put whitespace here, some there, some put the curly brace here, some ther…
Making people who care about formatting to the extent I do refuse to use the language is the cost of tools that enforce those kind of rules.
That's of course their choice, just as it is mine to stay clear of tools (and languages) I don't consider worth my time.
Re: Re: Moving from PHP to Go and Back Again
#275Earlier quoted context omitted.
Your concerns have already been answered. Most succinctly stated by two points. 1) A lot of things work, it doesn't make them good ideas. 2) Go doesn't meet the strictest litmus tests of a systems language, never did, never will. It's only a systems PL only if you relax your definition of what it is. Go's own creator says it's not and if any one person is the authority on this topic it's him. There are platforms that…
If people cared about litmus tests, whatever that means, JavaScript would never have left the browser. I only care about what Computer Science books and ACM SIGPLAN papers accept as systems programming languages, not random opinions in online forums. Thankfully both of our opinions are meaningless to Go users.
Re: Re: Moving from PHP to Go and Back Again
#276Earlier quoted context omitted.
If people cared about litmus tests, whatever that means, JavaScript would never have left the browser. I only care about what Computer Science books and ACM SIGPLAN papers accept as systems programming languages, not random opinions in online forums. Thankfully both of our opinions are meaningless to Go users.
It doesn't matter what people like yourself think or attempt with a given technology. This is about technological definitions. Go is not a systems PL by the strictest measures available, that's a fact. Designers of C++, Rust, D and Go for the most part agree on that. You're the only odd man out. Redefining terms or loosening the standards for quality is an intellectually deficient venture. Some may partake in that, m…
Re: Re: Moving from PHP to Go and Back Again
#277Earlier quoted context omitted.
But a pokemon character was rather unkind to it back in 2012, so here you are. Two years after that, Mickens wrote a glorious takedown[0] of Javascript--which must not have been as glorious as I thought--since people still seem hell-bent on using in as many places as possible. Alan Kay said that computing is now a pop culture... [0] https://scholar.harvard.edu/files/mickens/files/towashitalla...
I mean, the way people bash PHP and praise javascript is completely ridiculous. The two languages are comparable at best in the amount of warts they have, while my firm opinion is that the js ecosystem is the most horrible thing in the world.
Re: Re: Moving from PHP to Go and Back Again
#278Earlier quoted context omitted.
But a pokemon character was rather unkind to it back in 2012, so here you are. Two years after that, Mickens wrote a glorious takedown[0] of Javascript--which must not have been as glorious as I thought--since people still seem hell-bent on using in as many places as possible. Alan Kay said that computing is now a pop culture... [0] https://scholar.harvard.edu/files/mickens/files/towashitalla...
I mean, the way people bash PHP and praise javascript is completely ridiculous. The two languages are comparable at best in the amount of warts they have, while my firm opinion is that the js ecosystem is the most horrible thing in the world.
Re: Re: Moving from PHP to Go and Back Again
#279Earlier quoted context omitted.
Not yet, but zero issues so far. Currently running Spring Boot 2M7 on AWS EB just fine. I was surprised how smooth it went.
Correction: found an issue with bean validation. https://github.com/spring-projects/spring-boot/issues/11343
Re: Re: Moving from PHP to Go and Back Again
#280Earlier quoted context omitted.
Still parroting that old trope, huh? The quality of an engineer is rarely dictated by their tools. You can be an excellent engineer with a shitty language, or you can be a terrible engineer with a great language. I'll be the first to admit that PHP certainly has it's share of really bad developers, but what language doesn't?
It is an old trope - I completely understand your point, but the fact is: wherever you're professionally going, PHP is not the language you'd like to use anyway. So why use it? I could see how doing FORTRAN for a banking institution is a good way to make money; but PHP doesn't even have that. Most of my closer friends with a Computer Science degree would probably try to stay away from PHP: neither does it pay better…
Unless you're doing web development. Outside of the HN bubble, there's still a very active segment of the software industry that uses PHP. Yeah, it's not a "cool" language or whatever, but experienced PHP developers can churn out solid work very quickly.
I made pretty good money as a PHP developer for a lot of years - you would not believe the places that this language gets used (and in what ways). "Dying business" is definitely not how I'd describe my past employers.