Hacker News new | past | comments | ask | show | jobs | submit | WallowingInShit's comments login

Except that wasn't a mistake, that was due to an intentional misinformation campaign.


So are you saying that new technology is not hyped with misinformation? Write once run anywhere?


Write once run anywhere, was Java's slogan in the nineties. And I still find the amount of abstraction JVM provides fascinating. At least since it became well defined memory model, you can write complex pieces of software and they behave remarkable identical on a lot of different platforms. I am aware that the API border to the operating system has always been the weakest link regarding practical portability. But I wouldn't call that misinformation.


This is bad design. Why excuse bad design? When I send a text message and it doesn't arrive, my messaging app lets me know. With Signal, this is a step backward.


You only know if your SMS fails to send, not if the receiving party has deleted their messaging app, broken their phone, or changed number.


> When I send a text message and it doesn't arrive, my messaging app lets me know

Signal does let you know, it never gets the delivered mark.


That's not letting me know, that's something I have to check.


I meant I check in Signal. It does indicate whether it's received or not and whether it's read or not.


has_my_thing(some_array) can be encapsulated too, using modules. For example, in elixir you have functions like List.to_string(some_list) and Map.values(some_map). This way, you get encapsulation and don't have to have a class.


Same thing, but for JavaScript: https://github.com/tc39/proposal-pipeline-operator

Going forward, the pipe operator is going to be showing up in many new languages. I've used elixir a lot, and the pipe operator is a genius piece of syntactic sugar.


M-x in emacs


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: