How old were you here? I remember this was one the incentives for me to start digging into the 3rd party code I was using back in my web dev beginnings!
This video just saved me for the second time! 2 notes to add: Don't forget to hit ctrl + s after modifying the code If the code looks unreadable, cleck the { } icon you see below the line numbers of the editor. It will format the code.
Thanks you didn't say "subscribe".. bro. you deserve it. you won it.. you really didn't need to "Request" for a "subscription" ... Amazing information ..
Maybe I'm not paying enough attention, but this just seems like a runtime with locked-down access to the underlying OS. That is not to say this isn't important or interesting just that maybe we are approaching it from the wrong direction. Maybe intend of pushing the browser down the stack we should define a process that has these properties. Wasi comes to mind but I feel like we could do it at the OS level.
OMG! Thank you! I have this website with live data and there's a lot of junk that I wish they would filter out. with your help, I was able to edit some parameters and bam! better website experience! thank you Paul
When you showed the tags without end tags... i really felt pleaseee take it off I cant handle it :D... but I really appreciate your way of explaining complex items so smoothly... thanks for sharing this video... lottt of info which i was looking for about HTML 5.
01:45 how we can build a new web browser 02:24 the devil, security holes, race conditions, cores 03:50 How do we give more control to web developers 04:19 rendering process 06:08 origin
Now I understand why even though people hate Java, it still is popular and still relevant. I dont need to go through all this setup just to debug. In Eclipse, Intellij or STS, debugging a java program works out of the box. Why is it so hard to do the same in nodejs?
blasttrash Node doesn't have an actual ide with proper debugging like VS2019 or eclipse is for c# and Java. It's a dynamic language made for scripting simple website interactions, not making real programs. People are basically misusing JS but it's so popular that the crazy optimized runtimes and tools and libraries have made it usable. The reason nodejs is popular is because webdevs learn JS then don't want to learn a real language for native programs.
@@YoloMonstaaa I know that. And being a statically typed language means that Java and C# have advantage when it comes to IDE or intellisense etc at the cost of some verbosity.
blasttrash I disagree. I don't think string int or char is more verbose than let and bar. What makes c# code verbose is oop and scope rules, nothing to do with static types.
@@YoloMonstaaa no I dont think so AbstractFactorySpringBeanInitializer abstractFactory = new AbstractFactorySpringBeanInitializer(); with dynamic typed language, you can at least skip the first part. Now scale this to entire code base. Without IDEs or code scaffolding, it'd be a pain to type all this. Thats why for quick prototyping or simple scripting, people use js or python or even groovy. In fact some codebases in java use groovy(spock etc) to write tests since tests are not that business critical hence can be written faster. Note groovy is whats called as optionally typed according to some people. Of course there is a huge gray area in that definition.
@@blasttrash Well no, since C# 3.0 (from ~2007) you can have implicitly assigned static typed variables in that situation, so your example would look like var abstractFactory = AbstractFactorySpringBeanInitializer(); And C# will automatically assign it the right type. It's still statically typed so you have all the advantages from that. I'm sure Java has an alternative, I just happen to use C#. It's actually best practice to use var in C# and styling tools (resharper) actually enforce it. So I think my point stands :) Edit- quick Google shows Java also has var keyword added in Java 10 in 2018. Man y'all have been slow to copy C# (11 years! Lol). So we can say that's been a limitation of Java and not because of statically typed programming.
Still watching in 2019 tho I watched through this a while ago and gained solid information and ALSO wisdom ABOUT wisdom. Your curiosity into the jquery source gave some insight onto how to investigate or learn from other sources. Thanks for uploading this - I watched it years ago, but I still remember. cheers man
Some objections. First of all, nobody ever made a system more secure by increasing the diversity of components that have to interact. Before too long, the law of the least common denominator kicks in, and you get most of the systems in the ecosystem not having most of the security holes patched. The question is not whether the average Joe programmer can patch security holes, it's whether he's willing to. Putting the power into his hands to write custom low-level code is also shoving into his hands way more responsibility. Secondly, nobody ever made a system more secure by adding concurrency. That concurrency means race conditions, and poorly understood semantics. In some sense, Javascript code's concurrency is easier to reason about today, because while it is true that calls to the DOM can race with code on the browser, you also get a kind of implicit critical section property, where each contiguous block of code that doesn't touch the DOM acts as a critical section. Perhaps rather than talking about JS as a weak, single threaded language, we should be talking about JS as a slick syntax to a simple concurrency model.
