Hacker Newsnew | past | comments | ask | show | jobs | submit | sto_hristo's commentslogin

First you have to know what you're actually up against. It's not a particular human behavior that is to blame, but stupidity itself. Some people are total morons and the behavior you're complaining against is merely a consequence of that. You can't defeat stupidity, it's a nature thing.

You can suppress it though. Public shaming, forced fines, get violent with them... All these things work to certain degree and will get you through the day. But again - you're not solving the problem, you're just suppressing. Stupidity is ultimately unsolvable, because nature; and that is why all those utopic dreams always fail with impressive death counts.


Anything social that tech enabled has become so toxic and damaging to normal f**ing human beings that i kinda wish governments step up and go full autocratic on these sites and services.

This stuff is 21st century digital bubonic plague. Revert life to the 90s and 80s snapshot.


Restricted OS like Android. Awesome hardware has been dumbed down to a pathetic handheld console, turning you into a brainless ad clicking zombie.


I wonder, is public WCs (like in the office) a potent vector for this disease?


I've seen seemingly immortal tech giants die to the newcomer, but MS's office is just too ubiquitous and embedded everywhere. So even if there's a superior excel alternative, who would use it when they already have Excel along with tons of other office tools.


Thing about JSON is the ease of reading and writing it, regardless the size of the document. Compression deals with the rest.


It may be easy to read and write, but few libraries implement it to the letter because the format doesn’t support extremely common use cases.

For those who disagree, try finding a json library that can reliably round-trip the data in a json file (i.e. ignoring spacing, tabs, and extra line breaks)

Common breaking points are discrimination between integers and doubles (e.g read 0.0 and write 0) and limits to the number of digits in a number.

It’s futile to try and change it now, but I think json would have been better if it had disjunct sets of integers and floats, did 64-bit ints (1) and IEEE doubles (1) as opposed to arbitrary length integers and floats, standardized serialization of time stamps and durations.

Requiring parsers to keep keys in file order also might have been a good thing.

(1) I know that opens a rat’s nest of users wanting unsigned 64-bit integers, signed 16-bit, 128-bit quad floats, etc, but I don’t see how not addressing that problem at all is better than picking reasonable values, event though that gives up on supporting those alternatives. Now, we have libraries making choices there, hopefullly in compatible ways.


I'm not sure what to make of this as .NET is "competitor" of Jakarta EE. In quotes, because who really would prefer that to Jakarta EE/Spring...


Isn't everything produced for mass appeal algorithmic? They even have a tropes wiki. And i'd take that any day over the arthouse originals the Elevated folks spawn.

At the end it's economics that dictate what goes out hand or not.


So you're an authority on adults and proper things to watch? Link me to the codex, must read it.


I wished Uber succeeded in my country. And by "succeeding" i mean being allowed to enter the market. Can't stand taxis.


Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

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

Search: