Ah. Thanks for the info.
I'll add that to the list of terms I utterly detest because they are confusing to a non-dev.
https://developer.mozilla.org/en-US/docs/Glossary/Chrome
"In a browser, the chrome is any visible aspect of a browser aside from the webpages themselves (e.g., toolbars, menu bar, tabs). This is not to be confused with the Google Chrome browser."
Notedeck is *a* browser, but one that uses feed definitions not HTML/JS.
Discussion
see. it's netscape corporate culture. i mean mozilla. in case you didn't know, mozilla was what netscape turned into. mozilla was the codename for their browser project to replace the netscape browser. it is short for "mosaic killer"
mosaic was the name of the first web browser, it was developed in some university, and then microsoft bought it and turned it into internet explorer. a few years ago they abandoned internet explorer in favor of also using google's chrome engine, with the "edge" browser.
so, netscape killed internet explorer, but google chrome killed mozilla. i mean, for real, ok a lot of "freedom tech" activist types are all using mozilla, it's the default packaged with most linux distros, but that's like 5% of the market. the other segment that isn't using apple is all now using google chrome.
So I'm in the extra ultra weird minority. 🤣🤣🤣
i think it's a terrible concept, the web browser. it started out as a hypertext document viewer and turned into a whole application runtime.
probably without web browsers we'd have a simple cross platform UI that maintains all the platform idioms but allows abstraction to bind it to any language you want. instead we are stuck with javascript, and now, typescript, which is the work of microsoft.
that (the latter thing you said) was the goal of the last company I cofounded. we failed, unfortunately, but I still entirely believe in the concept of Hypermedia and a malleable UI/OS
i do too. you may have heard of Oberon perhaps? this was one effort towards this based on a language that was also an operating system.
Go is based on a lot of the design principles in Oberon, which is descended from Modula and then to Pascal. the principle is that source code becomes the primary form of distribution of applications and libraries and in theory you could wrap such a runtime engine inside linux, darwin, bsd mach, and windows kernel, and then you would have a universal design. throw in the extension of the "everything is a file" principle of unix to "everything is a server" of plan 9 and who needs browsers anymore. your whole GUI is a browser from top to bottom, running fast binary code compiled from the source code fetched from the internet.
i mean, in theory most of it could be interpreted, to have a shorter time for first deployment but Go's insanely fast build system proves you can do the same with binary.
IMO, the biggest mistake with the browser-as-app-runtime is the way it messes up the boundaries between presentation and application logic. it is not that difficult to abstract a clean interface between the two things and eliminate the single-language requirement. but most of the dev world is obsessed with objects, even though they are just primarily a mechanism for breaking domain boundaries. applications are called processes in most operating systems for a reason. not OBJECTS. objects are some kind of frankenstein between application and data. once you blend these two things together, it becomes impossible to do certain things efficiently at higher levels of abstraction, and it creates a bottleneck in development that sees endless major version upgrades, with codebases that are entirely chopped and changed, again and again for no reason, destroying the whole point of software development's most important principle: clean interfaces, and separation of concerns.
imagine having software that didn't need to change every 3 days? or: arbitrarily old versions you could still run. or: it "changes" constantly because the proper things are fixed/fully malleable in realtime.
there's basically a corparate UC conspiracy preventing this world from existing.
yeah, i'm not a fan of the "you must update to keep using" shit like discord and others do. it's like uh. how about you don't break your APIs on a weekly basis for funsies?
I would recommend trying keychat. Basically we already have this and it integrates with amber.
For what purpose? I already have amber. I don't care about nostr DMs.
Its not about dms. Keychat is basically a nostr browser with amber support. So any web based nostr app, for example nostrudel or plebian market, or nym or kanbanatr anything. Im saying we already have the app that will wants to create and it supports amber login and then ALL those websites dont even have to both implementating.
Ok. That's terrible naming, then. 🤔
