Time to clip this and tag netflix on twitter and ask them if this is why they turned you down in the interview, for not sharing the same kind of opinions as the rest of the staff
Bro, this made me realise how the dev circle is such a parallel to wizard towers in fantasy and hoe they bicker and fight about magical philosophy all day
When I had a job I spent like 40% of the time on bicker fights about magical philosophy and 10% on meetings, and 20% drinking coffee. Only about 12% was spent actually writing code, the rest was reading the lambda ultimate. Now I retired, I don't spend time on bicker magical philosophy because when you're a lone wolf you can do whatever.
We conjure spirits from thought that move through the circuits. We bind them with names, and through those names we command and change them. The wizard book really makes programming sound metal.
If you know German it is ever funnier because when he says all those variables with the $$ it coincides with Hitler saying "SS" (The Schutzstaffel), which is just great timing. Really needs to get some probs!!!
When a JavaScript dev tells you Go is bad that's when you know they're cooked. They can't deal with the fact that Go devs are happy because they're not JavaScript devs.
Dang I didn't know Prime knew about Action Script. A legit great language that is easy to learn in my opinion. Cons are that async is a bit weird (Worker) and it's missing out on some modern syntaxic sugar like arrow function and Linq.
For web applications, PHP is fundamentally flawed, especially if you have to do IO during requests. Basically, this comes from two issues: every PHP request is basically a new process, and every request requires doing some setup, such as connecting to a database, loading language files, etc, etc, which will block. Likewise, doing database requests, API calls, etc, will block. All this work for every request. Sure, there's Laravel Octane for long-lived workers, so you don't need to do constant setup, but that's almost worse, because having a set amount of workers versus just forking a bunch of PHP engines will make it so any blocking will make further requests impossible. PHP was also never designed for long-lived processes, so it leaks memory like a seive, especially if you use libraries that never expected to run in a long-lived context. For anything that's a little more than a static page or a few database calls, PHP loses out to JavaScript, not to mention Go or Rust. I mean, sure, there's stream_select and some libraries that can make async work, like ReactPHP, but PHP still has some fundamental issues.
you dont know what you are talking about. php-fpm are long lived workers. and if you have as many workers as cores you dont even want to do async because it will slow down the CPU with context switching. I have a feeling you just dont understand web hosting/ webdev. Javascript/rust/go script kiddies need to learn more.
@@turtlefrog369 You have no clue what you are talking about. If you are waiting for a IO, and you haven't made the underlying connection async, then waiting on the connection will block the thread and waste precious cycles doing nothing. If you have a finite number of workers, this places a hard limit on the concurrent number of requests that can be handled. If your database is locked or an API request is taking longer than expected... then you are fucked until that request finishes. It kills performance. Using the PHP SAPI and spawning a bunch of PHP threads is also a way to work around this, but then you are basically doing async but passing the work off to the kernel, while kernel threads are generally much heavier than green threads or tasks. In essence, PHP is okay as a templating engine, but it doesn't scale. Blocking itself requires context switching anyways, as you pass control back to the kernel to start scheduling time for other processes, which is much more expensive than simply opening sockets in async mode and handling a bunch of requests concurrently using an async runtime. These are basic computer science concepts that I learned as a freshman while getting my degree.
@@turtlefrog369 That's kinda my point. PHP is great for simple or static content. One or two calls to a database won't hurt too much. But once you start doing more complex stuff... like web sockets, keep-alive, SSE, etc, then async is the only realistic way to do so. Even PHP-FPM kills their workers after like 20 requests because PHP leaks so much memory that the only way to make long-lived workers realistic is to kill it quickly. For startups, blogs, or marketing, PHP is great. For more complex use-cases, it is not. Plain and simple. Since that's the case, it's much better to find a more performant language or server that actually has async support, such as Go, Rust, or Node. Again, PHP has a place and is good for quick iterations, but larger projects aren't meant for it. These are all extremely reasonable takes. I primarily used PHP for a long time and I kept running into issues related to these. There were some workarounds, sure. But fundamentally, PHP was never meant for the modern web, so it was a bitch to get everything working. I'm smart enough to work around these issues and find solutions, but after switching to another language, everything became much easier because I wasn't using PHP how it was meant to be used. Also, I have a minor complaint about PHP-FPM... They aren't compliant with the FastCGI spec. I implemented a FastCGI server to communicate with PHP-FPM and their non-compliance with some of the protocols was annoying, particularly they don't hint via FastCGI how many workers they have.
@@reybontje2375 did you just call facebook a startup? The "modern web" can F itself, js needs to go. I am sick of all the fingerprinting API. And no you do not use PHP for static content, what are you smoking?
Re: proxies Yeah it's great fun in the land of Spring when you forget to put breakpoints in both your controller and your service classes, and then you think, how long could it possibly take to step out of the service back to the controller? There's like 7 different levels of indirection to call an autowired Spring bean method, and they're all called invokeSomething. You have to use a debugger that knows about your framework, and there's something cursed about that.
Happens to every Dependency Injection framework. At least the ones i know. But then again, i could be helpful if there is some filter, circuitbraker or wathever in between that is causing an error. And the stacktrace is more helpful than from the Rx library.
Adobe Flash age was great. It was a mess, but it sparked so much creativity. And I'm ok with that, because nobody tried to run high volume corporate information system inside a Flash instance. Which was wise. Unlike someone else...
ThePrimeagen: "You wanna give your career the pink slips? Learn JavaScript. Even PHP is better than JavaScript ..." php: "A-ain't no mercy, a-a-ain't no mercy (Woah) Got that purple Lamborghini, purple Lamborghini lurkin'"
The inoculation to JS 2018 was remembering JS 1998. 😂 But being real... Disposable code is the best code. Except for the code you never even have to write.
Decorators and proxies may not be the worst when it comes to indirection. What about Aspect Oriented Programming and COMEFROM, the implicit GOTO instruction?
Learn as many languages as you can stand to learn my friends. It dilutes the hatred. 😂 But please could someone tell me why I learnt coffeescript... "Oh... look at what new JS can do now". Like writing an XSLT engine months before msxml was released. This was in my stars. 😔🤣
Not asking this in a hostile way, just genuinely curious. How exactly did you, Theo, and Fireship become the holy trinity of RU-vid web developers? It feels like that's been a very engineered process, and I'm wondering how much of it was the three of you working together and how much was just the result of naturally aggregating fanbases or less naturally occurring sponsorship patterns.
Say whatever you want about languages, Java was, is and will always be the greatest language of all time. And those who know how to code in Java and understands it's value & power well would agree. Haters are always gonna hate. We just gonna ignore them like Linux DE devs ignore those systemd haters...
This video is really weird if you're german and you understand most of the real bad german they are speaking there, but the subtitles are saying something completely different.
As someone who actually used as3 at the time, don't listen to the guy who read a blog post about what Adobe thought would be a good idea once. It was a terrible language, poorly implemented.
