Isn't the problem of including only the code the component actually needs already solved with dead code elimination? So the framework authors can include new features but as long as your component doesn't use them the code for those feature does not end up in the final bundle you serve to the user.
I sure am missing something here because the author of Svelte is actually also the author of rollup.js [1] which does exactly that, it eliminates dead code via its tree-shaking mechanism.
As far as I understand, ReactJS is a tightly weaved 40kB chunk of code which will be delivered to the browser no matter how ferociously you shake the tree.
Unfortunately, UI frameworks are extremely hard to modularize in a way that makes them amenable to tree-shaking. So you're left with the alternative – cobbling together your own pseudo-framework out of 'small modules', which loses all the ergonomic advantages of a good framework. As you might imagine, I've been thinking about this problem for a long time :)
It's silly that the wifi owner has to opt-out of wifi sense. Because it's not like it's already difficult enough for a non-techie to securely configure his access point, no, let's add another thing he has to care/know about.
And the way to opt-out is even sillier: you have to append _optout to your SSID. The SSID should not be used to control the clients behaviour imho.
Unfortunately nothing changed (neither in bash nor python repl) after i installed it. I followed the installation steps 1-3 on Ubuntu 14.04. Does anyone know what i'm missing?
I'm really interested in how you managed to start out on yourself. Care to share your story?
When I was 19 I managed to get a developer job at a medium-sized german dating site. I'm 22 now, still working on the said dating site, so my experience is pretty niche and limited and so are my connections. I'm actually pretty strong programming-wise (PHP and JavaScript professionally and Clojure(Script) and Go on the side.) But I completely lack any experience with business and design other than reading HN and blogs.
My goal is to get into freelancing/consulting the way patio11 describes it: make thing-X which will make/safe client-Y Z-amount-of-money. The challenge for me is:
- how to get experience in making thing-X without having the connections to get client-Y
- how to get client-Y without having the experience in making thing-X
What worked for me is simply learning as much as I could and keeping an eye out for opportunities to turn pure tech engagements into more business-focused and value-based projects. Once you start looking, you realize they are plentiful. Even just being a good programmer who can evaluate features and prioritize based on business value puts you way way way ahead. If you're reading a lot of patio's writing, you're probably on the right track. It can take some time to make the transition, but it will happen if you keep at it.
I'm pretty excited about Atom Shell as it looks like they fixed the different js context problem that node-webkit had. The last time i tried node-webkit i was really annoyed by the sneaky bugs that pushing objects from one context to the other introduced.
This. Enlive and now Kioo are elegant solutions to the problem of letting designers and programmers work independently. It still amazes me that something like Enlive hasn't popped up in other languages/frameworks.
I have often wondered the same thing. I created enfocus and kioo to solve the exact problem you stated. How do you get designers and programmers work efficiently together? This is particularly difficult with single page applications.
I sure am missing something here because the author of Svelte is actually also the author of rollup.js [1] which does exactly that, it eliminates dead code via its tree-shaking mechanism.
[1]: http://rollupjs.org