This looks awesome, unfortunately my attempts to use it result in showing some kind of placeholder blue image with a yellow and black corner, despite it appearing correctly in the list of available widgets. Hopefully that gets fixed soon.
I should add that to the docs. I have seen changes in Gists take a few minutes to propagate fully. The widget fetching outside the app is a little more sensitive since iOS budgets widget updates. Glad you got it figured out!
I worked on an ad attribution service for a AAA games company and sold my soul in the process. It was neat maintaining a service that had 130m+ hits a day though, never had to deal with scaling like that since. Even neater was it was just two instances in production. Vertical scaling all the way!
Yup. 10 commits, first commit was just 4 days ago. Same with their public website & docs. On Github, it's all barely 4 days old.
Brian Lovin has released his work under the MIT license. AFAIK I believe this leaves it open to others to take the code and just run with it.
Even so, looking at their value proposition, it's just a landing page that leads to https://nymhq.com/join where you can subscribe to a "waiting list" to join a server. They claim "Nym is currently in private beta with limited servers, but is accepting waitlist requests now."
The "showcase" on the front page are just content fodder (AI? Web 2/3/5?) with quick, unstyled instances of their blogging software. The rest of that landing page seems to contain a lot of fluff as well.
Frankly, I'm extremely apprehensive about supporting this.
I found graphics programming impenetrable until I found https://learnopengl.com. Going through the articles there was enough for me to feel comfortable working in all the other graphics APIs, even Vulkan.
Personally, I don't like the use of indexing to determine the JSON structure (like this `<input name="foo[0][1]">`). I think it's way more powerful to derive the JSON structure from the DOM tree. That's why I wrote some code to do exactly that: https://gist.github.com/mjepronk/5b33eaa90ecf11a5c2c47935a2c...
The use of `<fieldset>` and `<section>` may not be the best choice. You could use `data-` attributes on arbitrary tags for instance.
As someone who doesn't follow the standardization process, I would love an explanation how proposals like this fail even when they have widespread support and no downsides. Is there an easy answer to this or is it different from case to case?
From what I've seen, standards need to be picked up by browser vendors for them to become established.
Usually one vendor will implement it behind a flag, and if it gains traction then other vendors will follow suit before it becomes a generally available feature.
I've noticed it puts people on the defensive when I put 'just' in a sentence, even though I have no intent to disparage others with my words, so I make an effort to avoid using that word at all in any business setting. I've found it goes over much better when framing suggestions as 'Maybe you could try..." than 'Just do...'.
I've set up a Legacy Contact with my Apple ID, since that provides access to all of my data, with a close friend in the event of my death. It was fairly easy to set everything up and I just had to provide their email address and send them a document produced after the setup was complete.
It's definitely given me peace of mind, as I wouldn't want them to be in a situation where my entire digital life was lost to them. They would also then be able to close all of my accounts and notify others of my passing.
I never much point in them as a kid. I'm left handed and I found it harder to use left handed scissors in my left hand than using right handed scissors in my right hand.
