161–170 of 211 posts
Earlier quoted context omitted.
> I enjoy using json5. I solves a real problem imo.. And what problem would that be?
Having a tolerable experience when forced to hand-write JSON?
Pray tell, which intolerable experience did you ever had writing JSON by hand?
Earlier quoted context omitted.
> Yes, but it’s a bit late for that. That just shows poor judgement on behalf of the developer who made that decision, not a failing of the language.
Right… and the fix is to switch from JSON to JSON5. I don’t see how assigning blame is productive here. People choose the wrong language, wrong library, or wrong tool all the time.
Not really. JSON offers no challenge in editing by hand. All comments I've seen in this thread boil down to people trying to pass off whimsical nice-to-haves as this sort of insurmountable problem.
I mean, I do like a nice git history with small diffs. Not supporting trailing commas is unfortunate as it can cause the trailing line to show up in diffs if you add a comma there. But is this a problem? No, it is not.
Let's be honest here: JSON5 solves no problem worth solving, at the expense of breaking compatibility.
I believe VSCode uses json5 with .json extension for a whole bunch of their configs.
It would be a slower parser than JSON though.
The only 2 things I'd like to add in JSON are trailing commas and comments, and this is already supported in most JSON configs (.eslintrc, .babelrc, ..), it's called JSONC I believe
Another name for this is JWCC. IMO very good argument for this feature set here: https://nigeltao.github.io/blog/2021/json-with-commas-commen...
The "Why not JSON5, JSONC #1, HJSON or HOCON instead?" answer says it's because of "unquoted strings", then links to a section that only talks about unquoted values. JSON5 doesn't have unquoted values.
Earlier quoted context omitted.
I think most companies do not set up mirrors. There is no way millions of individual companies are downloading daily the same pieces of code. And if they had caching they'd download them only when a new release happens, not daily. There aren't that many companies in the world basically.
You don't have to set up local mirrors. You can start the build with periodically-saved node_packages, or if you're using docker "ADD packages.json, RUN npm install", or commit vendored modules, or do one of thousand of other things. For some companies release just means another merge to master, so they are doing tens/hundreds releases a day. Once you do enough development that this matters, you're going to be doing…
Consider that for developers a slow build = break time. https://xkcd.com/303/
And just running npm or pip at every turn is easier than setting up all of that, so there needs to be a push to do it. And the server of those entities seem to be able to deal with the load.
In my first job we had autoscaling cloud servers that took 30-40 minutes to be operational. I told my boss we should have pre-created an image instead of installing and compiling dependencies when we started them. But he said it would not be agile.
Non-constructive criticism is extremely easy to produce and can make the author of it feel smart for a second. Doing it in a place where folks share their creative works is like shooting fish in a barrel. There may be a tiny bit of signal in such comments but it's mostly just noise. I try to just ignore any comment that looks like the commenter just wrote whatever came to their mind, they're gonna forget about it in…
Since this behavior is so common, apparently it works, evolutionary:
It makes others think your are smart, for a long while
And not much effort required, on your part. So, a great opportunity?
And the more popular the project you start bashing is, the smarter you'll seem? Corollary: If one builds something great, one will get dissed by some.
Earlier quoted context omitted.
Some people get paid in money and not exposure.
You may want to find other employment if your work requires an NDA that disallows any discussion of your work, or your future opportunities to get paid in money may be limited.
Earlier quoted context omitted.
Having a tolerable experience when forced to hand-write JSON?
> Having a tolerable experience when forced to hand-write JSON? Pray tell, which intolerable experience did you ever had writing JSON by hand?
Lack of multiline indentation-ignored strings.
Earlier quoted context omitted.
That's a terrible outlook. You are saying that all negative feedback should be ignored by everybody and treated as a positive sign. This is insane.
Nowhere, not once, did I say that all negative feedback should be ignored. I specifically stated "I have long held the belief that if the audience of Reddit or Twitter or Slashdot or Hackernews universally hates something with such vehemance that you doubt your own thoughts then you are probably doing the right thing." This is not "all negative feedback" or "that it should be ignored by everybody" or "treated as a po…
"If you've found something that arouses interest and debate, you might be on to something"
And critique, or a gathering of enemies, is interest in something
(interest in the stuff the enemies in the game are guarding)
I'll take any feedback. If someone tells me I'm dumb and have it wrong, I thank them and fix it. Now they can't complain about it, I learned something, and someone spent their time giving me free advice. But if they don't convince me I'm wrong, then I ignore them. :)
What if, though, they convince others that you're wrong -- so no one wants to use your software?
(although it would have been helpful to many)