Am I the only one that thinks the vanilla js example is actually easier to read and work with?
- "The setup is noise and boilerplate heavy." Actually the signals example looks just as noisy and boilerplate heavy to me. And it introduces new boilerplate concepts which are hard for beginners to understand.
- "If the counter changes but parity does not (e.g. counter goes from 2 to 4), then we do unnecessary computation of the parity and unnecessary rendering." - Sounds like they want premature memoization.
- "What if another part of our UI just wants to render when the counter updates?" Then I agree the strawman example is probably not what you want. At that point you might want to handle the state using signals, event handling, central state store (e.g. redux-like tools), or some other method. I think this is also what they meant by "The counter state is tightly coupled to the rendering system."? Some of this document feels a little repetitive.
- "What if another part of our UI is dependent on isEven or parity alone?" Sure, you could change your entire approach because of this if that's a really central part of your app, but most often it's not. And "The render function, which is only dependent on parity must instead "know" that it actually needs to subscribe to counter." is often not an unreasonable obligation. I mean, that's one of the nice things about pure computed functions- it's easy to spot their inputs.
I am not sure what the fuss is about, honestly. Elon didn't storm off the set, he answered all the questions asked, Don seemed to pick up on some negative vibes but of course he would since they're having an intense discussion where there were several points at which they had to simply disagree and move to the next subject.
Don irritated the guy who invited him into a partnership and then that partnership was rescinded. Don himself prefaces the clip by saying his show wasn't cancelled by X. Seems pretty in line with what Elon said in the interview about how everyone's free to post, but that doesn't mean X will promote it. X decided not to promote Don Lemon's show.
When I shopped for a new watch two years ago, I was looking for a simple non-smart, easy to use, robust watch that didn't have a ton of features. I ended up getting a Freestyle watch and I have been very satisfied with it.
It tells the time and tells me time elapsed, the light isn't obnoxiously bright at night, I'm not fiddling with the interface, I'm not getting pinged, my data isn't being collected, I'm not afraid of breaking it or soaking it, I'm not charging it.
I agree, Java is wordy, ritualistic, and prone to overcomplication. Build/run/write loops are slow and painful, and frameworks and toolkits try to do so much that they inevitably get in the way.
Well, it's written in the opinion section in newsweek. Also, there are quite a few links throughout the article, but they may be easy to miss because the only indication they are links are the red line underneath, otherwise it looks like regular text.
I personally thought it was well-written, and I find it relieving to hear someone admit the many flaws in the execution of the covid response.
For those interested in some good history of the punk movement in East Berlin, I recommend the book Burning Down the Haus by Tom Mohr. Really gives a window into the courage, creativity, and motivation of the youth, and their oppression by the Stasi.
While I agree that's a big part of the problem that needs to be solved. I don't think any one thing is going to tackle such a complex multi-faceted issue. For example the book Evicted by Matthew Desmond was a good read and told the story of some families on the edge of homelessness, facing eviction due to various reasons such as drug addiction, low income, etc. These problems won't go away with addressing housing regulations, although more affordable housing availability could certainly help.
You can get a good grasp of the size and complexity of HMIS data by perusing the HUD's HMIS Data Dictionary [0]. It shows the business objects and their fields, allowing you to get a rough ERD-like idea of how the HUD views HMIS data. Many HMIS systems, from what I've heard and seen (I've only done a little work in the space), don't use this as a data model internally though or if they do it's not exposed that way through their APIs if they even have APIs that they're willing to let you use. Presumably though, they must have to report it that way to the HUD for funding.
I agree, it would be great to have a fresh, pragmatic take on this data, and I'll be reading more about that Built for Zero framework.
One Center of Care (CoC) I talked to talked about their old HMIS system from a private company who charged something like $70K/yr (iirc) to keep using their software. That seemed excessive to me, but they didn't seem to mind too much. Migrating off would have been extremely difficult anyway. Their bigger stated need was the ability to easily send data from their system to other CoC systems in the area as the people they were helping moved around or were transferred to more relevant services. Each time those people encountered another CoC, basically the intake process would have to be started over again at the new location, which was a drain on both the receivers and givers of services.
We tried a couple attempts at making a sort of hub for pulling and pushing data to the various systems, but only one entry system company was very supportive, while we had to tread carefully around some of the HMIS system makers who seemed very protective and unwilling to expose or share their APIs if they had any. One big challenge was finding a single unique identifier for each person across systems, which is why a local by-name list like the article mentions is very intriguing.
"The latest conditions on mountain bike and hiking trails are being shared inside communities like Reddit but not on the web."
I just wanted to mention that a friend of mine made an app for user-reported trail conditions that might be worth taking a look at:
https://trekko.app/
I wonder how much time has been wasted by devs who get the order wrong. I know I've been guilty of it so many times. It's really frustrating, but I like that someone took the time to write down which order goes for which software- this is a nice reference.
We stayed in the basement after the sirens started, and followed it on the weather radar. We got notifications on the phone, and kids were dismissed from evening activities early. Pretty rare to get this type of weather this time of year.
I use it pretty heavily for node.js apps. Every time I see the newest Rube Goldberg contraption for deploying code, my first thought is trying to figure out why they didn't do something simpler, like Heroku.
Being comfortable with complexity isn't a good excuse for making things more complex than they need to be.
This is really neat! It's like having a video with selectable, inspectable text/markup. I also love how there's no sign-up needed. Thanks for making this freely available.
This is the kind of thing that I love about the internet: it opens up new opportunities for open, collaborative, creative expression.
This looks like it's well-executed too. I like the minimal, elegant design. Good idea on the links as unobtrusive arrows that are still informative as to whether it's linked from/to.
- "The setup is noise and boilerplate heavy." Actually the signals example looks just as noisy and boilerplate heavy to me. And it introduces new boilerplate concepts which are hard for beginners to understand.
- "If the counter changes but parity does not (e.g. counter goes from 2 to 4), then we do unnecessary computation of the parity and unnecessary rendering." - Sounds like they want premature memoization.
- "What if another part of our UI just wants to render when the counter updates?" Then I agree the strawman example is probably not what you want. At that point you might want to handle the state using signals, event handling, central state store (e.g. redux-like tools), or some other method. I think this is also what they meant by "The counter state is tightly coupled to the rendering system."? Some of this document feels a little repetitive.
- "What if another part of our UI is dependent on isEven or parity alone?" Sure, you could change your entire approach because of this if that's a really central part of your app, but most often it's not. And "The render function, which is only dependent on parity must instead "know" that it actually needs to subscribe to counter." is often not an unreasonable obligation. I mean, that's one of the nice things about pure computed functions- it's easy to spot their inputs.