> Disregarding a law that was passed by a bipartisan majority, signed into law by the president and ruled on by the supreme courts feels like the start of a very dangerous path
The very dangerous path started a long time ago, or at least that's how it feels from abroad. "He can't" followed by "He wouldn't" then "He did".
IMHO this is the reason things should be laws not weird tradition and conventions if they really matter, (same reason that the fault of things like SCOTUS upturning Roe v Wade is in Congress for never making it a law instead of just a precedent
> Would it be possible to render retro pixel art from a simple 3D model?
Not exactly retro pixel art, or maybe it is since it's been 25 years (omfg) but in Commandos 2+ we had 3d models for the characters, vehicles, etc which we rendered at runtime to a 2d sprite which we then mixed with the rest of the pre-rendered 2d sprites and backgrounds.
But this wasn't about trying to help someone to be better, it was to help them avoid facing consequences for being bad, like advising a wife beater about concealer options for his wife (overly dramatic example, I know).
"You should stop doing dumb/illegal stuff, it might impact you" is very different advice than "You should stop talking about the dumb/illegal stuff you do, they may stop you".
TOML, extensions of json like json5 and hjson, a bunch of lesser known formats for nested structures like NestedText, UCL, kdl, Eno,sdlang, eldf, etc.
Also languages with some progrommatic capabilities like cue, dhall, jsonnet, nickel etc.
Non of them are perfect, and some are less suitable for certain use cases than others. But IMO pretty much all of them are better for human editing than json, and in many cases yaml.
JSON has a very minimal set of types and I regularly use all of them. I guess you could argue that integers and numbers could be combined, but I think that's it.
I can't put much faith in any technical promise from GOG.
My GOG account broke somehow almost 10 years ago, and over the years and several attempts they have been unable to recover it. They can't even establish why it's broken or what games I owned or if the whole thing has been irrecoverably lost.
> it will become far less obvious that their comments should be downgraded.
I'm curious why you think this would happen... I would imagine that their comments will now have be to about things that matter, and if they are unhelpful they will stand out more.
It is obvious that a style comment is of no significance, and that the person who made it chose to spend time and personal capital on something of no significance.
It is not obvious that an actual code change is of poor quality.
To show that takes infinitely more experience, work to analyse all the direct and indirect ramifications of both the original and proposed approaches, capacity to push back and decide that your own engineering judgement is equal or better than whoever is purporting to correct you, willingness to suffer everyone else accusing you of arrogance for that on top.
Even with all of that, it's a lot harder to prove the valueless comment is valueless because the more you know, the more you know that practically every single line of code could be done 30 other ways with some valid argument for each one.
It's completely insidious both for the junior and the senior.
The junior has no way to know the junk comment is junk. So they internalize the comment and everyone is worse for it.
The senior has it almost worse. They know enough to know they don't know everything and the comment might be valid, so they put in all kinds of work to try to figure out if they actually missed something, did they have point etc. Maybe in the end the code doesn't end up as bad as the junior just rolling over, but it sucked for everyone and the challenge was not really an intentional productive crucible, it was just a douche that everyone had to waste time and energy taking seriously.
Only someone who actually is arrogant (whatever level, whichever side of the pr) has it easy. Again bad for everyone except them maybe.
If the seniors are too passive to say no faster and faster, and management is absent, the junior’s going to end up being the tech lead. I’ve seen this. :)
It’s not necessarily even bad if there is no meaningful leadership above or alongside the junior. The fast-rising junior may end up hiring developers who are more assertive and still capable.
But you see the contrast between "you are a valuable and well-compensated knowledge worker" and "you have to move somewhere more appropriate for your working-class income"? And how can anyone continue to say this is lucrative with a straight face?
Another department store squatter here along with my brother. It was crazy to think this is how we learned to program, but it made sense at the time. We went for the ZX Spectrum and eventually wrote our first commercial game for it [1] with the rubber keyboard, it never bothered me.
The very dangerous path started a long time ago, or at least that's how it feels from abroad. "He can't" followed by "He wouldn't" then "He did".