Absolutely. The biggest criticism of KonMari from Japanese is "no duh." Even the techniques for things like folding and arranging clothing so you can see everything at a glance are common knowledge among Japanese. Baffling.
People need to be reminded of obvious things. In this case especially because there is active pressure to collect things - from your typical BigBoxCo flyers, sales, TV doorcrashers, buy-one-get-one events, etc. I know too many people who are simply drowning in junk, so if it takes a half-cultish trend to get them to unload - then so be it.
For most of human existence the ability to find sweet and fatty things and eat them as much as possible and put on as much weight as possible kept you alive. Now it hurts you.
Similarly with stuff for most of human history stuff was expensive, you kept every good thing you could possibly get. Then in the past 60+ years stuff has dropped in price amazingly and keeping everything is no longer a good tactic.
Space has become more expensive that stuff in places where you can get good jobs.
A huge proportion of people reading this could go out and buy a caravan or a new car in cash. Few of us can afford a good place with much space in SV or NYC or Sydney or London.
The amount of work required to fold and put away laundry is absolutely insane. Especially in a household of 5. It's more efficient to just stuff everything into any drawer that has space, and rifle through all your drawers and closets when you want to get dressed.
My life goal was to keep both clean and dirty clothes in baskets. Take from the clean basket, wear, put in dirty basket. Run dirty basket through wash. Dump cleaned clothes in clean basket. No more time spent folding, organizing or even putting stuff away.
My girlfriend was not a fan of the system when I described it. Alas, I still need to fold laundry.
My family of four solved that by just HANGING everything.
We use one of these http://www.amazon.ca/dp/B00578QVGC in my kids room. On the top bar is the out of season clothes, and on the bottom bar, which is at an accessible height to my girls (4 and 6), we put the in-season clothes.
This works really well since little kids are way better hangers than folders. So when I take laundry out of the dryer, I basically make a pile for the kids clothes and then yell at them to hang everything up. They love it and it saves me lots of folding time. Plus, no wrinkles!
We got rid of our space-stealing dresser and just have a little plastic set of drawers for socks and underwear, which probably could just be in stuffer bags hanging off the clothesrod now that I think about it...
I've seen that. It looks like it is just as much work to take things out of the dryer, turn them inside out if necessary, and load them onto that machine. And separately deal with types of clothing articles the machine can't handle.
It's a lot like a dish washer. By the time you scrape and pre-wash and load all your dishes, you could have just washed them and put them on a drying rack. The real value of a dish washer is it serves as that drying rack. Most kitchens don't have a lot of dedicated space to dry dishes.
I wish I could find it, but the CEO Phil Libin gave a talk about how to price goods. He split pricing models into 3 camps, based on how they deliver value over time:
1. Fixed price goods correspond to items where you realize the value upfront, then over time the good decays. Like food, physical goods like clothing, etc
2. Fixed price subscriptions correspond to services which deliver constant value over time, like a newspaper or utilities
3. Freemium subscriptions start free, then charge more money over time, and correspond to services which deliver increased value over time. Lots of free 2 play games work this way, with people paying hundreds of dollars as they get serious. He also argued that Evernote was in this camp, since as you store more of your information in Evernote, it becomes more valuable to you
So charging a one-time fee for evernote is mismatched with the value delivered. They would get payment as a one-time event but the more you use it, the more it costs them to support you, without you paying them more because you like/need it more.
Only looking at lifetime value delivered ignores the competition, much of which is free and easy to switch to.
Also support costs typically go down over time; most support effort is spent in onboarding and getting users up and running. Although now that you mention it, Evernote may have huge technical drag because they have bugs outstanding from over six years ago. Indeed, the only time I reached out to support (I couldn't install PC version because it was incorrectly detecting that I already had it installed) they weren't able to assist. $10 lifetime value may be a bit generous.
I've been fighting this fight for over 17 years now. The landscape has changed a lot - mostly for the better IMHO. In particular, issuers are taking more responsibility for checking the validity of the cards but some of them are hopeless and there is still a way to go.
Criticise me all you like but I still have a blacklist of countries where I will never send physical goods to (unless they direct deposit the money, for one of my sites).
Not sure if it's relevant for "subscription" model businesses but Stripe and a couple of other providers have an option to charge the card immediately or just get authorisation for the amount. The authorisation is only held for seven days, but I have found that this has often been enough for the owner of the card to notice and cancel the authorisation before the charge happens. I haven't checked but this could also solve the "instant feedback" problem for providers that give it as "authorsied" is less conclusive than "charged" for the scammer.
Drupal at least provides you with a fast prototyping experience. Data fields for everything, and connectors to all kinds of external services, validated in some cases by years of production grade usage. Caching, databases, clustering, high-availability... All solved and mature.
The only thing you don't get for free with Drupal is a backend which you can speak to if you're deciding to go the SPA route later on.
Which, in my personal opinion, is a pretty stupid trend anyway. SPAs tend to grow to Java Enterprise levels of complexity very very fast, and things break All. The. Time. Not to mention you're putting huge amounts of work to the frontend, where you virtually cannot account for cross-browser behavior, people with multiple-year-old browsers... and people with devices older than two years!
Leave a Drupal project idle and unmaintained for a year, and you'll be able to pick up where you left it. Good luck doing the same with an AngularJS SPA - you might get away if you used npm shrinkwrap when you left, but the first npm update WILL kill your code with a billion possible places to fix.
Drupal is mature, and maturity is something that the entire Javascript development and tooling community is missing unless you stick to plain jQuery.
Stability and reliability IS a thing, especially in enterprise.
Go the hipster way when your target audience is hipsters, go the proven, old-school way when your target audience is enterprise.
edit: ad maturity of Drupal and support... D6 got released in 2008-Q1 and support ended in 2016-Q1. That's EIGHT YEARS of continuous support and security fixes, and I expect similar if not better support timeframes for D7.
Good luck finding a Backbone.js or Ember.js (and maybe even AngularJS) developer in four years from now; not to mention that during the entire D6/7 lifetime backwards-compatibility-breaking changes were a rarity in Drupal when all of the mentioned JS frameworks have had more than their fair share of clusterfucks stemming from bad design. Or just the tooling environment, breaking changes everywhere and (gut feeling) every month there's a new tool to learn or best practices revamped.
Wonder why PHP, server-side rendering and SQL is so prevalent? You can rely on buying a solution and having support and developers even in multiple years from now. Enterprise doesn't want ever-changing piles of crap layered in more piles of crap, enterprise wants stability and maintainability. And enterprise is where the money is, not some SV startup only surviving on VC or with 90% of its customers startups only surviving on VC.
I have a turbogears app from 2008 that I still occasionally maintain. It's not officially supported, but it works, and I find Python to be nicer than PHP by enough to be worthwhile. I wouldn't use Javascript because it's awful, but if a small, immature framework suits your needs I wouldn't avoid it just because it's small/immature. Either your app won't be terribly important, or it will be; in either case you're sorted.
If you want to ever have a safe upgrade path that doesn't involve months of testing then you absolutely need a type system, IMO. The only framework I've felt completely safe doing major upgrades on is Wicket - which, not coincidentally, is the only framework I've ever known to make extensive use of final classes and final methods (Java), to enforce that it's only possible to use it in supported ways.
Javascript SPA applications get less respect from business owners than they deserve.
People see JS and throw their JQuery & some CSS developers at it. Or they use their backend PHP devs who've never written code that runs for longer than one request.
Either way you end up with code written by people who don't understand some of the fundamentals of UI programming.
Angular gets the worst of it because it's the most popular framework. It's exacerbated by the fact that Angular doesn't offer suggestions for a lot of common problems.
I live and breathe Angular SPA applications -- the vast majority of developers that work with it cannot comprehend a well-designed and usable Angular application.
Proper error handling, sane state management, and keeping the codepaths short and easily grok'd is very difficult with Angular -- especially for larger applications. This results in blackholes where users find themselves in strange spots that are inescapable other than a full page refresh.
These are either developers dipping their toe into the front end after living in the back end of things their whole career, jQuery dudes hastily breaking into SPA development to stay afloat in an environment the submitted article exactly mentions, or simply lazy developers that couldn't be bothered due to tight deadlines/budget/whatever.
Angular is popular enough that someone who could distill a reasonable set of concepts and practices for working with it could probably reap some significant rewards in the education/training marketplace.
But if proper error handling, sane state management, and keeping codepaths short are actually "very difficult with Angular," maybe it's not the comprehension powers of the developers using it that are falling short.
A framework should be actively making those things easy.
Exactly. Server-side rendering is incredibly fast with modern browsers which makes a bunch of SPA sites completely infuriating. There are a few things that make sense like little button actions using AJAX but most of the page should just stay as a normal HTTP HTML request.
Leave a Drupal project idle and unmaintained for a year, and a new, non-backwards-compatible Druoal version has been released and you'll need to rewrite everything.
I don't have experience with Drupal, but it says "plan for periodic upgrades of their project to the latest major release (every 6 years or so)". So, even if a new release comes out, you have _literally several years_ to decide when to make a switch. For perspective, Backbone.js was released 5 years ago!
But the "old" major version will still be supported for a very long time frame. In the case of D6, it was supported over five years after the release of D7.
Just coming here to give Backbone.js some credit. It is one of the most mature of the frontend frameworks, because it does almost nothing. It's what I'd call feature complete, its core probably will not change or grow much from here (in a good way). jQuery and Underscore back it, which also aren't changing or going anywhere. And as another commenter point out, it's 5 years old already, still in production all over the place.
What do you suppose you should do when people start demanding interactive features and capabilities that can only be done client side? For a lot of us the alternative of doing things on the server is a significantly worse UX.
> What do you suppose you should do when people start demanding interactive features and capabilities that can only be done client side
You are free to use jQuery in your theme (aka frontend code), or D3 for visualization, or any other JS stuff you may need. On a private project, I'm using a current jQuery, D3, and SCSS and it works quite fine for me.
The only thing in D7 that can be a major PITA is proper multi-language support, because it's a bit sparsely documented.
Ironically the 4chan crowd who create most of the world's shareable GIF content are either banned from Twitter because a feminist got outraged or have left of their own volition.
Sorry — that'll be the search trying to get a singular term from a plural.
I've tagged the images with singular terms to make them easier to search, so it will change terms like "bridges" to "bridge", or "men" to "man", unless I override each term. If anyone can suggest a better way, I'd be very grateful.
I'll add "Australia" as an override, for now. Thanks for pointing it out.
stemming will be baked in to a search engine, for example elasticsearch or solr dependent on the language analyzer you use and how you map your fields.
Wow. I feel like an abuse victim that has just had an intervention. Now that you mention it, I've seen this phenomenon at almost every open source project I've peeked into over the years. I need to sit down for a bit.
"Are you seriously using that coupon company instead of Groupon?"
This was the bitchy-voice Groupon sales rep phoning me direct when I used a different coupon service in Japan. I asked whether she was talking about the same Groupon of "Great Osechi Ryori Disaster and CEO's Fake Apology of 2011"-fame and it shut her up real quick.
So many things wrong with this company, failure couldn't have happened to a more deserving bunch of people.
