It intentionally doesn't support JavaScript to make things faster and much less resource intensive.
this post was submitted on 27 Dec 2024
62 points (98.4% liked)
Privacy
32587 readers
283 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
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.
But…that’s just a setting on all the browsers
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.
Browser permissiveness didn’t create implicit type coercion.
Considering the community we are on, I assumed the criticism was more about the privacy problems surrounding the engine and browser security model than the quality of the language itself. If that was the intent, I mean... Yeah, its weak typing is a fucking mess.
That's fair. I just assume most people who reflexively insult JS are like that usually because they've written something in it, rather than having dealt with the many vulnerabilities and annoyances browsers have made possible with it
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.
this is why i will write my blog from scratch with absolutely no JS or code execution of any kind
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<
Furry day?
every day is furry day ~~if you're the right kind of linux dev~~
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…
o my goodness i didnt even see that hehe >w< it does look cool meow :3
Great to see another brand new browser under active development!
lynx would like a word...
please use https at least for your own website lol
it has https for me
i clicked the link, boom certificate warning
accordimg to firefox android they use letsencrypt
i use cromite, which also supports https
Everything supports https today, I think that wasn't a question
from the browser side, yes. But not all websites are hosted on https
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!
Checkboxes are displayed as input boxes. Well, it's an Alpha.
Tested it with flatfox.ch "Your browser is too old" while it works even with Dillo and Links, seems a useragent-issue.