I use OMZ because it lets me rely on popular defaults instead of bike shedding and rolling my own. Its main advantage is convention over configuration. For instance, I just have to learn the git plugin aliases once, and then I can use them anywhere with OMZ + git plugin. Is there any lighter alternative that is compatible with OMZ plugins?
The problem I have with coding on Termux is that it's not a full Linux environment, and a lot of tools will fail to compile because there's some dependency that doesn't exist. That includes, for instance, database adaptors for nodejs, which compromises web app development.
Do you use any workaround for that huge limitation? Or just SSH into a proper Linux box?
This could be debatable if browsers had any UI at all to display XML. It's incomprehensible that if you open the open web solution for subscribing to web content (RSS) you're greeted with a wall of unformatted text. Right now, XSLT is the poor fix to that browser's basic inability.
+ Doesn't have the same compatibility issues Termux has, so I can install things like bun.js and npm packages with native bindings (e.g. database connectors)
- Can't edit text selection, which makes it difficult to copy text
- Can't paste text
- Frequently restarts and loses all progress while switching apps
I can't say much about the battery because I just haven't used it enough to tell the difference. Honestly, with all these major flaws, I usually end up just using Termux.
I hope they fix these glaring flaws soon, IMO they're a lot more urgent to get devs to actually use this than GUI support.
Nitpick: also, a more distinctive name would be nice. Right now, it's basically impossible to search for solutions to Android Terminal issues
Do you believe the amount of time developers have spent building hello worlds is a waste because those are useless applications?
Should go without saying, but the interesting thing about this thread is not that you can now play a flawed text version of an old game. It's that this example toy use case manages to explore the new capabilities and limitations of this new promising tool. This improves our understanding of this technology, and helps us make better use of it in the future, for more productive and innovative applications that we may not be able to predict yet at this point.
Relying on hacks for production code is usually a red flag/code smell that indicates there was probably a better alternative. `string & {}` definitely feels like one of those hacks.
As an alternative, wouldn't it be better to map the list of supported values in a structure like an enum?
Example:
```
enum HelloWorldValue {
Hello: 'hello',
World: 'world'
}
const value = HelloWorldValue.Hello
```
And now you can call that enum when declaring a variable value and get its contents in autocomplete. As a nice bonus, because these are references and not strings, you can ask your IDE for all places instantiating those values, which can be a life saver.
This is what happens when you are building rules are around an existing system versus the other way around.
In another language you have a value of type String which can take any value, might crash, might not, when you give it a color value.
And then you have a set of items like you described, which are convertible to String (or are a string, like your enum).
In fact, the receiver property probably shouldn't even be String, but typeof Color, which can be constructed through a method/constructor that ensures the String input is a valid format.
I like to focus on the main business element. If it's a SaaS for sharing videos with comments, for instance, I'd take a longer look at the video and comment models, their relations, and the call chain from API endpoint to model.
Another strategy I like is picking parts of the codebase and trying to refactor them. You don't even need to commit anything if you're not supposed to go around changing things: just by spending some time moving things around, seeing what breaks and so on will give you a better understanding of the code and what it does.
