Sure. In terms of making a decision, yes, in the healthy process, there should be a person with a formal power to decide (and take responsibility) eventually.
I was more curious about the discussion when the parties were speaking on the same level of command.
Agree, I wasn’t consistent with “a framework” vs “just language” approach. Ideally it should be 100% one or another.
My idea was to use the standard library as much as possible, but I didn’t eliminate the use of third party libraries entirely if it would allow async/concurrent processing.
It all started with Go vs Rust vs Zig as the main point of comparison. Then I added more languages I am familiar with.
By far, IMHO, Go is a clear winner in terms of being 100% with the standard library, fully concurrent and quite concise.
Sure, JS/TS implementations are also concise but it is different, not natively compiled technology.
The language's selection is purely my personal familiarity, so nothing wrong with Java, it’s just not my area.
Has anyone used htmx for a more or less large project?
Everything turns into spaghetti code really quickly.
Separation of API and frontend isn’t just for fun. It’s for making testing bearable.
Finally, mixing data modelling (database) with presentation (html output) in one place (htmx handler) goes out hand really quick too, making testing much harder.
But real coding cowboys from the golden age don’t write tests, right? :-)
This feature of Go tool chain is so underrated. Yes, there is nothing magical here. I can achieve similar outcome with some custom preprocessing, but having it built into the ecosystem, with type checking and inferencing, single binary compilation, etc. is a great productivity booster.
staging or index is one of the most beloved by me features of git. It saved my careless butt from loosing files SO many times. I stopped counting. Severely underrated, even complained about to be confusing.
I’m always puzzled when people say than git is hard, confusing etc. Is English hard to learn? Russian? Chinese? It depends, as always.
Yep, it’s a learning curve, and as deeper understanding comes, in more ways you start bending this great tool (git).
There is an endless ocean of toolings, helpers etc of all kinds, for all levels.
I’m not saying git is the best. There is no the best tooling in general. Fossil is great, git is great, and some other VCS. Pros and cons are everywhere.
The ugliness of vanilla CSS is in the absence of scopes, though it’s coming.
I was a big fan of Tailwind, but after switching to mostly Svelte, where CSS is scoped by definition, I found that the vanilla CSS is not as nasty as I previously thought.
Releasing to public the sources of the old software, especially from platforms which are gone, is very cool!
I would die to see the original sources of Norton Commander 3.0 written by John Socha. They say, he used "an ortodox" (back in the day) approach of C and assembler mashup, which not many programmers used that time, and "real programmers" always wrote in assembler :-)
The only use case I found (though still quite possible) is if I have NO access at all to any of my devices, and I only have access to internet, and precisely - web only. I could go to 1Password website (for example, in an internet cafe or via someone’s tablet), get into my vaults with the master key and the password, and start recovering other passwords, details etc. Without SaaS, it would be barely possible.