Greedy ads and too many ads drive users to AdBlock and Ghostery.
@mitchelldunaway6 жыл бұрын
Closed Captions: 10:10 - "time to get interactive" / 10:25 - yes, it's Travis CI / 10:26 - "in the pull request"
@elliemay17486 жыл бұрын
A lot of this is due to business requirements, I.E. the trend to have the frontend completely separate from the backend so that the backend is just API, so that the same API can be deployed cross platform. That led to the rise of things like React, which require twice as much code to do the same thing just because people went "Oh cool look how fast it renders! We must build everything in React now!", and enforces all these insane rules about one way data binding for the sake of the all mighty "convention". Then usually about 30-40 libraries on top of that to get you out of the hole that React creates. The issue is not momentJS lol. But what can you do? Most businesses are way to strapped for cash and time to be worried about optimizing to that level. If you're worried about minimizing your JS code base because it's over 1mb, it's either because there is some sort of technical limitation you're hitting due to it, or you're somehow completely out of other much more critical issues, which has never happened anywhere I've worked in 15 years.
@eni4ever6 жыл бұрын
Look at that T-Shirt. I think he's a FF spy! 🦊
@philipgomez7136 жыл бұрын
I saw that too! funny
@codewithnacho5 жыл бұрын
Hahahaha Saw the same thing
@rowolta6 жыл бұрын
One of the biggest problems is that developers are too keen on importing external libraries. Keep it simple folks.
@alexhinds78486 жыл бұрын
Best practice for external libraries that support it is single file functions, as with lodash, date-fns etc. Allows developers to get tiny additional payload and only the barebones functionality they require of a piece of the library.
@arbaazkhan70916 жыл бұрын
is it only me or this host guy looks and sound like Will Wheaton?
@CerebroVasconcelos4 жыл бұрын
It's really
@herrbasan6 жыл бұрын
In the age of bloated frameworks most of what he's saying is lost on most people. The odd fact is that i have to defend my way of doing it (creating my own tooling for the task at hand) because JS Frameworks are seen as "Best Practice", which is insane to me. I usually get the same results with 1/10 of code that runs twice as fast in half the time.
@cloudstrife70836 жыл бұрын
that's because "most" (not saying all) JS programmer aren't good programmer like senior C/C++ programmer.... they don't have deep knowledge of performance and OO etc The JS community is mostly made of kids who didn't start programming in the "hard language" back in the 90's or early 2000's so they went online and just started to scripts without optimization or data structure... so you see the mess we are in today with bloated stuffs all over the place that your talking about and the re-inventing the wheel everywhere
@kamaboko16 жыл бұрын
And there aren't any bad C/C++ programmers.
@herrbasan6 жыл бұрын
I completely fine with the concept of abstraction layers to simplify development for a certain task or a certain group of people. Javascript itself is such an abstraction layer. But those should always reduce complexity, not add to it. There is people a lot smarter then me making this point. I don't claim to be expert in anything. I just know that i'm a lot more efficient and i'm almost certain it is not because i'm the better programmer. I think there is a paradigm problem with web-development.
@kamaboko16 жыл бұрын
@@tureebluh I think it really depends on where you work and what kinds of projects they have you working on. For instance, if you have to update a website that uses jQuery, what are you going to say to your boss? "I'm not going to use jQuery. Forget that." I don't think so. Now granted, it is certainly not my first choice. But if it drops on your plate you have to deal with it. As for bootstrap, I will use it for rapid prototyping using React. I can spend more time on React and less time on the HTML and CSS, and in my estimation in that situation it is a better use of time.
@Bulbophile6 жыл бұрын
Hope to get there
@TheUnknownFactor6 жыл бұрын
One thing I really dislike about these types of things, and other content google puts out recently, is stuff like "promises are well supported for a few years now"; yeah, if you're talking about evergreen. Almost all actual web-developers still need to support IE11. I mean sure, it'd be better to only include those polyfills on IE11, but this whole pretense that IE11 doesn't exist or doesn't still typically need to be supported is absurd.
@AddyOsmani6 жыл бұрын
There are absolutely sites that will need to continue support IE11 and other non-evergreen browsers. What we try to encourage (and I didn't have time to capture with nuance) is that this can be done with some balance. For example, conditionally serving polyfills for features like Promises to browsers that need them. This has become more straight-forward with babel's preset-env and browserlist. In some of our projects we'll generate a legacy.js bundle for IE11 while serving everyone else a leaner bundle. Best of both worlds?
@slidewineder39536 жыл бұрын
fantastic production
@lsping86 жыл бұрын
There is framework out there that support code splitting out of the box, it's call Next.js (it's a react.js isomorphic framework)
@SudoProgrammer6 жыл бұрын
So much valuable information at one place❤..keep doing👏
@Bulbophile6 жыл бұрын
Exceptions prove rules in languages. A ratio that makes a language a language. There are more exceptions to the rules in JavaScript than what are needed to make it a language.
ad networks and other 3rd party scripts that deal with user data are BY FAR the biggest problem with web performance and destroy the user experience. I wish this topic was discussed more in public mediums such as twitter, etc. Chrome has been THE leader in advancing browser features and security and I hope they consider '3rd party scripts' as an important problem.
@nixtoshi6 жыл бұрын
A lot more bandwidth is lost to images, SVGs and audio files. I think optimization and the recommendations are important, but UX is more important at the end of the day. Because most users will be able to load 1mb in less than 5 seconds, in return they get a nicer UX
@619frank6 жыл бұрын
wait is that the guy who used to have long hair
@LJdaentertainer6 жыл бұрын
Yes
@mcbernnard43036 жыл бұрын
JS is like foxpro?
@h3rteby6 жыл бұрын
"Promises have been well supported for a number of years" According to Google Analytics, 25% of our users are still on Internet Explorer :( Even on Windows 10, Internet Explorer beats Edge...
@samuelgrahame36176 жыл бұрын
Well if someone needs that much js. It's fine if you are making a business application. Where you treat the entire js is the application.
@sudarshangurung6 жыл бұрын
Is that a fox without a fire?
@samuelgrahame36176 жыл бұрын
Why not just let the programmer export the code that is not used. From Google dev console.
@mandaputtra6 жыл бұрын
I wanna test your browser tooo, give me a link
@alkayes2476 жыл бұрын
Google Chrome
@HoracioMiguelGomez6 жыл бұрын
Of all the T-Shirts in the world you woke up, remembered you had a Chrome interview and put on a Firefox 🦊 one?
@addyosmani10566 жыл бұрын
This is a teejungle.net shirt rather than a Firefox one :)
@carloalberto41326 жыл бұрын
Javascript has made the web a playground for hackers.
@themorbidhero29876 жыл бұрын
Why would you say that
@callofdutymuhammad6 жыл бұрын
@@themorbidhero2987 Passive downloads of third party software all the time?
@apidas6 жыл бұрын
there's no too much javascript
@rickviscomi98106 жыл бұрын
False
@ferns20776 жыл бұрын
!true
@lordswaggity12136 жыл бұрын
Go do your homework.
@vic64666 жыл бұрын
Firefox t-shirt
@lawfreed6 жыл бұрын
well played.
@patrickcyiza5956 жыл бұрын
It's hard to believe that the same company saying this is backing up angular.... Just saying.
@erobwen6 жыл бұрын
There can not be too much of Javascript!
@lordswaggity12136 жыл бұрын
Go do your homework.
6 жыл бұрын
Oh that fox.
@StefKrie6 жыл бұрын
It's Firefox!
@harogaston6 жыл бұрын
He knows better!
@dandan78846 жыл бұрын
ELM anyone? In the last benchmark I've seen building a whole app using ELM consumed less bytes than the React framework.
@mandaputtra6 жыл бұрын
I used AppRun it super Blatzzz, but lack of documentation
@mithunkumar-hs6ni6 жыл бұрын
i am a java developer, To me javascript developers looks like scientists
@themorbidhero29876 жыл бұрын
Why?
@mithunkumar-hs6ni6 жыл бұрын
i feel Javascript is difficult to learn.
@aArcziMetin26 жыл бұрын
@@mithunkumar-hs6ni you would learn it in 10 min tbh
@mithunkumar-hs6ni6 жыл бұрын
two months passed, i am still learning.
@mithunkumar-hs6ni6 жыл бұрын
i agree
@sergioavila27206 жыл бұрын
Javascript with Django.
@kevindt1006 жыл бұрын
1 MB ummm my site has like 7 When i send yay i think
WASM does not have access to the dom. So WASM is only good for heavy algorithms
@adilismail35936 жыл бұрын
Hey google ur chrommy is very resource hungry on Linux
@A1rPun6 жыл бұрын
Go FF or chrommyum
@IdrisMC6 жыл бұрын
This is why i stopped using bootstrap and jQuery. I just use backend libs and framework s
6 жыл бұрын
Webpack is the root of evil #dontpack
@aArcziMetin26 жыл бұрын
Wrong
@KevinBeal6 жыл бұрын
Not enough black women
@rickviscomi98106 жыл бұрын
I care a lot about representation on this show. Feel free to suggest the names of guests you'd like to see and I'll reach out to them!
@habibsspirit6 жыл бұрын
+Rick Viscomi He was very likely mocking the diversity agenda big companies have nowadays.
@md.fazlulkarim88476 жыл бұрын
I don't like the idea of showing a skeleton version(without JS) of websites in 2g networks. Always remember, you are just a browser, a utility, like a pair of glass. We see the web through the glasses. You have no right to alter the actual view without the consent of site owners... Anyway I enjoyed the talk. 🧡