[flagged]
Also calling the project a "waste of effort" seems a bit out of touch. Effort doesn't have to pay off in any way to be worthwhile. If the act of building is part of the motivation then taking shortcuts at building it defeats the purpose.
131–140 of 293 posts
[flagged]
Also calling the project a "waste of effort" seems a bit out of touch. Effort doesn't have to pay off in any way to be worthwhile. If the act of building is part of the motivation then taking shortcuts at building it defeats the purpose.
Earlier quoted context omitted.
I think their C++ library is one of the reasons they can create capable software so quickly actually. They have jetisoned just a tonne of C++ nonesense and added some really nice modern features such as how they handle memory and errors. Also, you would think that having to implement EVERYTHING themselves ( they are making their own image decoders as an example -- inclding SVG ) would slow them down. However, as it i…
> they are making their own image decoders as an example -- inclding SVG Considering the vast amount of exploits that continually comes out of media decoders everywhere, this basically guarantees I will never ever use this browser.
Earlier quoted context omitted.
It is not any easier, because we still have a monopoly running the show, only it's not called Microsoft anymore. If anyone threatens Google position, they can literally throw money at the problem, invent some overcomplicated standard, implement it in Blink, and have the competition chase them. It doesn't need to go through W3C either, if it works in Chrome, all web developers will adopt it and any smaller engine will…
> if it works in Chrome, all web developers will adopt it This is why we, tech nerds who understand the problem, must resist monopolies: object to using such APIs. Chrome wouldn't be in quite this position if, instead of embracing the monopolist, more techies had warned their non-techy friends and family away from it, like they did with IE.
Becoming part of it isn't hard either, if you test software either as a SW engineer on a team or as a full time tester it might actually save you some time :
- If you use Mac, test in Safari first. On any other platform, install Firefox (or the Debian version, or Librewolf) and use it as the first tool to test applications.
- If it doesn't work (and the customer hasn't very explicitly said they absolutely only care about Chrome or IE^CEdge) report it as a bug.
I mean, seriously, who would have accepted a feature that only worked in IE 6?
---------
OK, some people might say: but IE 6 was an old and outdated browser, you cannot compare IE 6, or any version of IE for that matter to Chrome.
Or one might say: Chrome has already won, your idealism is appreciated, but you are too late.
Well, here is the thing: IE was at one point in almost the exact same postition as Chrome is now:
- biggest browser by far
- endorsed (or even enforced) by IT
- lots of features only worked in IE. (I remember one particular customer who seemed to be obsessed with security to the point were we had to keep a VM with Windows XP and IE 8 around with both Active X and Java Applets enabled to sign into them. This was around 2014..! Yes, if you find this notion of security absolutely ridiculous then we agree.)
---------
OK, one key difference:
Back in 2006 when I started fighting IE we had Mozilla on our side. Firefox was innovating like crazy. We had extensions that let us embed IE in a tab to render certain web sites. We could automatically archive a full website for offline access (full rewrite of links so they worked on our copy was included). Full developer tools that everyone knows from every browser these days started out as just an extension to Firefox, named Firebug IIRC.
Today, while I understand that the extension API had to be reigned in before a disaster happened, it went way to far and today we cannot even get a function in the API to programmatically remove the top tab bar when we add a tab bar on the side. And not only that, but if someone asks about that particular issue, someone will come and hush and hide the comment.
So godspeed to Ladybird devs and Orion devs, Librewolf devs and actually even Safari devs and everyone else who challenges the current monopoly!
Is it just for fun or not? I think it's important to face this question, because users should not trust a just-for-fun browser with their security, and we should not look to Ladybird as a meaningful contribution towards competition in the browser space if it's just for fun. If it's just for fun, we need to temper our expectations accordingly.
Hello everybody out there using minix -
I'm doing a (free) operating system (just a hobby, won't be big and
professional like gnu) for 386(486) AT clones.Earlier quoted context omitted.
The whole point of the project is to write a completely independent browser from scratch. The effort seems focused to me, write a complete engine. Not write a small part of a browser. But why would reusing something be better? Reusing someone else code wouldn't be competing with them, it'd be depending on them.
Because you can have something usable instead of dreams. If you want to have completely independent code eventually, then replace modules one by one, while having a working product. Like Mozilla did with Servo. They had C++ codebase they wanted to replace with Rust codebase. They did not create entire browser from scratch, but replaced C++ with Rust gradually. While one figures what HTML and CSS layout should look li…
Realising dreams is called progress.
The reason Chrome and Firefox exist is because people dreamt of having something better than the already "usable" Internet Explorer.
It seems there is zero c++ in their web engine (cannot clone their repo right now and github is spitting raw json while browsing their source code with noscript/basic (x)html browsers). Is this true?
I also find it curious that they are sponsored by a real estate site (:
This is a really cool project, but: "Where are the ISO images? There are no ISO images. This project does not cater to non-technical users." This comes off as really abrasive. Wanting an ISO image to quickly test this out is not an indicator of someones technical ability. I'm sorry I don't want to boot up a linux vm, install a lot of development packages and then build my own boot image just to try this out.
I think that’s often the point with OSS projects, especially those that have an ambitious long term vision. If you “don’t want to boot up a Linux VM” etc, they don’t want you. It’s a filter. It means their concern at the moment is the coherence of their community, not increasing their numbers. It’s the same reason projects like this often have absurdly ugly logos, and landing pages that don’t work on mobile. Fast growth is often seen as destructive when you already have a nice little community vibe. It’s essential to maintain that vibe carefully if you have a long term goal of building something important.
Earlier quoted context omitted.
I think their C++ library is one of the reasons they can create capable software so quickly actually. They have jetisoned just a tonne of C++ nonesense and added some really nice modern features such as how they handle memory and errors. Also, you would think that having to implement EVERYTHING themselves ( they are making their own image decoders as an example -- inclding SVG ) would slow them down. However, as it i…
> they are making their own image decoders as an example -- inclding SVG Considering the vast amount of exploits that continually comes out of media decoders everywhere, this basically guarantees I will never ever use this browser.
It's really quite incredible that one guy basically started a project to create a whole operating system from scratch for fun and to give himself something interesting to do, and then accidentally created one of the most viable new browser engines in a decade or two... I've been watching the development videos for a year or two, and the speed that this has progressed in such a short time is unbelievable. Now they hav…
He is a world expert on Web rendering, and an extremely capable C++ developer. One of their success recipes is to code up the various specifications directly, which is - today - the best way to go about this. They are also heavily test-driven. He did not even use the C++ standard library, when he says "from scratch" it includes his own string class, for better or worse, which is fine since it's "just for fun", "to le…