Peppa Pig is at least funny. The one that pushed me over the edge wrt to behavior modeling was Caillou. My god people have some self respect as parents. You have to have to create some boundaries for children, not just knee-jerk syrupy-sweet coddling from dawn til dusk.
> It is bad practice to have your authentication database be the same as your app database.
No, this is resume-driven-development, Google-scale-wannabe FUD. Understand your requirements. Multiple databases is non-trivial overhead. The only reason to add multiple databases is if you need scale that can't be handled via simple caching.
Of course it's hard to anticipate what level of scale you'll have later, but I can tell you this: for every tiny startup that successfully anticipated their scaling requirements and built a brilliant microservices architecture that proactively paved the way to their success, there's a 100 burnt out husks of companies that never found product market fit because the engineering team was too busy fantasizing about "web-scale" and padding their resume by overengineering every tiny and unused feature they built.
If you want to get a job at FAANG and suckle at the teat of megacorporations who's trajectory was all based on work done in the early 2000s, by all means study up on "best practices" to recite at your system design interview. On the other hand, if you want to build the next great startup, you need to lose the big co mentality and start thinking critically from first principles about power to weight ratio and YAGNI.
We did not publicize it in any way because we are a legit film streaming company with hundreds of distributors worldwide, and no good can come from any awareness of a site that looks like ours streaming pirated content. Maybe some day.
I switched to Notational Velocity years ago after trying to type things into Evernote, yet I am a premium user. Why? Because Evernote's killer feature is pasting in any kind of content and syncing that across devices. It is an extremely useful dumping ground for miscellaneous pasted content.
It's not about people who don't know what computers are. It's about creating simple solutions to common problems. Most people do not want to fiddle with their computers regardless of how well they understand them, they want to accomplish a task and move on. Even as a developer this is why I choose OS X over Linux.
The question is how far can they push it without totally frustrating the power users. I think it may be inevitable that Apple eventually stops making machines that the majority of non-Apple developers can tolerate.
I don't think that is what is being done. Making things better is something that can be enjoyed by all users, not just "regular" users.
This part of ComputerGuru's post is what resonates with me:
> But my biggest pet peeve is just the sheer dumbing down of things. iTunes 11 is pretty, but why put everything a click away? What was so bad about a sidebar that makes everything instantly accessible and only takes 80px? Why does the app now prefer to be run in full screen?
Some things are legitimately being improved. Network configuration in all of the major operating systems is a great example of this. NetworkManager is wildly better than manually editing a wpa_supplicant file, and Windows/Macs have seen similar improvements. Not "Better for 'Regular Users'(tm).", just "Better.".
There seems to be a sort of schizophrenia in the field of "improving" computers. On one hand you have people who are honestly just trying to make things better (and are, for the most part, succeeding). It seems to me like you fall into this camp. You see value in changing things to improve the situation for everybody. I totally dig that attitude. However on the other hand you have people who are trying to make things better... for people who are perpetually trapped in the 90s. The improvements these people create are the ones that concern me.
Both are trying to improve things, but the attitude towards users is very different. I only mean to attack the second camp of "software improvement"; I think their motivation is flawed, outdated, and toxic.
> If something with Drupal's advantages were available within Rails (as an engine or what have you) it would be a clear game-over for other stacks vs. Rails.
I have to disagree here. There are clear use cases for either Drupal or Rails. I understand why you yearn for a Ruby Drupal, because dealing with PHP is a hassle, but objectively there is little to be gained since Drupal is already a beast and performance would only be hurt by being ported to Ruby.
Aside from that, the key advantage that Rails or other low-level web frameworks have over Drupal is that they don't make any assumptions beyond the fact that you are using HTTP. With Drupal there is an incredible amount of pre-existing architectural cruft to enable its powerful functionality, but it creates a ton of overhead to deal with as soon as you want to do something that doesn't neatly fit it's paradigm. As soon as you brought something like this into Rails then you'd be defeating the purpose of its simple elegance.
I just don't see any way to separate out the best of both worlds. They have very distinct use cases.
To be clear, I don't want it in Rails core. I want someone to make a framework that can run in Rails where I can pull in giant duplo-blocks of functionality.
Aside from PHP being around twice as long and around for years during the nascent phase of open source web apps, the number one reason it has more and more popular turnkey apps is the same reason it "killed" perl: easy deployment.
The secondary reason is indeed cultural, but not it's nothing so abstract as what 37signals does. Rather it's the technical culture of moving fast and breaking things. With Rails you need to stay on top of upgrades all the time. If you are actively working on an app then this is a net benefit because you get new features. But it also creates maintenance work downstream, and not just with application code, but application servers are also relatively unstable. When you have something with a high heterogenous installation count like WordPress or other popular open-source apps, the pain of maintaining version compatibility and keeping it running over time far dwarfs any benefit of using a more powerful language like Ruby.
You would still have an update problem with wordpress since it's a very popular attack target. One of the things that has made me shy away from using it is fear of running into a problem like "we need to upgrade to version X in order to fix a security issue, but version X breaks plugin Y".
I guess what I was mainly getting at was that prior to around the time that rails and 37s got going the idea of paying monthly for web based Saas hadn't really exploded in the public consciousness (of course this was due to many factors other than 37s and rails).
So web developers who didn't want to do consulting would naturally think of the shrinkwrap type model first as a way of selling software.
I know as well as anyone the relative futility of relying on HN, Reddit, or TC coverage for building a successful tech product. Feedback and traffic from social news is merely a blip that says next to nothing one way or another about your long-term prospects.
However, if your site goes down for any reason a postmortem of this sort is definitely warranted. The word "launch" is not signifying much more than a point in time in this case, and I think you're jumping to a lot of conclusions about what hopes they were pinning on this event.
