@jhnns
flexbox all the things
Nothing here yet.
Nothing here yet.
No blogs yet.
I'm using Martin's hint for a year now and I think it's awesome. I think you should never install something globally that you are going to need for a specific project. I just install some things globally to also do prototyping or some testing.
That's a very technical POV. Accessibility for your websites, for example, may be unnecessary from this POV, because it slows down your developers. However, I think we all agree that it is our duty to not exlucde people with disabilities. Same goes for supporting old browsers. Take mobile browsers, for instance. There are a lot of manufactures that don't ship OS upgrades for their devices. Should we exclude these users and require them to buy new devices, creating a lot of unnecessary electronical waste? For me, the critical line is crossed when the manufacturer stops shipping security updates for the software. Than we should also refuse to support these legacy browsers, because they are a risk to the user's security.
For government/legal content, legacy browser support is a must Yes, but it depends on the definition of "legacy browser". There is a time when a browser is even too old to be a "legacy browser". Or are we supposed to support the Mosaic browser for government sites as well? :) And I think this question is about the definition of a legacy browser...
External CSS file Agreed. Also, HTML files as entry points are still a big problem. A true module bundler for the web should also understand HTML as entry point :) It would be cool to use webpack also for simple, static sites. This is already possible but it feels like a huge hack.
Yes, diversity drives innovation! We should not think Open Source in a "corporate" way. It's all about ideas. For instance: I really appreciate rollup's efforts on scope collpasing . Other projects are able to benefit from its insights. Personally, I haven't discovered the real benefits of JSPM yet. I think it's misleading to say that JSPM is future proof, because imho ES2015 module loading semantics have not been figured out yet. Browser vendors and node.js contributors are still struggling with the actual implementation of the loader spec (that's at least what I can tell from my point of view).
I've founded a small company with my friends. We're focused on JavaScript development and work for several clients. We try to develop as much as possible Open Source, but it's not always possible depending on the actual client. Besides working for clients, we also teach at the local university and are organizing monthly meetups like Web&Wine or the Nodeschool Munich / Augsburg . Unfortunately I don't have any productivity hacks. If you know one, let me know :). I would like to do much more Open Source, but there is little time. Recently, I've started to focus my efforts on projects where I'm the "main" maintainer.