It is always dismissed as too verbose, while in go’s case it is never mentioned, when in fact the latter is way more verbose.. People’s bias show.
@programming.dev
No, an alias will only give you pseudo-anonymity. Even trivial analysis like counting which words occur together frequently in your writings can reveal with very good accuracy any other alt of you, so the available information of you is basically everything you have shared online with enough accompanying self-written text.
What impact do games have? Computers use very little energy, and come on, books?! Your plan is just plain stupid.
You can live an ultra minimal footprint life while not suffering - sure, maybe if you live in a huge house alone, move to an apartment and use public transport if feasible, etc. But there is no point in being depressed and basically torturing yourself.
Wait — it uses websockets for each and every user??! That’s just completely insane and of course it will fail to scale! There is zero reason for that, have specific live threads with websockets where it makes sense (though that is only mostly a one-way communication so even there it is an overkill), but for mostly static content it is just insanely inefficient.. surely I’m more than fine with that upvote appearing a minute later and not in “real time”!
Though to add: many things in your file system are listed as “files” in a directory, but are completely virtual with varying ways on what they do when written to/read from. (Also, linux has streams and files, not only files) E.g. /dev/null will read zeros, and discard data written to. But it has no physical backing.
Languages also have inner consistency. E.g. the mentioned python len function is inconsistent with the rest of the same language - and that is a statement that is true in itself, without an external reference point.
I do believe that static typing is at least a local optimum, but I am still not entirely convinced. Rich Hickey is a very convincing presenter and I can’t help but think that he is on to something — with Clojure the chosen direction is contract-typing, which is basically a set of pre- and post-conditions for your functions that are evaluated at runtime. Sure, it has a cost and in the extremes they are pretty much the same as dependent types, but I think it is an interesting direction — why should my function be overly strict in accepting a “record” of only these fields?
thanks for using Leebra!
go to feed...