![]() One thing that’s kind-of well-known is that WebEngine doesn’t have a particularly deep API (yet). Granted, just about every major browser is packing pretty big binaries anyway – but it’s still wasted space. If a distro ever eyes Fiber as a default browser it means there’s over 40 extra reasons to consider a slimmer browser which makes use of more common libraries. This is more due to WebEngine being part of Qt and already being on the system – but CEF isn’t, and so the rendering engine is a separate binary to distribute. Since Plasma Mobile includes a more malleable stack I have less doubts that Fiber will run fine on that, but I would like to see Fiber eventually run on Android.įinally, CEF will add a lot of weight to the browser as an external dependency, to the tune of at least 40MB at minimum. I would also like Fiber to be extremely portable, which makes CEF more of a concern WebEngine currently supports mobile, but CEF will only have Android support ‘in the future’. This doesn’t even include potential future CEF implementations who knows what might show up in 5 years. At minimum CEF means more complicated work than using an established Qt API.ĬEF and having multiple engine options also means that we may see two entirely different sets of bugs coming in, depending on whether or not a person is running Fiber-Chromium or Fiber-Servo in the future. The Qt guys didn’t decide on this arbitrarily as they have a different goal for the WebEngine API. The first and biggest downside is the fact that CEF doesn’t have a Qt library. Not everything is rosy and bright in the world of CEF there are always downsides. Valve in-particular bases their Steam client on the thing. Adobe, Valve, Blizzard, Amazon, and other big names have thrown their chips behind CEF. Servo, Mozillas new wonder engine is actually building itself to be a native CEF implementation, meaning that future Firefox will actually be a CEF-based browser.ĬEF, despite being not so well-known, is actually used by some very high-profile companies which lends credence to the longevity of the project. While it started off as just an implementation CEF has a defined stable enough API that it turned into a sort of pseudo-standard. What is it?ĬEF started as a Chromium-based project meant to create a stable API relative to the rapidly changing engine, something non-qt applications could use as easily and reliably as Qt applications do with WebView. After Fiber kind of came into the light I had a comments and emails pointing me to CEF, the “Chromium Embedded Framework” as an alternative to WebEngine.Īfter doing research it’s severely divided my thoughts on what to use. When I started Fiber I worked under the assumption that WebEngine would be the engine for this browser it’s an official Qt extension, being actively developed, and isn’t going anywhere. The result now is well commented code, and consistent naming conventions in-line with other Qt/KDE projects.īut re-factoring code isn’t what I’m really interested in talking about… WebEngine vs CEF I also spent a good chunk of my time reading Qt and KDE coding guidelines and documentation on how files and classes should be structured, and then I applied that information to Fiber. He is passionate about Alabama Football, all things nerdy, and his Golden Retriever, Butterbean.Fiber has seen some active development, and over the course of a long 3-day weekend full of hacking I’m glad to say that exactly 0 progress has been made! Of course that would be a bit of a fib, I’ve spent the weekend re-factoring all of the profiles code and organising the codebase structure. There is no growth in comfort." He believes that hard work and a positive attitude can take you far in life. ![]() Wil's motto is "There is no comfort in growth. All of these experiences lead him to his current role at Rhino Web Group. In 2020, he moved to Texas where he became the Marketing and Graphic Designer for Xochitl Chips and Salsa where he found he had an innate skill for marketing. After college, he was appointed as Art Director of the 2019 Edition of Alabama Advantage Magazine. Before graduating, he began his design career at his university newspaper as Assistant Lead Designer at The Crimson White, and as a Creative Designer at Capstone Agency where he found a passion for designing and working with clients. He has a Bachelor's Degree in Communication and Information Sciences from the University of Alabama. Wil specializes in Graphic Design, Social media and Website Development at Rhino Web Group.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |