notsotrue

While I love Rails, I've stepped away from it over the past couple years in favour of smaller frameworks. While it's nice to have a kitchen sink approach when it applies, for SPA's, I found I was using very little of the sink, and the sink often got in the way. Is Rails 5 doing a better job of letting you pick what parts you want, or is it still predominantly focused on an all or nothing approach?

I illegally use marijuana, not for the pain relief, it's not any more effect in my case than a bottle of Jack. But it gives me a pocket of time where I can just feel okay, mentally, knowing that I will never live another day without pain.

The medical community focuses too much on symptom/treatment, and not enough on quality of life. I'm not saying that marijuana is an answer here, and I completely accept anyone who says I'm just using my pain as an excuse to get high, but it lets me feel emotion again, something you wrap up so tight in order to deal with the pain, you forget how to laugh and cry.

I suffer from avascular necrosis, where my large bone joints are dying from a lack of blood flow. The bone breaks down (sever acute pain), chews the shit out of the cartilage (chronic inflammation pain), and movement exacerbates both. I still do the excises, as each joint will eventually be replaced, and strong muscles decrease dislocation chances, but this provides no pain relief, and only causes to fatigue the muscles. After 7 surgeries, 3 joint replacements, you begin to realize that the average person has no idea what pain is. A broken bone isn't pain, it's an inconvenience.

I refuse to use opioids anymore, I can't code on them, they muddle your brain. But I wouldn't wish this life on anyone, not even the morons who glibly state that all you have to do is not take drugs.

A tad hyperbolic, don't you think?

They already have, and I'm not cheaper because I'm currently focused on node.

Given the other data points, you can assume javascript.

How so? Depending on where you live, going cold will kill you far far quicker, than going hungry. If the arguments are on need, then the need for shelter here in Canada trumps the need for food, by a long shot.

Yea, no. Grocers in low income areas shoulder the burden, while grocers in high income areas don't. The poor, subsidies the poor. Brilliant.

Well, the terms section is certainly misleading. I prefer to see data where the plural is grouped with the singular. Looking at the chart, VR ranks above drone(s). VR has no commonly used plural, so without combining singular and plural terms, and without the raw numbers displayed, it's not a useful chart.

Why not, food isn't the only item at the bottom of Maslows pyramid. Food being the only one you can steal. The rest must be acquired through currency.

So who pays the grocer? It's both unlawful, and unethical to place the burden of feeding hungry people on the shoulders of the grocer as a cost of selling food.

So when I'm freezing to death, it's not okay to steal money for shelter?

So the grocer is going to sue 1000 insolvent hungry people? For what exactly?

I'm curious, what would you consider a complex app?

Please refer to other posts.

You may not, but you don't live in Canada. Here in Canada, food is secondary to shelter. If you have the energy to steal, you won't die today. However, if you have no shelter in -40, you're dead. You can't steal shelter, but you can steal money to exchange for shelter. So, yea, you do have a basic biological need for money...

Is it? Here in Canada, an empty belly won't kill you if you have the energy to steal, but the -45c nights will absolutely turn you into a popsicle. And you can't steal shelter. But you can steal money to provide a roof.

So you place the burden on the grocer, and absolve the state and the thief?

I agree, basic income is the answer. But this judgement isn't logical or sound.

What I think is that the burden should be shouldered by the state, and not small business owners. What this ruling does, is place the burden of caring for the 'hungry' on grocers, which is an unfair burden. Unless the courts decision came with a way to compensate the grocer, this ruling is idiotically naieve.

In many jurisdiction around the world, people get stoned for having sex. Just because some jurisdictions allow something, doesn't stop it from being murder.

Agreed, I'm all for basic income, and social safety nets. But stealing them, isn't the right answer either. The burden should be on the state to provide those necessities, not the local business owners.

By this logic, money theft is 'not a crime' if poor.

Implicit vs explicit binding.

I'm looking forward to trying this out. Having written Ember, Angular, and React apps now, I feel like they are all getting closer, but a lot of rough edges still exist.

Ember: interesting framework, but all too often, you would hear a team mate say "wait, why is that working, it shouldn't be?" Mixed with equal parts "logically, that SHOULD work, what am I missing?"

React: I love the component focus, and redux is pretty slick. However, the insistence on using JavaScript in lieu of helpful abstractions that clean up the code for easier maintainability, is frustrating. The whole point of JSX is syntactical sugar, but the team went with half measures. You also end up with a lot more plumbing code than the other two. Sure, I can reuse some of these components, but in truth, most of your components will be single use.

Angular 1: by far the easiest and most intuitive. Enough magic to make setup and a basic app easy, but not so much magic that you can't figure out why something is working. However, the more complex an app, the less Angular 1 serves. And you really need to use directives as a component, and follow a more react pattern, or you're going to have a bad time. Also, the dependency injection is a nice thought for simple directives, but when you're done, you'll very likely have so many dependencies being injected that unit testing becomes burdensome. And if it's burdensome, it won't be done as much as needed.

All that being said, if your app is primarily collecting data through forms, you can't beat angular. If it's highly dynamic, and you want a more native feel to your app, react is the clear winner. Ember is a neat, but I won't be using it again.

Angular 2 doesn't fix all of my complaints, but it's getting closer.