Careful you don’t come off as a sealion.
Though this is a thread about Wayland so eh.
Careful you don’t come off as a sealion.
Though this is a thread about Wayland so eh.
Thanks, you made me feel old today. Get off my lawn.
I’ve watched some slow typists program, and I think I have the answer. If it takes you a while to type the code out, you are much more likely to stick to the first approach that works, and not rewrite it as much.
??? What the what now?
Yuuup. Webpage with a button to toggle a bit in a database. For a personal project, 1 day. For work? Well it took a few weeks to figure out what database, what pass security review, register our subdomain, get traffic quota, revise security review, mocks, learn new framework as the old one is deprecated, set up a new group to run the app as, including admin group and two person authorization to make changes. Set up autopush and test environment. Uh key rotation schedule. Reply to comments on the design doc questioning our choice of database. Translations for all the text.
Only took a quarter.
Edit: oh I forgot gdpr deletion service. But we got to hand that off to another team. Yaaay.
Have you looked at the Lisps / Scheme / Racket yet? Racket in particular makes it quite nice to go
#lang blah
at the top of the file and change the parsing or interpretation entirely.For example all the documentation pages and guides are written in scribble:
https://docs.racket-lang.org/scribble/getting-started.html#(part._first-example)
#lang scribble/base @title{On the Cookie-Eating Habits of Mice} If you give a mouse a cookie, he's going to ask for a glass of milk.
And it has an entire document markup language created in it, which can output pdf or html. But you can still use @ syntax to drop in racket code to compute values. Or create templates.
I even implemented a #lang which took assembly directly (and interpreted it, it was for a class).
So if you are really after full control, you should study Lisps and their macro systems.