295 karma · joined August 15, 2011
[ my public key: https://keybase.io/whostolemyhat; my proof: https://keybase.io/whostolemyhat/sigs/rYfSAiH2dJJuMkjqveEVSmh08oNEoxJAFK_igakxnDY ]
The only way around the poor performance of table layouts is to use table-layout: fixed, which then means you lose all responsive layout so you'd need to create a new version for every screen size you wanted to support (and implicitly, not be able to support every size of mobile screen since percentages don't play well with fixed layout. In this case, you haven't saved any time and in fact have created more work for yourself along with a worse version of your site since fewer people will be able to view it properly.
[1] http://www.stubbornella.org/content/2009/03/27/reflows-repai...
You can still assign/use global variables in the browser, but like the parent says, this is the browser's fault - having to accept old and badly-written code for compatibility reasons.
If you absolutely must tell the world that you don't like JS, at least be interesting or actually list your reasons so there's something to discuss.
1. You don't have a girlfriend
2. You blame an entire race for your cousin being raped
3. Women were promoted
4. You feel society owes you thanks and praise.
But you're not a spoiled child.
My feeling is that backend development is overcomplicated/overbloated. Specially with the big players (AWS, Play). Lucky me, I found my way with PHP. Simple, elegant, lightweight and fast enough. You don't need a lot of complicated boilerplate, nor learning a new template language or syntax.
I make around £2 a month from ads on these articles, so it's not exactly lucrative :)
Remote: Yes
Willing to relocate: No
Technologies: Javascript (Node, ES6, React, Redux, Webpack), Python (Django, Flask), HTML/CSS, SQL
CV: https://uk.linkedin.com/in/james-tease-b048a032
Email: james@jamestease.co.uk
Github: http://github.com/whostolemyhat
Website: https://www.jamestease.co.uk
I'm a freelance full-stack web developer with around eight years experience in everything from setting up servers, creating APIs and CMSs and building frontends.
For the last couple of years I've mainly been involved in large-scale SPA sites, including multiple language versions and some running on embedded hardware.
A lot of the churn going on is due to people trying to work out the best way to use these new features, along with whether or not to keep backwards-compatibility with existing frameworks and libraries.
Why would you stay at a company where you're being under-paid?
For APIs I either use Express if it's really small, or Django/Django Rest Framework/Postgres if I want something with admin pages.
I think it will cause the app to ask you for permission again when it starts, but it's good to know it's not a one-time-only option.
Things like starting up PhantomJS to run tests takes 2-3 minutes when running in Windows, rather than a few seconds on a Linux VM on the same machine. I get the impression that Windows seems to be a second-class target for a lot of front-end tools, so while they'll probably work, just won't work as well.