3 ms·
Come on now. With modern flow, you have to "install git", but in ye olde times you don't install svn or ftp? And back then we didn't have gatekeeping seniors? A
by npteljes 4y ago
Come on now. With modern flow, you have to "install git", but in ye olde times you don't install svn or ftp? And back then we didn't have gatekeeping seniors? And we request sudo now, and not back then? I think you got that confused.
Old software sucked a lot, and automation sucked a lot. Weird issues where you HAD to know what went wrong, because handholding was looked down upon. The lack of automation meant that servers were pets, you looked after them, groomed them, maybe even sang a song to get the piece of junk going. Modern automation means you mostly care about the blueprint, not the actual instance. If it's not working properly, you reimage. If you need more, fire up more instances.
Also, what can you do on the frontend only? I have two examples from the top of my head:
https://www.photopea.com/ https://www.photopea.com/
https://simplepdf.eu/ https://simplepdf.eu/
- 5350-uiop-1130 4y ago> Also, what can you do on the frontend only? I was talking specifically about React. But it's not a surprise that "modern front end" devs conflate React with JavaScript.
- npteljes 4y agoI see. I was confused by the statement before it: "no such thing as frontend development. only full stack." Getting back to the point, my simplepdf.eu example is indeed using React - according to Builtwith, it's built with Next.js, which is used to build React applications.