If we're letting agents send e-mail, what's the point of reading e-mail? Surely I can have an agent to reply to e-mail that other agent has sent. Do we really want to create dead internet?
A similar thing happened at my university in an Advanced Algorithms course. Students failed it so much, the university was forced to make the course easier to pass, by removing the minimum grade to pass.
I believe your case (and many other students) is that you couldn't abstract yourself from imperative programming (python) into logic programming (prolog).
In my opinion this can't even be labeled as a single HTML file, because it loads external files to complete the app. But back to the question, a "plain html" file doesn't load any external resources and is usually semantically described.
The issue isn't socially interacting with any of the users, I wish that was the major pain point.
The issue is having to handle e-mails, issues, feature requests, code-reviewing, continuous development, acquiring new users (otherwise project will stale) - all of this after a long day of work and balancing other important issues "non work related".
- Cross Compilation (even wasm and js) out of the box
- Simple concurrency model, similar to NodeJS
- Ability to use it on a popular cross platform framework (flutter)
- Hot reload capibilities (has JIT and AOT mode)
- Strong developer tool chain
All of these are built on top of a language that has a pretty syntax and supports many language paradigms.
The biggest con is the (weak) package ecosystem and community.
Function operations are possible in Go like it’s possible in any language that define function in the syntax. But functional programming goes beyond functions, and Go was not designed to support it.
I’m a fan of Go and FP and would love to see someone bridge other FP aspects like monads, in a way that feels natural in Go.
The additional features this tool brings (port enumeration, list usb devices, system info), makes me thing the tool was not designed for good/ethical reasons, but to ease the life of infostealers that are usually distributed via Discord.
Most Android apps are huge because they bundle tons of assets just to accommodate the “initial experience of the user”. Also, using bloat libraries and frameworks (any shipped by Google), increase the apk size.
Nowadays Google offers a solution for this problem called app bundling. It’s especially good if you build a mono app that behaves differently in certain regions. Instead of delivering a raw apk, you deliver a region specific app bundle.
I attempted to do this back at the start of this year, but lost motivation building the web ui. My trick is not CSS but simply loading fake images with <img> tags: