lynxwould like a word…Mozilla failed to build a new browser from scratch. How did they manage that?
They didn’t, not yet at least. What’s available right now is barely usable.
Thanks @warmaster!
It intentionally doesn’t support JavaScript to make things faster and much less resource intensive.
Ngl if you just don’t support the majority of modern browser features, it’s not hard to make a new browser.
Not as hard, I agree but reimplementing just CSS sounds like a very special level of hell.
W. JavaScript was a mistake.
The stuff like Flash, Java applets and Silverlight it eventually replaced were arguably even worse. There’s a legitimate need to run client-side code at times, IMHO the mistake was making it so permissive by default. Blaming the language for the bad browser security model is kind of throwing away the baby with the bathwater.
WASM is a better way to run code client-side, and has the benefit of not being a terribly slow, untyped mess 😌
It desperately needs interface types if we ever hope to make it a serious contender for general purpose web development. The IO overhead of having to interface with JS to use any web API is itself pretty slow, and is limiting a lot of usecases.
Browser permissiveness didn’t create implicit type coercion.
please use https at least for your own website lol
im a bit curious about the cjoice of gtk2 over 3 or 4, but im too eepy sleepy to look deeper rn ill do that later meows >w<
I think it’s just a place to start:
The browser is currently in Alpha stage
Planned support for systems in the near future: Linux GTK3/4…
Furry day?
