I once had a professor. He's a certifiable genius. Genius for the usual reasons, certifiable because he does his web development in awk, as God intended. You can still, in 2018, cgi-bin your way to victory. But you'll be doing it alone. *Nothing* gets done for you.
-
-
Show this thread
-
Do you want to deserialize JSON? Doesn't come out of the box in AWK, better write and maintain one yourself. Do you want to access a database? Better write and maintain one yourself. Do you want to charge credit cards? Stripe doesn't have an AWK binding, so... you get picture.
Show this thread -
It's not just the code, either. When you go to HN or Stack Overflow or a Slack of your choice to ask people how to X and give your assumption, they'll say "You wouldn't even have that problem if you were on a modern stack." This is not inaccurate. It may or may not be helpful.
Show this thread -
When you try to hire people, you will find folks with the skill level you want at certain aspects of the job (product sense, say) will *recoil in horror* from the technical choice you made.
Show this thread -
Technical choices within the realm of plausibility are basically fungible, particularly for intermediate to senior engineers. Python, Ruby, Node, whatever, it's a web app. But if you accidentally 5 years as a maintenance programmer in a bad stack, there is non-zero career risk.
Show this thread
End of conversation
New conversation -
-
-
The community definitely makes assumption with regard to the size of the tech stack you want as well as how much you'll want to scale. As someone newer to webdev, it can be hard to figure out what you can cut out if your product is only serving 50 people to start.
-
Polite disagree unless you mean a very, very specific question [0]; the number 50 is indistinguishable from 50,000 on every system you'd reasonably consider using in almost all cases, so you just default to the 50k case. [0] "Can I use sqlite in production?"
- 4 more replies
New conversation -
-
Show additional replies, including those that may contain offensive content
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.