https://vieb.dev/
> Vieb is the Vim Inspired **Electron** Browser
WHY!?
You just made yourself inferior to qutebrowser right off the bat!
Even though qutebrowser is made in Python, at least it’s not Electron.
Also, websoyte doesn’t allow me to select text, so I had to get into inspect element to copy text, which is absolutely insane.
The other way is to disable CSS in order to re-enable browser functionality, I thought about it after the fact.
> Vieb is the Vim Inspired **Electron** Browser
WHY!?
You just made yourself inferior to qutebrowser right off the bat!
Even though qutebrowser is made in Python, at least it’s not Electron.
Also, websoyte doesn’t allow me to select text, so I had to get into inspect element to copy text, which is absolutely insane.
The other way is to disable CSS in order to re-enable browser functionality, I thought about it after the fact.
@ryo Electron for a web browser does, in fact, make some sense. The rendering engine is already implemented, thus, no need to implement it again
@neo It's basically a browser in a browser.
The point I've been making for quite a long time now is that there are way too many Chromium themes with extensions pretending to be its own browsers, only enabling the Chrome monopoly even further, and by that the centralization of the browser space.
The point I've been making for quite a long time now is that there are way too many Chromium themes with extensions pretending to be its own browsers, only enabling the Chrome monopoly even further, and by that the centralization of the browser space.
@ryo That ship has not only already sailed, but almost reached its destination already. Google is literally funding its competitor to avoid an anti-trust suit, that's how you know things are already fucked.
@Telvannichad @ryo
how feasible would it be to just replace javascript with something much more limited in scope
how feasible would it be to just replace javascript with something much more limited in scope
@neo @Telvannichad Occasionally, there are legit use cases for Javascript.
I actually don't mind vanilla JS, and if used when really needed.
Soydevs lack that discipline though.
I actually don't mind vanilla JS, and if used when really needed.
Soydevs lack that discipline though.
Follow
@ryo @Telvannichad @neo I'm kind of tempted to use it just so I can have a navbar that I can change on every page without server-side scripting or editing each individual page.
@neo @Telvannichad @ryo You can do that without AJAX. Just have an external script that puts down a few links via document.writeln() or innerHTML.
@xianc78 @neo @Telvannichad You can do it much simpler if it's just a navbar color.
So make it generate a random hex value on every page load, and ASSign it to the div as the background-color.
So make it generate a random hex value on every page load, and ASSign it to the div as the background-color.
@ryo @xianc78 @Telvannichad
I am literally only using it to load another html page and fake-frame it on the left or top so that it acts like a real navigation bar
I am literally only using it to load another html page and fake-frame it on the left or top so that it acts like a real navigation bar
@neo @xianc78 @Telvannichad
> I am literally only using it to load another html page
The HTTP protocol is designed to load a new page statically each time, loading another page without leaving the current one is considered bloat.
> fake-frame it on the left or top so that it acts like a real navigation bar
We have CSS for that.
> I am literally only using it to load another html page
The HTTP protocol is designed to load a new page statically each time, loading another page without leaving the current one is considered bloat.
> fake-frame it on the left or top so that it acts like a real navigation bar
We have CSS for that.
@ryo
I don't want to have to define my navigation bar on every single html page, if I can just define it once and load it on every other document that's much easier to maintain by hand
@xianc78 @Telvannichad
I don't want to have to define my navigation bar on every single html page, if I can just define it once and load it on every other document that's much easier to maintain by hand
@xianc78 @Telvannichad
@ryo
the navigation is static. the page they'll be on is static. i just don't want to write the navigation html on every page
the navigation is static. the page they'll be on is static. i just don't want to write the navigation html on every page
@neo This is why I'm using a static HTML generator.
Maintaining everything every single time is a pain.
Maintaining everything every single time is a pain.
@xianc78 @ryo @Telvannichad Yeah, I use it for that too
<script type="text/javascript"> (function(){ var request = new XMLHttpRequest(); request.open("GET", "WEBSITE NAVIGATION URL"); request.open("GET", "WEBSITE NAVIGATION URL"); request.addEventListener("load", function() { document.querySelector("#navbar").innerHTML += request.responseText; })
some real dirty shit, but it works