Our great sponsors
-
-
ihp
🔥 The fastest way to build type safe web apps. IHP is a new batteries-included web framework optimized for longterm productivity and programmer happiness
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
As far as what makes it into production, those choices are usually more conservative. I can, for example, imagine a backend in say IHP haskell, and a front end in wasm-compiled yew rust, buuuuut more often than not, it's something like the LAMP stack, or like ASP.NET top to bottom. Nothing here will produce code that makes senior engineers cry of its beauty, but it will be code that any company can fill roles to work on, and is at least reasonably intelligible if you already know a C-based language. Things that would not be true in my extremely contrived example.
As far as what makes it into production, those choices are usually more conservative. I can, for example, imagine a backend in say IHP haskell, and a front end in wasm-compiled yew rust, buuuuut more often than not, it's something like the LAMP stack, or like ASP.NET top to bottom. Nothing here will produce code that makes senior engineers cry of its beauty, but it will be code that any company can fill roles to work on, and is at least reasonably intelligible if you already know a C-based language. Things that would not be true in my extremely contrived example.
I think the closest I've seen is languages that have features that let you write code that looks like a DSL (domain specific language) without actually being one, like ktor in kotlin. But even this is kotlin, a language largely used in android development, being used in an interesting and not-popular way. Once again, the pragmatism of picking something not the most "elegant" and "clean", but the most productive, legible, and popular, shows itself.