fullstacking
I used elixir because thats what I know and love so it was mostly just a personal choice rather than a technical one.
/s
Second: pixabay
Third: Yeah that's the challenge I'm working on at the moment. Thanks for the feed back.
I do plan on cleaning up the repo so that you are not starting with the example and also plan on making a small tutorial video to show how much effort it takes to setup.
Street Photography by Josh Chernoff
I'm abandoning a techstack because of it's community (or lack there of)
I'm not gonna bother saying what tech stack it was or even the specific tech issues I had with it or liked about that given tech.I could do that but honestly who cares? I've already moved on and have a profound realization.My issue with it was never the tech, it was with it's community.I tried to engage in a non contentious way but it was always hijacked by it's community "try hards".You know...
Calling the server distribution is an over simplification of the issues. To this point we should only use the browser in the terminal, but even when its just text it still has to "format" it's content.
this the problem, who owns the "formats" for the content in a system where many sub systems needs to be aware of "formatting"
If the server didn't have to be aware of the html at all and it was only ever just raw data I would agree with your view.
Ok I will bite. in the realm of desktops, what is the "backend"?....
But also lets assume you are talking about c/rust what ever code. Then you saying that because qt/gtk does not generate something for that code that is equivalent? This is such a reach. First The c code does not need to render a initial output before qt or gtk kicks in for starters. sounds like you just want to boil the ocean. F it, lets reinvent TCP everyone...
Also just gonna put this out there, what is your web agent if not a desktop app...
But really I can't even with this. I'm looking for sensible solutions to this real problem. I guess throwing your hands up and saying everything sucks is an option but I don't have time to think like that.
Maybe we need to acknowledge that you can't seperate them as they both exist with a need to produce HTML. But instead position the html closest to who it best serves and let them inform the other side. IE JS is most concerned with html as it interacts with it more where as the server only needs to really produce it once.
IMO your take is the worst take on this issue.
The HTML template is the core of all front end vs. back end problems
WIP: A website for listing / finding free plants in your community
Simple link aggregation and bookmarking site
Better Access Control by Default with Phoenix 1.8.0 Scopes
[Domain, link counts]
github.com 7819
www.youtube.com 3990
hackaday.com 1590
www.theguardian.com 1553
en.wikipedia.org 1509
arxiv.org 1317
www.theregister.com 1196
arstechnica.com 1001
www.nytimes.com 967
medium.com 910