Comments by "Kristopher Driver" (@paxdriver) on "Theo - t3․gg" channel.

Well then just don't answer. Leave that for someone more novice who wants to help out and build cred in the community. Why can't you let someone else earn a badge instead of making it your own cross if it bothers you that much? This is exactly what I don't understand about the culture on stack. People are so proud of the credit and votes and don't ever really mention human beings. Is it just a transaction for status amongst peers to you? I've never heard groups of teachers act so snooty about students or other teachers trying to become better teachers by asking stupid questions. This is human evolution, getting help from people isn't always lazy it's what most normal people have always done through history to engage, connect, and manage frustrating emotions in challenges. This is the problem with stack, imho - ego and disdain don't build communities. This is exactly what it means to be elitist, with all due respect. Most people don't like it.
29
Synthetic training data will eventually lead to mad cow disease for the model.
20
First off, discord didn't have anything to do with stacks demise imho, stack is just toxic to newbies who are earnestly trying and finally ask a question after 6 hrs of prowling and reading docs and looking around. To be told "did you read the docs or google it" is emotionally ravaging in that state of mind where a person was daunted before even mustering the courage to try something difficult on their day off. The only other thing I'd mention is if the internet becomes an AI incest bukake it will only make way for i2p or web 3 variants rated by users which, over time, will exactly mimic old Google... And rinse repeat from there. This is why we can't have nice things: capitalism is good but not unbridled at all costs. Moderation is key, humans are incapable of that over time. Radicalism always breeds and kills faster than moderation by definition.
18
If we need to add a denounce, then add debounce... Why is this terrifying? This feels like another chicken little situation to me.
12
@6:23 Theo finds his own error message interesting 😂 Love these javascript vids. Catharsis all wrapped in a senseless block. You should do one on defining objects with variables for keys. That syntax is so confusing where the key can be dropped or wrapped in brackets, or spread, but only shallowly spread... And there's no built-in optimised deep copy! I have to trust a util or write a case for every symbol, collection, set, array, etc, etc if I plan to reuse it lol
8
I would argue it would be easier for the entire world to simply call the language "jayess" and be done with it all. The "lawn mower opensaurus" quite at 22:33 always cracks me up, btw lol
5
Yes!!! Three, drei and react content would make me cream, especially for nav, transition and streams.
3
Please do a video on stacked diffs. This is new to me (2 yr casual git novice, speaking)
2
14:53 why doesn't the cdn just provide the server with the skeleton too si the server doesn't generate a useless static shell? (maybe I need to keep watching for the answer lol)
2
Ya, I'm glad I don't have to make the esthetic argument, so thank you lol. This is nothing I'd want to teach my team to read and use. It's not even saving lines, there's no point at all to this except for being a fun way to abuse javascript if you're an enthusiast (which I totally get and support). I'll never use this even if paid to.
2
15:50 also, $151k in New York city is very different from $151k in Montana... That's such a dumb number. That's a grounds keeper at an apartment complex in Queens if run by your brother who trusts you to speak on his behalf. It's still dumb. 20:02 very very good call on the Republican FTC members 😂nailed that one blind
2
7:58 to correct you, they didn't promise successful businesses, they claimed "business formation". More businesses forming is still good, that's education for the failed business, which leads to better workers when they go back to working for someone else, or a more successful second try at something else down the road. It's very good to encourage young people to invest in themselves and try starting their own businesses.
2
I don't trust a company who does this, never mind benchmarks. Character and integrity matter.
2
36:34 prediction - phantom infinite renders one day. Terrible idea. Explicit is better. I'd much prefer a reliable error than an unreliable rare error after deployment.
1
I'll never understand why useless fragments are annoying but all the semicolons are fine lol
1
Who's going to use their headset on the can? Nobody uses twitter if they're not streaming or steaming poops. I'm gonna call it now - twitter will never survive on the quest. I'd bet twitter would lose more people than gains with respect to quest owners, because they'll be social anywhere else instead lol. 😂
1
$awesomeness
1
Arm is RISC-V, and amd/Intel were fully invested and betting the farm on an architecture that was proven, it would've been insane for either to bet the farm on a guess after billions invested. Chip design is a long-term game. It takes years to design a new chip even on an ISA everyone on staff is expert in. I don't think anyone would say that betting on arm made sense when 5 generations of x86 CPUs were already in development and successful AF.
1
This is a perfect example of why it's important to understand how to read charts. If 100 companies all need 20 employees but there are tons of them out there, they can each publish one ad and select applicants for the different positions they need. If 100 companies all need 5 employees but there are only 250 devs looking for work at any given time capable of the positions, each of those 5 jobs at all 100 companies will get their own listings. Number of listings is a stochastic representation of the job market and says nothing about the employability of devs that average pay, average hours, or average turnover doesn't. I would expect devs of all people to recognize this chart represents nothing. Small business is the heart and soul of the nation, imagine 90% of all devs started successful businesses so while this chart looked like this, small business success rates quadrupled and nationwide incomes surged as a result... Would that be terrible just because indeed's listings took a nose dive? This data reflects nothing that can be extrapolated imho, just click bait and trying to drive salaries down. Be on the lookout for scary foreboding "science" to get published about the job prospects of programmers. Know what, though? Programming is hard and even gpt needs a junior to hold its hand when using it to write code. It pays well because only practise makes you better at it - hence the expertise and the salaries. Until they start selling anything that doesn't come with code needed to run/maintain it there will always be demand for devs, and so long as dashboard for UI are helpful for customers who aren't geeks, there will always be a version of web development. That demand isn't going anywhere, it'll inflate when it's cheap and contract when monetary policy dictates, that has nothing to do with the career prospects and everything to do with poor fiscal policy and government. They engineer cycles of boom and bust because that's how bankers arbitrage, by controlling the flow and capitalizing on both ends. It's greedy and dishonest leadership of economic policy, and absolutely nothing to do with anything practical about the field.
1
Sets are amazing for lookup tables
1
J++ is coming, Mark my words.
1
How can you say "gif" incorrectly and also pronounce "gist" incorrectly?! Lmfao Jk great content thank you
1
Why not just run return in a finally() after the promise returns? Finally(return jsx) should work fine, no?
1
RISC-V has open instruction slots anyone can assign to new tasks. That's what arm is, RISC-V with a proprietary set of a bunch of specific instructions tacked on to the end, I think. Meta is also designing FPGA and ASICS on RISC-V, along with Google, Apple, MSFT and Nvidia.
1
Isn't any server component the same as a js file called by the server and the output served by an api? How is that any different from Express? I don't understand all these changes because very few of them seem to serve a need. If shorter code results in less legible code, the more code is better if it's descriptive. I hate shortening code just for the sake of character counts when it makes it take twice as long to figure out the 4 different ways to write the same thing without performance benefits. Nobody is impressed by fewer lines lol I don't like changes when nobody benefits from them, but many people suffer. Ref should be a built-in prop, not a second arg. If you're gonna need the ref it might as well be a reserved key in props, like why not?
1
18:13 when sentiment is broadly negative that's a sociology thing, the chart needs to be phase shifted. People are more depressed, it's got nothing to do with the tools.
1
Whoa!! Congrats xyzeva on another shout out by Theo.
1
Why can't you build extensible rust? There's no reason in my mind that rust can't be developed with a system of future features easy to plug in. If a garbage collector can do it, then a system of add ons that easily plug into your existing project should be just as possible and reasonable in rust, doesn't it?
1
CSS is as incomprehensible as it is today because of trying to grow features for the sake of growth. Many css additions are vital like transitions and variables, but how many people have actually memorized the right object-fit keywords, or the difference between static and relative position until they try both to make sure? It's so great to have css, but it's so unbelievably impossible to write it by hand without ide tools now and javascript is getting to be similarly convoluted when we have to memorize which js is universal, browser-specific, or if it conflicts with a particular bundle, maybe server, framework, or bugs/vulnerabilities with polyfills? I may just be old, but I seriously believe js needs to slow down and plug gaps. Build new features on the new language for people who need to tie new features into a browser script. JavaScript is really really good and tying into other systems, just put those specific niche new features in a new language that's built with them in mind (like Pyscript), it's way easier for everyone to learn a Python implementation of a new feature than it is to change the whole language to shoehorn it in. Serverside javascript is wonderful for those of us who learned js 25 years ago, but it's a mess for someone starting from scratch I would imagine. Would've been so much easier if express was in Python and javascript just linked to an interconnect api because Python is just easier to apply new modules to, and those modules can be standardized in chunks and in lower level languages for performance. Programmers today are constantly building layers of abstraction to organize code bases but the language for some reason just sprawls incessantly like they think it'll die if it just stops changing for a bit so that standards can for organically. I really don't understand what is so lacking of a web browser scripting language that the thing needs to keep growing. I'm not saying they've done a bad job at all, I'm just saying there's a point in which it doesn't make sense to do more when we're already leveraging markup, parsing virtual DOMs and diff-ing in between event loops and css computations - drawing and reporting precise paints and performing all these api connections between technologies. It's a great intermediary language, I don't see how expanding it while it's still bleeding from past scabs helps anything when there exist alternative approaches that javascript could readily plug into instead of building it itself. Maybe I'm old and too novice to understand neo-modernity lol as coders we reduce and simplify, but with languages we spread eagle before mopping up from the last round of features added in. It may make 2 devs lives easier when they copy-paste templated code anyway, but for every generation that comes next who has to learn specifics like "bind(this) but not with arrow functions" it's actually worse for everyone who isn't already fully committed to the language. It doesn't help the language making it harder to learn the trade for benefits few will realize and none can measure imho
1
I just built my first fastapi endpoint for a react project I'm working on. I took 2 days longer than the 1 day I estimated because I felt compelled to make the json file it served an asyncio call, the fetch was through an async web worker in react, and the fson it serves updates only once per day so it is reprocessed server side to be ready and waiting as soon as it's updated. Did I go overboard or are we suggesting my anal retentive approach ought to be standard? Again, my first time, learning solo, sincerely curious. It sounds like you're suggesting I did as much as we ought to expect of backend to provide to front end.
1
Why is a 2-column waterfall difficult to code? Doesn't react perform memorization automatically now? That should be built in without thinking now, innit?
1
Dude thanks for the vid. You look like you just gave birth at the office lol I feel bad you work so hard. Legit question though, how is an event or signal with usememo, or a consolidation function, considered "a bunch of other code" to accomplish the same thing as use transition? It never really seemed like a lot to me. Even arrow functions seemed pointless shorthand unless binding "this" is part of the function (in which case arrow functions are a godsend and why would you use anything else?)
1
11:51 I've been writing html consistently since 1999 when I was 14, it is still easier to read closing tags with a space. If it's unclear, like not-BR tags that can be nested, never use it. If I see <> without a slash I have to stop and check if the word is one common to new HTML I'm not familiar with (like section, article, picture, or for old people like me the I, b, or center tags) then I don't have to try to remember if the em is a legit tag, an XML thing, and whether what I think it is has nested elements... Just use a "/" in every tag or closing tag, make it clear when that part of the markup is done so I don't need to focus on that when debugging someone else's HTML. Why not use /? We should just add 1 character to make any code much more reasonable. That's why we dropped the semicolons in javascript, that 1 character is distracting because we have to stop and ask if that's where the bug is.
1
Imho there's an easier way to think about this so it's jot a headache: when globalThis has a property initialized that means any other functions defined next to it may use that scoped function, so it to needs wait to for the globalThis to garbage collect to be sure that the function gets collected and the array buffer with it. I will try this theory out on my own so this is sort of a bookmark for myself, but I would bet functions wait to garbage collect until after everything in that scope is collected first since functions are hoisted when defined they're probable last to get destroyed. That would mean defining functions in global scope or well defined scopes (unlike the example which initialized part of globalThis from a nested scope, effectively holding back garbage collection of the entire globalThis object). The practical way to avoid this is good practise already - don't initialize a global key from a nested function. A class instantiation of all possible keys would prevent this, I bet compiler frameworks prevent it, and even wasm or other transpilations would too, because they're not jit interpreters. It's probably the interpreter part that needs to hoist scopes like this because otherwise you'd just be setting an arbitrary depth for cutoff and that would be way worse performance than recursively hoisting an object being structurally modified in a deeper scope. Either by defining all functions in their useable widest scope like functional programming doctrine dictates, or by defining all objects with all possible placeholder keys like modular OOP doctrine suggests, I bet these paradigms eliminate this memory leak by design, or at worst limit it to an interpreted, unoptimized runtime anyway where that kind of leakage should be expected. Love these videos btw, thanks a mil. Can't wait to try this out with iffe and async and every variety I can imagine lol. I bet the browser throwing timeout into its own thread loop has something to do with it too, or specifically array buffers working at lower level than standard objects due to their memory allocation benefits maybe plays a role? There are so many different reason I can imagine this made sense to ECMA lol
1
YouTube just scored less than 30 across the board using chrome on a galaxy note 9. Case in point lol
1
Dude... Why are you losing sleep? You acted in good faith speaking your mind and you have professional insurance. Just go to bed, this isn't useful content worth rushing out. Everyone could've waited for this.
1
I'm a new-ish MERN developwr. I'm convinced, thank you. There are definitely trolls on the internet
1
Why are we even trying to perfect javascript with expanding the language when we still haven't developed consistency for the language as it already is? It won't stop innovation because frameworks do fine on top of js; modules for a prime example. It will never be as solid as rust, that's never been it's strength anyway. Its versatility is always going to make it vulnerable, but as the language gets more specific and complex and becomes less script-y. Pyscript could easily fill this language gap, while we leave js to close existing vulnerabilities just apply any language specifics from what we learned from js and make Pyscript that new programming language for browsers, with packages and imports and all that good stuff. JavaScript can't be made into Rust by brute force, and the language is already so powerful nobody is losing sleep about what they can't do in javascript... That's just not a thing. If you need more from js, build it for Pyscript or wasm instead. I don't understand this obsession with constant language growth, hardly anybody uses most of javascript's built-ins already. Proposals should be fixing what's already here, we don't have to constantly introduce new features when scripts are best as connections to API's as opposed to being the api itself.
1
This is literally what I love most about javascript lol ❤
1
Theo, you're amazing
1
#theoForgotLoL
1
Actionstate pisses me off. Nobody cares what I think, but that's what it is. 3 assumed destructured variables from a single function pisses me off. It's should be one object, like all hooks. Even if they had to use maps or a set to avoid an object, the assumption we'll memorize conventions that aren't enforced but are required is such poor foresight imho. They don't do that with anything else but react. They should've enforced an object formation so it can't just be convention that de teams rely on with unfamiliar code base. With context we know for a fact they could've incorporated manual render mode on components too, which would've been nice. Instead of context being able to send a bool for components to render them manually through props would've been cool. Then they default to off again once rendered from a true prop. That'd be so efficient for checkbox components and stuff. use is just a shortcut, it's not new I don't think. Just sugar coating instead of a new feature.
1
Looks like I gotta do housekeeping on all my snippets and templates again lol nice
1
I love react because of how similar it is to Flash 5. Flash was my first love in highschool, going from jQuery to react was a dream come true lol
1
It's like web developers who don't know any css or graphics editors. I started as a flash developer, it bled into javascript, jQuery, react, blender, gimp, Photoshop, inkscape, and all kinds of odds and ends over the years and it was never my main job ever in my life. If you're exposed to the industry and you're not an entitled liability waiting to happen you will have accidentes upon tools like audacity, git and vscode just by osmosis if you ever tried to challenge yourself more than copying a tutorial word for word.
1
Maybe I'm completely wrong, but couldn't you wrap script tags to any other parent tag to avoid this? All scripts could just be appended to <div id="scripts"></div> without breaking anything if component mounts amd renders that div. I call a compensent like that I use on my app called "DataContainer" for a batch of tags prone to hydration errors. Scripts that depend on other become a mother script, which import all component parts and it is the thing appended to the DOM
1