The thing "JavaScript programmers" coming from the server mostly miss is that client side work is an order of magnitude harder.
-
-
Replying to @slightlylate
So if you're coming from the server and you've assembled a tool chain that makes you think "this isn't so bad", you missed something.
1 reply 6 retweets 16 likes -
Replying to @slightlylate
...probably something fundamental. Client side work sucks because the space to work in is so cramped. Networks, CPUs, and disks all hate you
1 reply 7 retweets 25 likes -
Replying to @slightlylate
On the server, you get what you pay for (CPU, disk, network, etc.). On the client, you pay for what you send in ways you can't easily see.
2 replies 11 retweets 29 likes -
Replying to @slightlylate
Now, the platform (browsers) have been working for 20 years to make this more livable; incremental rendering, steaming & threaded parsers...
1 reply 3 retweets 11 likes -
Replying to @slightlylate
What you should understand most when you use a framework that's "all JS all the time" is that you're throwing all of this away.
1 reply 6 retweets 23 likes -
Replying to @slightlylate
Flight taking off, so parting thought: if you call yourself a "JavaScript programmer" and not "web developer", you are likely to fail
3 replies 17 retweets 47 likes -
Replying to @slightlylate
@hexxthalion Do you have the percentage likelihood of failure?2 replies 0 retweets 0 likes
: this is the maddening part: the failure may be creeping. "Oh, it's fast here, what browser/machine/phone?"
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.