"backend" and "frontend" are arbitrary categories made by bureaucrat programmers that are dead inside.
Discussion
This guy almost gets Nostr.
It is a very good question if your database is actually a damn server already anyway. People have tried to address it in the traditional world before, with things like CouchDB, Firebase, Postgrest, Supabase and the "local-first" community.
Nostr is that but also adds the fact that you are actually talking to a ton of different databases that you don't control.
The truly interesting difference is in authentication.
In traditional servers, OAuth tokens are used to protect database write access, because all the rules of the app are made up and stored in the database itself. So the database itself is the "protected resource".
On Nostr, the database is public and open. It has no fantasies, just data. The "protected resource" is actually the user's private key. So authentication is reversed. The server demands authorization from the client rather than vice-versa. Truly mind blowing for anyone stuck in web dev for the past 20 years.
you can also go full on database-less when building an app. app has a keypair and can rw encrypted state data to relays. I did this in a PoC strava bridge where I stored app data on public relays. pretty paradigm shifting.
This approach needs to be leaned into more
🎯
To be fair this is true for all "web3" in general. from Bitcoin wallets to ethereum dApps to nostr
I've always considered the DB to be the backend 🤔
front end is heathen complicated bullshit
show me your Go GUI and i'll show you mine (mine compiles and works, mostly)
We are all full stack developers
LMAO, no.
In a restaurant, the front of the house is the part that has the interaction with the customers, the back of the house is where everything happens but has very little interaction with the customer.
So, think of an app/program as a restaurant and you’ll understand why your comment is hilariously ignorant.
That’s a good analogy.
Owch!
Moreso came out of pivot into role specialization in IT. I remember coming out of college in the early 2000s, roles were much more bucketized -- Help Desk, Systems Administrator, Network Administrator and Programmer is pretty much all we had at Sony where I took my first job. Many, many more jack of all trades, master of none types.
Then C-Suites and MBAs put on their dunc... thinking caps and ushered in specialization all over the place. Within a few years, that programmer role now was split into individual languages or technologies and we suddenly had 5x the people. Same with systems administrators, getting a mail admin, Windows admin, Linux admin, so on and so forth.
When I'm at now, we have people that know a singular language or technology and are completely fucking worthless outside of it. I'm talking lacking fundamental cursory computing knowledge to boot.
That said, all IT professionals all dead inside to some degree.
i'm not learning c, python, c++, rust, or fucking javascript, no, that's not negotiable, i have very good reasons, and mostly it's just that you'll have me doing nothing productive for months for any given task outside of what i already know
unfortunately nobody bothered to make a really good Go GUI so i'm stuck in the back of the shop
if someone fixed that problem you'd be back to the old days because it taes like a week to get used to working with Go versus 2 months for C++ and Rust and python is slow as piss so why bother
IIRC, back at Sony you essentially had to know either C/C++ or Java and then Basic, SQL and got bonus points if you knew COBOL. When I left, we had multiple individual developers for all of those as well as separate front end developers. Hell, they literally hired people that did nothing but played with PL/SQL scripts trying to shave seconds off their runtimes.
We were an Oracle dominant shop.
the industry has grown enough now taht you can specialise, that's part of what's going on i think
i hate it that Go has such weak libraries for GUI apps because i'm quite good at building them and the concurrency in Go was actually originally devised for GUIs (newsqueak, circa 1985)
c/c++ has a huge learning curve especially with the build system (the language itself isn't so hard)
java is a bit more reasonable but setting up the dev environment is painful until intellij
basic, haha, that was my first language, sql i aced the test in highschool circa 1992
it's pretty amazing but there is still work for cobol programmers... mostly banks of course, nobody else uses that shit, holy crap have you actually read cobol code or the language spec, it's like writing legal documents
Yeah, COBOL is fascinating to follow. I have a buddy that basically works a handful of months per year while making a killing. Just travels around to companies helping them with their COBOL issues since there are so few of those dudes left.
yeah, it's an awful language but i guess if you know it, nobody wants to learn it and dumbass banks don't spend the money on upgrades and actually
they are probably wise to not upgrade
i'm literally in the middle of learning how to use a smart contract language that has super severe guards on doing dumbshit and cobol also made it hard to do dumbshit so ... idk... these days you can probably make good money doing financial programming with Move, it's pretty good, but it realy is like cobol shrank down a bit and using Go semantics and Rust syntax
I don't think that relay developers are dead inside.
“shirts” and “pants” are arbitrary categories made by big textile to make you think you have to wear one of each