198 karma · joined August 22, 2013
Do you use any workaround for that huge limitation? Or just SSH into a proper Linux box?
+ 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
I've got a strong preference for open source apps, so this is the best news I could get from this app.
Thank you for your great work!
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.
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.
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.
I wonder how it got to the top of hn all of a sudden though.
Agreed on both. Maybe it should have been done sooner, to avoid looking reactionary. Though I understand why today that propaganda may be considered worse than in the past.
> Sure, but there is clearly a difference here.
There's a difference, but not significant IMO. Just like misleading results should generally be penalised, to help people get to the information they requested.
This isn't about silencing a political view, cancelling an unpopular opinion, or whatever. It's defending against a deliberate attack from an oppressive regime. Search engines already have to do a lot of tweaking, for instance to defend against SEO spammers. I don't know how can this be controversial.
Anyway, answering your question, I use and like Ecosia. I've heard good things from Brave Search, but haven't tested it yet.
The developer can definitely do work like providing samples of generated SQL, UI screenshots and so on. Again, knowing who will do that deep due diligence is more important than the actual decision.
In my previous team, the reviewer was the main responsible for the code they were approving. They were expected to test locally and should actively hunt for potential issues, such as checking in the logs that the ORM was building correct SQL.
In my current team, the developer is the main responsible for the code they're pushing, and is expected to do all the tests needed. Reviews are more about ensuring code standards, finding possible oversights, requirements mismatches, and so on.
No one strategy is right or wrong, as long as expectations are set and everyone knows their responsibilities and expectations.
I honestly believe the only way for a search engine to be as valuable as Google was years ago is to let human knowledge drive more decisions. Maybe closer in spirit to what a web app store would look like, or closer to the categorisation Yahoo did. Not to browse by category (though even that would be refreshing at this point), but to better select the most relevant search sources.
I feel your pain about wanting more R&D around treatments and potential cures but finding almost nothing because it wouldn't be commercially viable.
My main strategy was trying to contribute with what I know best: software development. The company I joined (lifebit.ai) is building tooling to reduce medical/pharma R&D costs, in an effort to make it economically viable to research diseases that weren't viable before. This is a mission I can get behind and that feels like the best use of my time.
I hope you get to find the best way to have the biggest impact. Good luck!
If worker pay isn't keeping up but company profits and equity are, this means that people are overvaluing being a worker and undervaluing being an owner, compared to market equilibrium.
Why would that be? Risk aversion? With the latest advances in global connectivity, online business infrastructure, ubiquitous technology and so on, I'd expect risk to be as low as it ever was.
Something else? What am I missing?
Right now, it seems to be one of the best protected PoS chains. It's still fairly new, with novel mitigations, so it still doesn't stand the test of time against all possible attack vectors.
In that sense, it still can't be considered as secure as a PoW chain with high hashrate, which is protected by thermodynamics (you can't produce more hashes than the physical energy you have access to allows).
Bitcoin is an open source permissionless protocol, so you have multiple clients to chose from, each with their own list of bootstrapping nodes, many open source where you can submit a PR to add your node too. You can even build your own client and point to whatever you want. You can also just ignore them and just point directly to nodes in a list from a public forum, a private chat, whatever.
Also, you're not just connected to those bootstrapping nodes: you use them to find the rest of the peers in the network.
Soft forks don't force you to download and run new clients just to be able to use the network, which is an important difference. You can use your existing client, you just don't have the new features and don't run validations on them.
The greatest risk on soft forks is that chain split you mention. That's why any reasonable soft fork deployment requires a long time window with a large majority of hashrate signaling support (like 95%).
This is not FUD, it's the most obvious PoS flaw, called long range attack, and the reason PoS chains often need more checks to be more trustworthy (e.g. keeping hardcoded checkpoints, choosing the first received block as valid, introducing penalties and so on).
All network participants are forced to verify the full chain from genesis. Some might be OK with validating block header signatures only, and not the full transaction set. It's a tradeoff.
You don't need to use those public key servers if you somehow distrust the CA certificates in your OS. Feel free to contact the repository maintainers or whatever else floats your boat.
Anyway, bitcoin is an open source protocol, not a particular client implementation. If you distrust everything and everyone, no one can stop you from building your own client that works with the rest of the network.
The best metaphor is perhaps digital cash. No government can edit the cash in your wallet out of there, but as the owner, you can definitely lose it by force or stupidity.