4 ms·
I think the frontend/backend distinction is mainly from the Web Development culture (that has unfortunately permeated everything else in software); it makes lit
by userbinator 5y ago
I think the frontend/backend distinction is mainly from the Web Development culture (that has unfortunately permeated everything else in software); it makes little sense if you're working on desktop applications, for example.
- toastal 5y agoWhy ‘unfortunately’? I figure most of us are grateful the internet exists and powers much of our lives (and livelihoods).
- userbinator 5y agoThe blatant disregard for efficiency and constant churn are a huge problem. Don't confuse the sane and stable Internet core protocols with the "web stack".
- deleted 5y ago[deleted]
- pseudalopex 5y agoBack end makes sense if the desktop app is a client for a server. You just wouldn't say front end because people would think you meant web.
- tempodox 5y agoIt can make sense if you're building a GUI app for Mac that's “scriptable and recordable”. I think you'd use VBA for that on Windows. The GUI communicates with the operational core via a message channel (analogous to HTTP requests and their responses) that can be recorded into a “script”. With those scripts you can automate tasks that would otherwise involve manually using the GUI. The “frontend” and “backend” wouldn't call each other's functions directly but use that interposed message channel instead. In that respect it's architecturally similar to a web app, but with all the code in one executable.