Did I miss something recent? Or are we going back to the DES days?
While not exactly recent, I think most people have Dual_EC_DRBG in mind these days when it comes to NIST and backdoors
Readit NewsGoogle photos removed the delete api endpoint. Now, in order to delete your own photos from their service, you have to automate browser interactions that batch by batch delete your photos. I've just done this with both my wife's and my google photos accounts, and it took over 24 hours of browser interactions to fully delete everything. Ridiculous.
On a tangent, I don’t understand how Apple’s App Store allows the Google Photos app to insist on being given access to all photos on your device rather than selected photos to even work (even just to view photos shared elsewhere). Seems like an obvious violation of privacy and terms around not requiring unnecessary permissions. I think the app should be banned until they provide an option to gracefully respect users’ privacy settings rather than holding unrelated features hostage if they don’t get to spy on every photo on your device.
The web is UTF-16 ? WTF
not just UTF-16 but potentially malformed UTF-16 (supporting invalid surrogate pairs or surrogate halves and with js string functions computing things like lengths independently of UTF-16 characters)
This is also widely known as WTF-16 (seriously, look it up!)
> That died last week, when the U.S. Court of Appeals for the District of Columbia dismissed the suit for lack of jurisdiction.
If the issue is one of jurisdiction, did they file the case in the wrong court?
Following local news, I've seen the case where a case is closed because it was filed in the wrong court. A different court had jurisdiction in the matter. I wonder if that's what happened in this case.
If you read the judgement it basically says that because the FBI eventually returned the money, she no longer has a live interest as an individual.
They also denied that she’s part of some well defined class for a class action. It’s not like they are saying there’s some other court she can go to.
US courts are generally infamous for denying justice whenever they see fit using technicalities like “standing” and other procedural grounds.
Environmental law violations, illegal surveillance programs, civil asset forfeiture like here, and constitutional violations are quite often practically impossible to get courts to address, especially if parts of the US government are the defendant.
0xfffafaCrash commented on I like Svelte more than React (it's store management) river.berlin/blog/why-i-l... · Posted by u/adityashankar
Never heard of Signals[1] until now, thanks. But it makes me nervous with how much influence it has from React and Vue, and the way React and Vue do things. These are not the be all end all methods of reactivity, and I can't help but think if there's going to be an official language feature implemented for this, there needs to be room for other voices to be heard that have zero influence from React/Vue. Maybe there's still time since it's Stage 1.
I wouldn’t say signals is coming from React. If anything React is the latest to the party and being dragged there reluctantly by where the tech community is going. They’ve mostly been resisting the movement towards signals because it undermines a lot of the arguments they have made for their virtual dom, synthetic event system, and rerender all the things dogma. Solidjs is much much more in the signals camp. Angular, Vue, Svelte, etc also recognize the need for this sort of reactivity.
React could be argued to have abandoned the fight for being the best client side framework technically (though they have dominance pragmatically). They are really all focused on Vercel’s Nextjs/SSR/SSG/RSC stuff in recent years
0xfffafaCrash commented on I like Svelte more than React (it's store management) river.berlin/blog/why-i-l... · Posted by u/adityashankar
Most UIs I've written in my career benefit from being modeled as FSMs. While I see the value proposition of the atom-based approaches, especially for basic applications, I can't help but become a bit hesitant about their scalability long-term on large teams. Part of the reason the very dogmatic Redux approach of a event dispatching + single store of truth caught on so quickly was because a lot of us had felt the pain of two-way data binding / global state with event listeners in Angular 1. I distinctly remember the horror of debugging digest loops (scope.$$phase memories) and being completely lost in the unstructured data flow. What made for a great demo became a nightmare at scale.
There's nothing stopping people from using these atom-based libraries to build more robust abstractions, but from my professional experience I tend to just see global getters and setters with useEffects / lifecycle method of your frameworks choice as a side effect sync.
Maybe my instincts are off here though and I am overly cautious. I love XState but the learning curve is rather massive and getting buy in from other team members is hard when the DX of the atom approach is so nice.
I feel like state "management" and reactivity performance are talked about a lot, when ultimately state orchestration is where I see things fall over the most.
I haven’t ever seen issues scaling with jotai even on very large apps working with extremely complex data structures.
I’ve seen far larger messes created in redux due to tight coupling of things across large apps to a global store and the inability to work with things like Maps and Sets or other values that are not trivially JSON serializable.
In the other direction I have seen messes with observable-based state management systems where things become far more complex and too far abstracted (how often do you really care about anything other than the latest value and maybe the previous one?) or with proxy based systems that have too much fragile magic (valtio, mobx) or require wrapping your components and going all in on oop (mobx)
To me signals hit the magic spot of reactive without being overkill and keep code testable in smaller units while retaining performance benefits of surgical updates
I like xstate in theory — it’s a good way to think about complex state transitions — but in at least half of cases in practice where you aren’t interested in a derived value, someone is storing a value/ getting the latest value or toggling a boolean and it’s just such overkill for that. The reducer pattern itself doesn’t meaningfully show up much for similar reasons. The other common cases are with fetching states (idle, loading, refetching, success, error) but you often end up wanting things like cache management or maybe even optimistic updates so eventually tanstack query covers that ground better than rolling your own.
0xfffafaCrash commented on I like Svelte more than React (it's store management) river.berlin/blog/why-i-l... · Posted by u/adityashankar
React doesn’t really concern itself with state management. Of course it has context, state, and props but the mental model for it predates focus on fine grained reactivity in frontends — useSyncExternalStore helps enable others to fill that void in v17+. Fine grained reactivity was notably also missed in the development of web components — only now is there a tc39 proposal for signals (in its early stages).
Jotai, mentioned briefly in the article, may not be built in but is as intuitive as signals get and isn’t even tied to React as of later versions.
I’ve very rarely met a state management problem in clientside state management where neither tanstack query (for io related state) nor jotai (for everything else) are the best answer technically speaking. The rare exceptions are usually best served by xstate if you want to model things with FSMs or with zustand if you actually need a reducer pattern. There’s a tiny niche where redux makes sense (you want to log all state transitions or use rewind or are heavily leaning on its devtools) but it was the first to get popular and retains relevance due to the fact that everyone has used it.
You can go a long way with useContext and useReducer/useState but few would opt for alternatives if jotai came batteries included with react.
0xfffafaCrash commented on Triangle splatting: radiance fields represented by triangles trianglesplatting.github.... · Posted by u/ath92
Can someone explain what a splat is? I did graphics programming 25 years ago, but haven't touched it since. I don't think I've ever heard this word before.
A splat is basically a point in a point cloud. But instead of a gaussian splat being just a point it isn’t infinitesimally small but like a 3d gaussian where the point represent the mean. It also has color and opacity. You can also stretch it like an ellipsoid instead of having it have perfect radial symmetry.
0xfffafaCrash commented on Getting a paper accepted maxwellforbes.com/posts/h... · Posted by u/stefanpie
This is an article about ML research, and the emphasis on branding and marketing your paper wouldn't fly in any of the fields people think of as scientific. Could you imagine someone saying, "be sure that the graphic for the molecule in figure 1 is 3D and has bright colors?"
The most disturbing thing about it is the way advice to forget about science and optimize for the process is mixed with standard tips for good communication. It shows that the community is so far gone that they don't see the difference.
If anyone needs a point of reference, just look at an algorithms and data structures journal to see what life is like with a typical rather than extreme level of problems.
Strongly disagree here. While I haven’t published e.g. particle physics work, I have authored/coauthored a number of peer-reviewed papers in other topics generally considered hard science (and published in ”high impact factor” scientific journals). This article and series is just as accurate about how ”Science 2” works outside of ML in my experiences. Branding and marketing is a very major factor in everything from grant funding to research publishing in academia.
https://github.com/tc39/proposal-pipeline-operator
It would make it possible to have far more code written in the way you’d want to write it