Comments by "Ozzy Perez" (@OzzyTheGiant) on "ThePrimeTime" channel.

  1. PHP literally stole all the good junk from every language right now and just jammed it into PHP 8. Absolutely fantastic to work with compared to Python or JS/TS. Unfortunately, I'm looking to use a default language that has more than just back end as its use case, so I'll probably be using Go, Kotlin or C# for that, as they all compile AOT and are easier to deploy rather than having a fat Docker container. PHP though, is definitely the most optimized language for straight up back-end web dev.
    87
  2. ThePrimeVuesSvelteVideosAndHasAngularOpinionsOnThem
    49
  3. C# has only gotten so much better, Web APIs dead simple, but love that they still support OOP/MVC architecture. Blazor is just a bonus!
    44
  4. Instructions Unclear, AI rewrote React as Svelte
    25
  5.  @RealTwiner  Even then, I don't think that will ever happen. There's no way that AI can reach that potential where it can understand context and architecture at such a high level as a human. We're talking about replicating the power of the human brain. We simply do not have the power to create that.
    16
  6.  @IvanKleshnin  Agreed, such sheep culture. Can't think for themselves
    15
  7. The only things hard about Go were understanding the import system and working with pointers, which was obvious at the time I was learning Go but those things are not hard to get past by if you understand value vs reference variables in other languages (it's just more explicit here) and how to organize code. After that, it's just no-brainer stuff. Go is just clean and refreshing to work with.
    13
  8. These JS devs are clueless. Promises are closer to co-routines than they are to actual multi-threading, and even then, they're just deferred function calls stacked in a queue.
    12
  9. How it get's things done is a whole different story
    12
  10.  @ParkourGrip  really any of the modern languages (Kotlin, C#, Dart, Swift, Go) would be significantly better, yet no one wants to give up their (not-so) precious JS and Python
    11
  11. If AI ever becomes as "good" as people hype it up to be, it's more than likely gonna replace THOSE people, not the low end devs
    8
  12. This, I have never felt so understood in my life. React hooks are the worst thing in the history of programming, all because React devs can't bother to learn OOP principles and just general code organization; instead you got functions acting like fake classes and forcing the one-way data flow on everything.
    7
  13. The benefits of PSR standards are clearly evident too. Recently upgraded Slim 3 to 4 and VS Code is now able to pick up the framework's types much better due to those standards.
    7
  14. The only people that do OOPS are those who can't organize their code.
    7
  15. Nah bruh, any time I see something simpler to use (Svelte, Astro, HTMX, Golang), I drop whatever tool I'm currently using and migrate to that. Whatever reduces maintenance time for me is the gold standard.
    7
  16. @ThePrimeTime I fully support your "Generalist Andy" philosophy. Any time I see an environment where someone becomes a "sheep" to a tool (or any object for that matter), that's the environment I try to get away from. We as devs should be constantly moving forward to newer tools and making new opportunities for ourselves to work with better tools rather than to settle down in one spot just for the sake of money. Also, React is not an "industry standard". It's a mess!!
    6
  17. DART, DART, DART, DART! No seriously, please try to give more attention to Dart/Flutter. I think it's quite possibly the best thing there is out there for cross-platform dev. Yes, I'm very biased
    6
  18. That's literally the same thing JS kiddies are doing right now. We show them Angular, Vue, Svelte, and they don't budge! That's not the point of this video. The point is to expose how react is terrible for large scale projects.
    6
  19. Not to mention that they only want senior devs. Ok that's fine, but the reality is that most of them are snatched up already, so they need to be ok with hiring juniors that they can train.
    5
  20. I started doing this when I joined a React project with plain JS. The tech lead can't organize code for squat and it is a pain having to debug all his spaghetti code, so I started implementing types using JSDoc and definition files. Works like a charm!
    5
  21. The fact that PHP has proper type hinting and JS needs a whole superset language (TypeScript) to solve its issues.
    5
  22.  @Jabberwockybird  High disagree. If people in self-employment can bill clients fees just to show up, then this should be the same for employees. My "business" is showing up, however long that takes within reason, to provide my skill set. Employees are businesses too!
    5
  23. Yes they do, they can STOP WORKING. There's even more leverage the fewer developers there are.
    5
  24. I can say the same thing about FP fanboys. They're all close minded. I use both, but when it comes to UI, which uses event systems a lot of the times, OOP solves the problem far better than a giant bird-shaped component tree of providers.
    5
  25. Yeah, I think mod reporting should become a weightier feature
    4
  26. So, can someone tell me what this means for someone new to Rust? Is it worth learning still given the chaos going on?
    4
  27. It's slower than most languagues, but I would argue that it's the fastest of the interpreted ones (PHP, Python, JS, Ruby), at least for raw performance. For async stuff, JS still holds the edge. Multithreading though, not sure.
    4
  28. Dude, you get me! This is exactly what I advocate for: Svelte (with TypeScript), Go (Echo framework + GORM) + Postgres (or SQLite for smaller apps and sites). This makes deployment so much easier! No Docker shenanigans.
    4
  29. It does have a use case. If you have a lot of basic CRUD endpoints, Django takes the cake in getting them done fast.
    4
  30. YEEEEE INTENSIFIES!!!!
    4
  31. nah, I say SQUEEL now 👍
    4
  32.  @musashi542  too young?
    4
  33. I think the problem is beyond Java. Java by itself is.... ok. It's not bad, but most of us got annoyed with all the XML programming, ridiculously hard to read docs, and the ecosystem that supports Java. C# is kinda the same but it seems that they have simplified a lot of tooling and other stuff over the years which makes it more enjoyable.
    3
  34.  @DEVDerr  personally I like Axios just because it's configured for JSON out of the box, but really, fetch is pretty straightforward to use that it doesn't matter to me which one a project uses.
    3
  35.  @ITSecNEO  although it's still dynamic, PHP has introduced a lot of typing mechanisms in recent versions and has encouraged libraries to use typing standards.
    3
  36.  @Rohinthas  That's always been true, the problem is bad management, bad organization, bad scheduling, etc. If managers are not going to get it together, work from home is necessary to avoid waste of time. also gas is high right now
    3
  37.  @joegaffney8006  agreed, need a head chef and support cooks who nod and say "YES, CHEF"!
    3
  38. XML is the reason I don't use Java. It's littered everywhere and so many configurations are written this way. It's like writing a front-end entirely in JSON
    3
  39.  @gljames24  Furthermore, if circumstances play out the way some fear, C could go the way of COBOL: very few C devs who have to maintain a lot of legacy code across various fields, and then companies might actually have to force themselves to switch over to Rust because no new devs bothered with it.
    3
  40. At this point, Next.js is becoming the next Java/Spring. I'm so done with all this React nonsense.
    3
  41.  @joschomo1010  Disagree, Flask is barebones, you have to piece together everything yourself
    3
  42. Thank you so much for broadcasting this! Never in my life have I felt so understood when it comes to front end dev. Everyone is preaching the React gospel when it fact this library/framework does nothing but cause so many problems for projects, from state management issues, to rendering shenanigans, to stuffing everything in JS rather than separating concerns (I don't want my CSS in JS!!), to some of the messiest components on earth all because instead of adopting OOP, people just want shortcuts, making functional components with hooks and effects that mimic class methods but now we have to worry about one way data flow. This framework doesn't make sense and needs to die! You get a like, a subscription, and advocacy!
    3
  43. My approach is to use a fast and simple language by default. For me that's Go. Then use query builders (not raw SQL, not ORMs) because that's the best middle ground for avoiding typos in SQL strings and the overhead of ORMs.
    2
  44.  @PanosPitsi  You wake up and choose to be sheep
    2
  45.  @TheCactuar124  sounds like people skills is something you need to fix. Never expect introverts to bend to the will of extroverts; extroverts are ruining this world
    2
  46. It borrowed a lot from every language, if anything: - inline classes: Java - named arguments: Swift - property declarations in constructor: TS/C# - array destructuring: JS - traits: Python - lambda functions: JS/TS/Python - union types: TS/C#/Python (type hinting) - match statement: Kotlin (when statement) Everything looks so good though 👍
    2
  47. JS Kiddies here are incredibly ignorant. Bet most of them use React too, well guess what? What React has been doing lately, is what PHP achieved like 20 years ago!
    2
  48. Ain't nobody got time for that! 😂
    2
  49.  @daedalus5070  Agreed, I knew the only way we were gonna get improved type safety and better performance is to just restart from the ground up, and Svelte is that answer. But no, React devs just being sheep, it's like arguing with Apple fanboys.
    2
  50. This sounds like someone is becoming ChatGPT. Just one big pile of nothing
    2