For me personally, I feel like a lot of tech companies are bloated and a lot of people are justifying their salary by doing unnecessary projects.
In many cases, it's all internal and no skin off noses such as this font project. In other cases, it means the UI changes every 4 to 6 months or even worse, the software becomes so bloated with "features" it becomes unusable so a clean replacement comes on the scene then the cycle repeats.
Sometimes, I feel, it would be better for companies to clap their hands and go "We did it, we solved the problem" then just stop. Keep the infrastructure running, do bug fixes, listen to customers on new features or changes but otherwise not do product churn for the sake of justifying salaries.
To expand on my view in an abstract way, when constructing a building construction workers, architects, project managers, and the whole cadre are hired then the building is built then all those people move onto new projects. Continual development of software is like if construction never stopped so that the construction crew still had jobs. A construction site should strive to transition from architects, cranes, and concrete trucks to maintenance staff, mop buckets, and screw drivers.
No iTerm2, weird shortcuts, random issues in video calls?, also not really cheap to get a laptop that reliably works with Linux and has decent battery life
What about multi-file / larger changes? How would you express files being connected, imports, and exports? Or are you thinking the hz files are disposable per change?
The intention is for the files to persist, and I didn't mention it, but a core part of the system is that the editor persists source maps. So at any point in time, you can map any generated line back to the line of pseudocode that generated it.
I'll be looking into multi-file stuff soon - it's an interesting can of worms to think through.
In many cases, it's all internal and no skin off noses such as this font project. In other cases, it means the UI changes every 4 to 6 months or even worse, the software becomes so bloated with "features" it becomes unusable so a clean replacement comes on the scene then the cycle repeats.
Sometimes, I feel, it would be better for companies to clap their hands and go "We did it, we solved the problem" then just stop. Keep the infrastructure running, do bug fixes, listen to customers on new features or changes but otherwise not do product churn for the sake of justifying salaries.
To expand on my view in an abstract way, when constructing a building construction workers, architects, project managers, and the whole cadre are hired then the building is built then all those people move onto new projects. Continual development of software is like if construction never stopped so that the construction crew still had jobs. A construction site should strive to transition from architects, cranes, and concrete trucks to maintenance staff, mop buckets, and screw drivers.