Comment by Lee on failure #1693
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
avatar:
You made some important points about the .NET stack, which I too struggle with. Been using it since version 1.0, but now I feel like I wish it could be interpreted during development - and of course that'll never happen.
So, what is your next tech stack? This is a VERY important conversion, one we've been having internally here for years.
.NET is (no longer) as agile as it was, and neither is Java, Rust, Go, etc. (even though awesome and fast in production). So what else? Python is wonderful in dev, but terribly slow in prod. Rails is nice, but it's just not "a thing" in most companies, and there's no talent. What else? Bear with me, don't laugh... There's Perl which is old, but it's blazing fast and also modern due to massive investment by Amazon; still, can't use it as no talent. So what's left? Again, don't laugh... It's old and has a bad reputation from the old days (and Wordpress), but it's also modern and is object-based if you want it, and kept alive as it's the foundation of Facebook, and has every tool you need, and countless threads on StackOverflow, and as much talent as you want... it's PHP. I feel sick admitting it, but it looks like that's our next backend platform.
What are your thoughts? Might make for an interesting discussion in the wider community, I wonder what people are thinking about this.