There's A New Browser (That ISN'T Chrome Based)

113,801
0
Published 2024-07-06

All Comments (21)
  • @wrux
    Judging a pre-alpha software project poorly is such a frontend dev mode
  • @kreuner11
    "Guys why is this piece of PRE-ALPHA software slow and buggy?"
  • @djenntt
    Who else thinks Theo should take a break from the internet 😅
  • @RichardJActon
    09:05 - Completely backwards take. Browsers are Not standards they are Implementations of the various standards that make up the web. Fewer competing standards is generally better - up to a point. More implementations of any given standard is generally better up to a point. You don't really know how 'standard' a standard is until you implement it this reveals the ambiguities in the standard that may need fixing. It can help to spot issues in how others have chosen to implement the standard / tooling around it allowing for improvement. 18:45 - This is exactly why having new implementations of standards matters if the standards aren't good enough that you can design these components well enough to work work largely independently the standards are not doing a good enough job of describing the system. 45:36 - Completely missing the point again - the spec is worthless if you can't implement it! You don't know if you can implement it until you do - the value of the implementation is in validating the spec The point is some ways is not the browser it's the web standards and whether or not people are following them. If you can't implement a new browser from scratch you have bad standards that people are not actually using which means you have ceded control to whatever the dominant implementation is and you are stuck with an fragile unhealthy monolithic single point of failure that if ripe for abuse by whomever controls it. This was a frustrating watch seems like you kind of got the point by then end but still not why it's an important thing to do.
  • Considering they are "targeting" an alpha release in 2 years, I'm surprised it can even render html
  • @rickdg
    By not using chromium, the project cultivates a culture of having to maintain its own thing. Otherwise, there’s a future where all browser are just adtech or waiting for adtech to find security/bug fixes. This project is mostly a preservation project for an open web.
  • @DFsdf3443d
    "usually things start fast and then get slow" is such a front-end thing to say. Andreas even addressed this in one of this videos. Its actually the opposite for low level software. Things start off slow but then get faster over the years as optimizations are added.
  • @TigreXspalterLP
    i dont get it. you seem to hype every ui library, which improves things in very minor ways, but you do a whole take down video of an ambitious browser project
  • @jackevansevo
    Man who's never built a browser speaks confidently about the best way to build a browser.
  • @irlshrek
    things do NOT start out fast and get slow...unless youre comparing the hello world version to the early version. the order is: Make it work -> make it right -> make it fast.
  • @calimio6
    I don't care what theo says, building a new browser engine is a huge take. Good luck to the ladybird team
  • Theo, let them cook, bro. You just pulled the dev build--not a 1.0 release. They just said the release target (for non-normies) is in a long way away. Go easy on 'em. They're building in public.
  • @yeox1929
    Linux was made "Just For Fun" read the book!
  • @PixPMusic
    "the thing that makes the most money does the most good" is so untrue I just spit my drink
  • @billoday
    The Linux take is just clearly wrong. Linus from the jump said it was just for fun to see how to make a kernel, like minix
  • @tato-chip7612
    People need to realize. Andreas started serenity OS as a project to break out of addiction. Same was also true for ladybird when he just wanted a browser for his project. He does it because he has fun doing it. I feel like the other stuff on foundation site is just flavoring.
  • @pavelmares97
    I am starting to think your research is usually few seconds. What do you mean they don't know html/css? If you look, the image is positioned absolutely. So overflow can be intended and the image is dark + text white. No issue there.
  • @Denominus
    Not using things built for other browsers isn’t some arbitrary line in the sand. It’s a choice to not use something that’s effectively controlled by another browser, making you vulnerable to the whims and choices of that browser.
  • @Shoey
    breaking: pre-alpha product is not in a polished state. let's critique the f out of it and its performance!!
  • @lcarsos
    You remember a month ago when we were talking about "don't drive by PR random repos trying to feel like you're contributing? Don't PR nit-picky README changes?" And now Theo's take is "look how innocent this little PR was, and the maintainers said no! Unbelievable!"