4 ms·
It's just some guy's side project. He probably doesn't make any money on it, doesn't care about the tech stack (which is from 2013), doesn't want to pay a lawye
by strken 9y ago
It's just some guy's side project. He probably doesn't make any money on it, doesn't care about the tech stack (which is from 2013), doesn't want to pay a lawyer for advice, and couldn't be bothered working out how to package all the data for release to users.
If you administer a free service that takes an hour a month to keep running, and suddenly you're faced with an immediate upfront time cost plus the likelihood of spending many more hours every few months responding to user requests, shutting your service down might be a rational decision when you would otherwise have kept it running.
- lokedhs 9y agoThis is a bit offtopic and I apologise in advance for that. However, I felt the need to comment on the assumption that an application that is only 5 years old would imply that it uses a tech stack that no one would care about. How is it that after a quarter of a century of web development, that the state of the software used is so bad that people still assume that something that is a few years old is assumed to be useless?
- strken 9y agoI might have been a bit unclear there, sorry: if he built it as a side project five years ago, he either knows that stack pretty well by now, or has decided that it wasn't very good, and either way wouldn't care to work with it solely for the tech. Five years ago I was messing around with Fortran 2008. Having done so, it's not as interesting anymore. That's not a function of Fortran, which was created when my grandparents were 20-somethings, but of the time spent with it.