> We are working out a proposal that is somewhat similar to async-await in C#. Again, we hope to finalize that in time for the next rev of the standard. Details as soon as coherent articles explaining it all can be put together.
It's good that Firefox can be customized, for sure. But I'm finding that after each major release these days, I need to perform more and more customization just to bring it back to a usable state.
I want a practical browser that does what I need it to. Yet with each new release of Firefox we tend to see further useful functionality stripped away, additional config panel options removed, and the UI dumbed down in one way or another. So whenever an update happens, it's off to searching for add-ons to basically undo whatever unhelpful changes the developers have just made.
Add-ons and customization should be there to enhance and already good piece of software. They shouldn't be there as band-aid that's applied to fix the numerous mistakes and bad decisions of the software's developers.
Funny, we're having the exact opposite experience.
I find that with every release of Firefox, I need less and less addons. Better dev tools? Okay, goodbye Firebug. Download popover instead of a different window? Goodbye DownloadStatusBar. Australis? Goodbye Firefox-button mover and FXChrome (I use Tree Style Tabs, but FXChrome make everything else look prettier anyway).
I gave up on config panel removals and UI dumb downs and now configure Firefox solely using about:config. I recommend you this approach. You will get much less annoyed.
You're right, that is generally a better option these days. Unfortunately, it still does suffer from the same problem, to some extent. Settings are sometimes renamed, and then it takes some time and effort to track down the new name, assuming the setting (or an equivalent) still even exists.
I see this comment every time for many of years in almost every discussion about using JSON for configuration and while YAML is certainly used by many projects most of the people still continue to use JSON and I think that's because YAML sometimes feels like Scala of serialization markups when people just want something like Python. I personally think that TOML[0] is not only more simple but also as easy to read as YAML and we use it in our projects without any issues.
TOML is ok too, though I still like YAML better personally. I honestly didn't really like ini files much at any point, even when everything on windows used them, so TOML starts from an unhappy premise for me.
I'd with the design would be more dense, it's a nice design and I understand that designers did it deliberately because they know whitespace does matters, but when it comes to web sites like Github I think the most important thing is functionality and not the cute and modern look. With the old design on my 13 inch MBP I could see 6 repos with the new design - only 5
I think that's not a problem with significant whitespace, but the problem with CoffeeScript syntax. I'm programming in Python and had been programming in Coffescript and I always found Coffescript code much harder to read than code in Python. I don't know exactly what causes this, but my guess is that indented blocks of code in CoffeScript can appear after any line, so you don't have visual anchors that will indicate where one block begins and other ends. In Python however, indentation is always comes after keywords like def, if, class, for etc... and those are always highlighted by your editor so your eyes can always catch the block start very quickly.
Yeah, I have this issue too, though I'm using stable Chrome, I thought that if this is a bug it must be already reported, the funny thing is that I tried to google it and all I got was some articles about web-fonts and icon fonts rendering problems.
Usually most of the people realise the need for this kind of tools when they are facing a need/requirement to develop a single page web application (SPA). If you don't need to make one then it's ok to use jquery or even add some PJAX to make your web site look more snappy. But if you have to develop a SPA, then you can't go far with jQuery because it just wasn't created for this type of things, you have to think about models, templates, about application state management and all other stuff, this is where frameworks like Ember and Angular shine.
