Hacker News new | past | comments | ask | show | jobs | submit login

What makes a project "modern"? Seriously curious, as it seems to often be used to describe projects/tools. Is it that the tools and languages used to build it are new? If so, should I care? I suppose if the point is to showcase a useful project in some new language/framework, then I'd care. But otherwise, do I? Like, what if this were built in some really old language and with ancient tools? Feel free to ignore this ramble, just curious what people think.



Hmm, TypeScript + deployed as a container?

Not cutting-edge, but definitely not obsolete, and does have obvious benefits over e.g. a traditional plain Python-based app which you need to package and host yourself.


What are the obvious benefits? I don't follow your example... you can run a Python app on AWS, directly on an EC2 instance or in a container, using Lambda, whatever.


Installing Python code and having all dependencies correctly resolved is a common source of problems and complaints.

OTOH URL shortener run as a Lambda looks like a good idea in many cases.


I hear ya, but still...I think I feel that you're overstating things. You can use pipenv or poetry or whatever to minimize issues with dependencies, bake into an image and run as a container. I've nothing against typescript or any other techniques/practices you might be alluding to, but choosing those languages/tools based on the kinds of benefits you're pointing to seems rather off to me. It's a bit of work (just a bit) to get deployments working correctly, but once you do, it's there and you can rely on it as part of your infrastructure. I think the decision of which language or framework is going to be used should be informed by something more than the benefits you stated (assuming you meant those are the primary ones) because those seem a bit weak tbh.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: