2 ms·
I really mean that, all those approaches using Perl, Java, .NET as stored procedures never gained much love among DBAs or the market in general, and I always fa
by pjmlp 2y ago
I really mean that, all those approaches using Perl, Java, .NET as stored procedures never gained much love among DBAs or the market in general, and I always favour approaches where I am not the only person on the building that can change something.
Also those approaches lack the end to end tooling, so you're basically back at printf debugging.
- hnlmorg 2y agoThat’s a fair point though it’s more of a practical argument when the topic was more academic discussion with regards to language design. But I do agree that practical considerations are important when making architectural decisions.
- pjmlp 2y agoThis is actually quite relevant to language design, too many people still get lost on discussing about grammar and language semantics, forgeting about everything else that is quite relevant why chose language A over language B.
- deleted 2y ago[deleted]
- hnlmorg 2y agoIronic you say that because usually we have the opposite positions with me asking you to have a little pragmatism. I’ll save this post and share it with you the next time a Go thread comes up. ;)
- pjmlp 2y agoShare at will, as professional, I am the first to chose C or Go if that is what the customer requires. It is the customer and their happiness to the service that matters, not what programming languages I enjoy using. Something that more people should actually think about, instead of proposing rewrites and then leaving when it isn't fun any longer.
- hnlmorg 2y agoOn that much we do agree