Hearted Youtube comments on Fireship (@Fireship) channel.

  1. firebase should do fireship in 100 seconds
    1200
  2. The funniest of this, that I'm a React developer from Ukraine, watching this in my basement after air raid alert here in Ukraine. You've just made my day bro. Peace to you guys!
    1200
  3. Fun fact: You can use $0 instead of $SHELL to get the actual name of the current shell, not just the path
    1200
  4. I was with you up until "CSS is way harder than React and Firebase."
    1200
  5. That error screenshot gave me PTSD
    1200
  6. "At least now she knows where she's headed" 😂
    1200
  7. I rarely comment on any videos on youtube, but Jeff, the comprehensive yet compressed way of teaching things, like you do here, is more than awesome. it's so amazing. i am speechless. i really want to say thank you for your effort to contribute to the dev community in that way.
    1200
  8. Lol what's the fun in coding then. I imagine employers/exams would be like "no copilot" allowed
    1200
  9. Of course the code is the most exciting part to us it's literally our job hahahah
    1100
  10. Oh yes, PHP. Now I can't wait for Ruby on rails in 100 seconds 💎🎉
    1100
  11. So, the main take-away from this video is that the operating system is a squishy snail inside a shell?
    1100
  12. sequel for short, now that's how you settle both sides of a debate
    1100
  13. I think everyone is "awaiting" this
    1100
  14. every programmer is different, but VSCode is what unites every one of them
    1100
  15. 2021: FireShip`s content quality stops increasing, because it's already perfect
    1100
  16. Watching it from a GNU/Linux based OS, a big respect goes to you, bro
    1100
  17. 100 seconds! That's all the attention span I have
    1100
  18. How many days of researching, learning, and developing behind this 20 minutes video? Awesome work 🔥🔥🔥
    1000
  19. "the console is your canvas" is a dangerous thing to say. Someone is going to figure out how to inject functioning html and js and into a console output, and end up building an entire app in the dev tools output window 😂 Maybe we could build some kind of logging system inside that inner app 🤔
    1000
  20. Been writing JS for 20 years, knew all of this shit already and still enjoyed your video... accurate, professional and fun.
    1000
  21. "I use arch, btw" You had to say that, didn't you? 😂
    1000
  22. "Blockchain is just a LinkedList but with salt."
    1000
  23. "I've got a fever and the only prescription is more Fireship!"
    1000
  24. click the f**king button man its his f**king dream😂😁😂
    1000
  25. Kids :- build Twitter from scratch Men:- build zoom from scratch Legends :-build AWS from scratch 8:14
    1000
  26. I really love how u are delivering great content almost every day
    1000
  27. imposter syndrome has joined the chat.
    1000
  28. I send these to my team whenever they come out, the insight/time is absolutely insane.
    1000
  29. 'Open DreamWeaver'.. Wow! Good old times.
    1000
  30. 2:14 "Segmentation fault" - classic
    1000
  31. Once you deep dive into cryptography you find that, even the strongest encryption algorithm in the world is weak if the user input is weak. The best course of action is to have an input that does not come from the user (I mean a generated password like a sha-512 hash). Ideally that entry is stored on the client device.
    997
  32. Hey man, love your videos, but a small correction for what you mention at 1:45 "Kafka guarantees that any consumer of a given topic will always read the event in the exact same order" That's true but at partition level. A topic is made of partitions, and a topic with 1 partition will guarantee that. But as soon as you need parallel consumption you need more partitions (one per concurrent consumer). When having multiple partitions, a single, non-concurrent consumer will get the events of any partition in the proper order but events from different partitions may be consumed with different interleaving This is why it's so important to put a proper key for your messages, as it's the default value used for sending your message to different partitions (different events with the same key will always end up in the same partition) Again, love your content, you explain super great. But I thought that that small point had to be addressed 😄
    988
  33. Pls try Elixir in 100 seconds. It's a really nice programming language. Great vid tho
    985
  34. 10 Design Patterns noted in 10 minutes. - Singleton (Creational) Object that can only be instantiated once. Use case: Settings - Prototype (Creational) Fancy word for "clone". Create clone object instead of extending object. - Builder (Creational) Create object with methods instead of constructor. Examples: JQuery. - Factory (Creational) Instead of using a new keyword to instantiate and object you use a function or method to do it for you. Use case: Cross platform app - Conditional checking to determine which button to show. - Facade (Structural) A simplified API to hide low level details in your code base. Use case: Create facade class that contain the low level systems as dependencies which then simplifies their operation. Examples: JQuery. - Proxy (Structural) Fancy word for "substitue". Replace target object with a proxy. Examples: Vue's reactivity system. - Iterator (Behavioral) Traverse through a collection of objects. for loop. - Observer (Behavioral) Many objects subscribe to events that are broadcast from another object. one-to-many relationship. Loop that unfolds over the dimension of time. - Mediator (Behavioral) Is like a middle man or broker. Examples: 1. Air traffic controller that sits between the runways & airplains to provide coordination & communication . 2. Middleware - State (Behavioral) Object behaves differently based on a finite amount of states. Examples: Finite State Machines
    985
  35. From now on, I will use emoji class names on all my personal projects :D
    982
  36. Jeff, 12 months ago I started closely following your content. I worked on side projects, I started a routine and I learned how to learn, all from your videos. To top this year off I scored a role as a software engineer at an awesome company, a job that I thought would always be beyond me. Today I signed up for lifetime access to fireship pro, to say thanks. But to also pay it forward, so you can keep putting out content and empower others like you did me. Thanks again mate, all the best.
    964
  37. Dude make web assembly in 100 seconds !
    955
  38. Dart = java(only the good parts) + JavaScript (only the good parts)
    954
  39. I absolutely love this! As someone who made several videos on NginX I understand how difficult to summarize this tech in 100 seconds. Amazing as usual.
    947
  40. All fun and games until someone start dossing literally your home connection trying to bring down your stupid to-do list webapp hosted on a Raspberry Pi
    940
  41. I reacted in less than 5 seconds to open this video. hehe
    939
  42. Your firebase cloud functions course really helped me out on a school project, thanks 🙂
    934
  43. Me thinking I'm only getting 100 seconds but actually getting 511 seconds: Wait, that's illegal!
    920
  44. it’s not all rainbows and Flutterflies
    916
  45. 8:11 " He created git!" - Lol why not right
    906
  46. Tailwind in 99 Seconds -- Taught by Jon Frok. Coming soon.
    902
  47. yes.. now i can finally take down zoom
    893
  48. Hi, PocketBase author here. @fireship did a great job with the video and managed to present a lot of things (Linode, Svelte, PB) in a very compact and easy to understand format. After reading some of the comments, I'll leave just couple notes: 1. At the moment of writing, the chat app seems to be using an older PocketBase v0.8.0 version. The latest v0.10+ releases come with split db pool and significant performance and memory improvements. 2. The realtime connections can quickly exhaust the max open files limit and you may want to increase it accordingly to the expected concurrent load (from the systemd in the video is around ~4096). 3. For those commenting that SQLite doesn't scale well - it is PocketBase fault that the chat app doesn't perform well on high concurrent load and further improvements will be done in the near future. For a single server setup, plain SQLite in WAL mode almost always will outperform other traditional databases. (ps. this is a second attempt to post the comment since the first one probably got flagged because of the github link).
    892
  49. This is awesome! Have you thought about doing a Beyond video for Rails? I know it's not considered a "hot" framework nowadays but it's definitely still got a lot of use cases.
    892
  50. “Architecture of the Burrito in 100 second”, please
    879