I already have "Scroll Anchoring" enabled in Chrome's flags, wish they'd add a flag just to disable page's ability to override scrolling completely.
Unfortunately "Scroll Anchoring" will likely never make it to a production build as it has odd interactions with sites that override scrolling to jump to new page elements (adverts in particular).
> Losing weight is actually pretty simple. But I won't argue that it is hard.
It depends on the genetics, but yes, if you're really overweight, losing lots of weight is generally pretty simple. At some point, though, you'll hit a roadblock and that's when those nuances can become important.
Because npm is a package manager that most devs already need present for their front-end build step (to install their deps for gulp/grunt/browserify etc) , and bower is an 'extra' thing that addressed a need that no longer exists.
What I hate more is the thought of having my financial data stored in some shady, cobbled together, cloud service, hosted somewhere on Amazon AWS.
I predict, that it is only a question of time until they will encounter some disastrous data leak.
Begin a YNAB user for more than a year now, I am really angry at them for this move. So I'll guess I have to move on to something else after the support for the YNAB4 apps will be shut down.
I completely agree. We've got support until December so I'm considering replicating as much of YNAB 4's methodology and functions as possible in either Excel or Google Sheets when I have free time.
One benefit with each line being valid JSON is that writing a reader/generator for this format is fairly simple. One can use existing JSON libraries as-is, with some extra consideration to the line-like nature of this format.
For the above to work you'd have to use a custom JSON-parser when reading the lines.
------------
Could also be mentioned that JSONLines-like formats are already pretty common in log-files, database exports etc. So this is more about giving it a name and standardizing it. Which I think is great!
>> For the above to work you'd have to use a custom JSON-parser when reading the lines.
Not necessarily. You could just re-add the square brackets before passing the lines to the JSON parser.
That would make more work for the machine, because you'd probably have to copy the whole string. But any time you can make less work for the human by making the machine work a little harder, it's usually a win.
You can't. At least not in modern open plan offices, nobody except management loves.