> The point is far more likely to be lost if I simply straight-up tell
The prerequisite for the point being lost or you jumping straight to the point is you having a point in the first place and that doesn't seem to be the case from the comments you have posted so far.
You seem to imply people care too much about TED yet the only one who keeps up bringing TED is you.
I also find it amusing you seem to have disdain and a feeling of superiority to startup bros and their emojis yet from a cursory glance, it doesn't look like you are doing anything out of ordinary or have achieved anything worthwhile yourself.
There are people who find "the alchemist" deep and life changing and there are people who find it trite and useless. You seem to be the first kind and I am latter. Nothing could come out of this conversation for you or me, so I will sign off now.
> If you don't have a cola each day, you can dribble into a towel for another 3 years when you are older.... No thanks, Ill take the coke. put it on the reapers tab.
If anything, an unfit person is slowly dribbling in a towel throughout his relatively shorter life.
You live a shorter, low quality life. I don't see how you see that a positive over living a longer, healthier life with may be a bit of suffering at the end compared to suffering throughout your life(out of breath, joint pains, clogged arteries...)
That footage is from a rally but every weekend, fwd cars with 800/1000cc engines and a peak torque of about 70 Nm do it just fine. Most of the cars have 2-5 occupants decreasing the already low torque/kg, and almost the whole climb is done in a bumper to bumper traffic(no momentum for the climb).
I had to read up on react, then on redux, then on es2015/babel, then on browsrify, then on gulp, then on eslint, then on sourcemaps, then on flow, then on react-router...It was a lot of effort, but I am liking it so far. The important thing is we can build applications in ES2015 which is a better language than the browser's js implementation and still get to debug it on the browser(sourcemap and specific devtools). My impressions of react-redux so far is it makes implementing a TODO list harder, but it will be better suited for applications with lot of state.
True there are conflicting choices and advice, but I think all this will stabilize in a year or two and despite the naysayers, the future seems bright. And it's not a take-it-or-leave-it deal - if you are happy with Backbone, keep using it. You can choose to just integrate gulp,babel and browserify for es2015 goodness. You might not like react but like how redux does state management - just integrate that in your existing application.
Most of the tools are orthogonal to your framework choice. Use tern for completion and analysis, use eslint for linting, use browerify/webpack to pack your assets...
Why have you added redux for such a small and simple project? What are you getting from react-router-redux - why do you feel the need to sync the the browser's URL into the data store?
You didn't 'have' to do any of these, especially for a project of this size. I can now understand why people might feel fatigued when they needlessly create overly complex solutions.
Haven't used flask in some time now, but most of your objections are missing the mark.
> GLOBALS: Flask has a lot of globals (from flask import g, request, current_user, etc.) A better web handler function looks like this handle(request) -> response. Any other web framework that I know does it like this.
Flask's request is not global. I have had this discussion with someone else before:
FWIW, flask's "from flask import request" never had been a blocker for me, whereas django's injected request variable had made me write middleware to preseve requests as thread locals so that I can access it elsewhere. Werkzeug does the same thing, except it does it more robustly.
> MIDDLEWARE: Flask promotes writing middleware as decorators functions, while it looks nice, it not really useable anywhere else, and its not really a standard. At least you can still use WSGI middleware.
I don't see an issue. If you can solve it using simple python(decorators), solve it using Python.
> BLUEPRINT are nice, but have issues: When you create a blueprint, for a sub app, you cant set error handlers. They only work on app level. Also (small issue) You cant add blueprint specific middleware.
Rather than calling app.before_request, you can call blueprint.before_request and it will work only for that blueprint.
> SITEMAP @route has disadvantages For big apps, its nice to have a single routes.py file where you can see all urls the app supports, and which methods
Then don't use the decorator. Have a routes.py and call app.add_url_rule
I have had a template with all of this from some time back
> publishers have the right to respond, either by blocking access to ad-block users
All the best with that. The number of sites on which I will have to disable ad-blocker because you won't show the content otherwise is in single digits.
Nobody is against publishers blocking access to ad-block users. But if 80% use ad-blocks, you block out your entire audience and let it surf to the competition who figured out how to serve ads that are not making people puke (ie. sponsored stories, endorsements, non-intrusive ads, social selling etc.)
It really is the fault of publishers that people hate internet ads.
I think it's the same reasoning with paywalls. I stopped going on pando when they paywalled. I don't see why I would pay to read Paul Carr feuding against the Intercept, the entertainment value is mild, and frankly I would better use my leisure money at the pub or for renting movies.
I don't think I have any exception to my ad-blocker. I have not yet encountered something I want bad enough to make an exception, and asking me to make an exception is a reminder that I'm the product, which is not exactly the most positive call to action.
There's someone around who matters more than you: Googlebot. Google wants sites to serve users and Googlebot much the same page, and will penalise sites who don't.
> it genuinely interests me how Vi users put up with the constant need to strain their pinky to switch to command mode.
Is it any different from how emacs users put up with Ctrl/Alt?
You aren't looking to switch, but if anybody is, install this https://github.com/tpope/vim-rsi for basic keybinding in insert mode. This is quite a short file. If you want, you can simply copy it to your .vimrc. For non-basic movement/editing, switch to normal mode and edit.
Biggest problem for me when I first used evil was learning that C-g is what I need to press when I accidentally hit an emacs chord sequence and want to abort. I had to google a few times to find that out when Esc wouldn't get me out of the minibuffer.
What is there to learn about the terminal? You learn the shell, coreutils, shell scripting, sed, awk, editor...Learning these isn't a measure of competency. If you just want name dropping, John Carmack works in Visual Studio, Notch works in Eclipse.
The prerequisite for the point being lost or you jumping straight to the point is you having a point in the first place and that doesn't seem to be the case from the comments you have posted so far.