It's a pretty sensible policy, really. Corollary to Hyrum's Law - do not permit your API to have any behaviours, useful or otherwise, which someone might depend on but which aren't part of your design goals. For programmers in particular, who are sodding munchkins and cannot be trusted not to do something clever but unintended just because it solves a problem for them, that means aggressively hamstringing everything.

A flathead screwdriver should bend like rubber if someone tries to use it as a prybar.

JSON is used as config files and static resources all the time. These type of files really need comments. Preventing comments in JSON is punishing the wide majority to prevent a small minority from doing something stupid. But stupid gonna stupid, it's just condescending from Mister JSON to think he can do anything about it.

> A flathead screwdriver should bend like rubber if someone tries to use it as a prybar.

While I admire his design goals, people will just work around it in a pinch by adding a "comment" or "_comment" or "_comment_${random_uuid}", simply because they want to do the job they need.

If your screwdriver bends like a rubber when prying, damn it, I'll just put a screw next to it, so it thinks it is used for driving screws and thus behaves correctly.

And we wonder why people are calling for licensed professional software engineers.

On one hand, it has made json more ubiquitous due to it's frozen state. On another hand, it forces everyone to move to something else and fragments progress. It would be much easier for people to move to json 2.0 rather than having hundreds of json + x standards. Everyone is just reinventing json with their own little twist that I feel sad that we haven't standardized to a single solution that doesn't go super crazy like xml.

I don't disagree with the choice, but seeing how things turned out I can't just help but look at the greener grass on the other side.

"do not permit your API to have any behaviours, useful or otherwise, which someone might depend on but which aren't part of your design goals"

I can not follow this law by making my API depend, say, the contents of a string value. Preventing APIs depending on the value of a comment is no different, so your argument is not a reason for not having comments.

> A flathead screwdriver should bend like rubber if someone tries to use it as a prybar.

Better not let me near your JSON files then. I pound in wall anchors with the bottom of my drill if my hammer is not within arms reach.

16GB is _not_ sufficient if you have Jellyfin or Immich or similar and a lot of media you want to scroll through quickly; I've found I need a lot of ZFS cache for that to be as responsive as I want, even with SSD storage.

Straightforwardly, nobody with the resources to build and maintain a browser could ever be trusted to do so, as they get those resources from somewhere, and it's going to be somewhere unacceptable (ads, trackers, Google, taxes, selling the browser or addons/features as a product, hostile nation states).

These things are far too complex and expensive to be produced as they should and as most FOSS is: for free, by a group of individuals who could fit around a breakfast table and don't answer to anyone but each other.

I feel like you're trying to be sarky with the "#winWin", but genuinely yes. If the tradeoff is that someone gets to feel important and have a plaque put up with their name on it, and something good but expensive happens which otherwise could not, everyone absolutely does win. Even better than taxes because it's a specific goal and consensual on all sides.

The political issue with this statement is VERY real ! [this is definitely not democracy compatible, if you want my personal feeling]

ESP32-C6, and associated dev boards.

This factor (95% of "your audience" not being interested at the time) is the core of why all marketing is unavoidably scummy.

I don't want to hear about your product _ever_, except on the day I am looking for a product which provides the function your product does. On that day, I don't want to hear about it from you or anyone you have anything to do with; I want a list of products in that space, curated by an independent third party you have never spoken to and cannot influence in any way, with a clear featureset and upfront costs comparison table that does not have any variant on "talk to their sales team" anywhere near it.

Seagate have an Exos M in 36TB for about £450, so 24 of those could do it. Three vdevs with one parity drive each? Call the project £13k?

Not exactly a production grade setup, but it'd do the job and you'll see fewer failures each year than in 544 10k SAS drives.

This seems entirely sensible to me. If I was offered the choice between doubling my salary or keeping the same one but halving my days worked in a year I wouldn't consider the former for more than about half a second.

I am not sure about Netherlands, but in Germany there seems to be no such choice. Getting a higher salary is hard even if you are willing to work more. Freelancing is probably the only way, but freelancing contracts get cut first in the current downturn.

In the US everyone has a contract similar to what you consider freelance...

Relevant - and old enough that those five years have been successfully granted!

The AI's assessment of him seems somewhat apt, really, even if it doesn't know much about Notion.

@Xymist Interesting. You're proving my point perfectly.

When a human shows contempt for another human seeking help, that's unfortunate. When AI learns to replicate that contempt at $200/month, that's the problem I'm highlighting.

Thank you for demonstrating why we need AI that elevates human interaction, not one that amplifies our worst impulses.