HN user

tomkinson

62 karma
Posts1
Comments64
View on HN

For the most advanced (well explained) Javascript and all the way to Typescript and beyond, get a FrontEnd Masters subscription for a few months. Top notch teachers in all manner of content and Kyle Simpson will lay it out well in his many videos (among other great teachers like Will Sentance). The SessionStack.com and Logrocket.com blogs cover some important concepts with modern ECMAscript standards. Surma and Jake at Google are great and have a lot of YouTube resources to bite into. Maybe start with 'What the heck is the event loop anyway?' by Philip Roberts and then Jake Archibald's: 'In The Loop' to get a foundational understanding of what is happening. Javascript.info also a great text resource. You don't know Javascript also should be on your list. Honestly there are so many resources these days including specific YouTube creators but really it's more about your learning style and what works best for you.

I did the test. I was 4-4-2 so basically mixed handed, but really more so I don't care about top hand on a spoon, knife or broom, so really more like 4 left, 1 right, 5 don't care. So as mixed handed as it get cause I throw a mean right handed spiral too. And boy do I relate way more with left handers, all because I prefer highly to write with my left even though if I need to my right will do.

While sometimes a longer timeframe to migrate is better (often, most times), there are edge cases where you want to migrate immediately after an announcement like this. For us, we'd like to get this done by next week. The sooner the better to avoid any schedule disruption thereafter.

Love that you charge by the second. Need to run some math, but we're excited to at least give this a go sometime this week. Congrats on launch.

Guilty of also falling for this insanely rad community. I don't have the time nor constitution to participate, but watching an occasional breakdown of glitch detection, shortcuts, hacks and other such time savers, is a lesson in outside the box thinking. Speedrunners capitalize on pixels and milliseconds and there's something I love about that level of attention (in occasional doses).

This is correct and covers most current attempts at implemention.

The public cannot be confused if you want new technologies to become mainstream. Selling the value of decentralization, something few ordinary people truly care enough to make behavioral or even proactive choices towards adopting, is the wrong strategy currently. That someday will change but it could be a while. The public needs other value propositions like the promise of benefit with little to no effort or mindshare to adopt.

This is similar to why mobile payments faltered (and to some extent still does) in the North American market. Too many players sending out different complex messaging. No unified voice.

Eventually we will eliminate the performance penalties, but mass adoption or demand for a decentralized web will require a complex multi pronged approach that includes education and extensive value adds which are easily understood.

Controversial, but the piece, and truth is, there's definitely some merit to this position. The difficulty is in creating onboarding experiences that also account for the uniqueness of humans. Creating a replicatable process for introducing new hires to a company based on who they are, not on procedural flow steps unified for company benifit. That's the real work to be done.

Android isn't the issue near as much as Google proper. - One answer seearch results scraped from sites to be dominant in keeping ppl on Google - Maps showing places scraped by Google - Google results order

These are the real anti-trust cases.

S̶o̶f̶t̶w̶a̶r̶e̶ Google is eating the world.

I'm actually surprised that they aren't pulling back a bit. Antitrust case is not near in this climate, but it will happen eventually and it's becoming harder with their ever growing tentacles to avoid or reverse. They are going to be their own worst enemy in the end.

Imagine you had a chat, and 30 videos in the chat.

30 play buttons 30 vulume sliders 30 pause buttons Etc

That's a lot in the DOM.

So intead you put the html5 video player components in shadowDOM and reference as needed. Only have them once then.