Can someone explain to me what is so special here? It seems to be just a simple binary abstract syntax tree, which with varying syntax can represented by almost any programming language
it seems to be optimized for dry walls. not sure how it would perform on concrete or other stone walls. Also I could not find a technical description how it works.
why should it be any different on mars than on earth?
> This show has a cool premise, that being what if the space race never ended. It's a sort-of alternate reality and it does a good job of weaving in actual historical events with where the timeline diverged. The main problem is that I feel like the show is being pulled in two directions. In one direction, there is the tension of the space race, engineers scrambling to be the first on the moon/mars and dealing with all manner of technical issues in a realistic-ish way. That part of the show I enjoy. Then, for some reason, the show also throws in a bunch of trite interpersonal drama and stupidity. Like inter-marital affairs, people leaking NASA secrets to the soviets, and a CLEARLY unstable drug-addicted astronaut being given solo control of a super important mission. It's like the showrunners thought the show couldn't stand on it's own without dumb drama, as if there couldn't organically be issues and drama in the context of Frigging SPACE. The first season does this better, but by the 2nd/3rd seasons most of the issues come not from unforeseen difficulties of life on the moon/mars but idiots. It really makes me wonder if they just aren't sure who their audience are. The people who like the technical stuff are not going to like the artificial drama, and vise-versa. Pick a lane, show, and stick with it.
I would argue that sometimes "dumb drama" is a good mirror of humanity. Inter-marital affairs really do happen (including in the highest levels of public policy as well as the astronaut corps), people do disclose "secrets" and pilots (including astronauts) are known to deceive medical professionals to avoid being "grounded".
My other favorite example of dumb drama at the highest levels: ex-director of the CIA, David Petraeus, was forced to resign after being caught by the FIB in an extramarital affair with his biographer. [1] You'd certainly think that the ex-military head of a spycraft organization would know to be a little more disciplined... and less vulnerable to blackmail.
The drama isn’t even done that well. Like you say, it’s stupid; the people are on average just worse than the sort of people who would actually be there.
I wanted the technical sci-fi to be worth it, but it wasn’t. There really isn’t much catering to an engineer audience.
As somebody who has spent a lot of time with high-quality academically pedigreed humans in far out places, I assure you that they're very capable of dumb drama. And, again tho I hated the show, everyone will be watching just as they were in for all man kind.
> The people who like the technical stuff are not going to like the artificial drama, and vise-versa. Pick a lane, show, and stick with it.
I like the show as-is. Maybe I'm not in love with every single subplot but in general the show is pretty great. IRL people have motivations that drive them to do greedy, irresponsible things -- even astronauts.
I find working with React and Mobx a breeze, also for complex apps. Not sure, why this has not been more widely adopted. It eliminates usually the need to use those mentioned unintuitive and error prone state handling mechanisms.
I optimized Mobx away by switching to "zustand" – it's another layer of simplification and I haven't had a project where it didn't work. Next to zero dependencies and it just "works". Mobx got me angry once they had too many breaking changes from 4 to 5 etc.
So much this. It's a perfect match for React. Let's you keep data/logic out of the components, 0 boilerplate, optimized renders (similar to what react compiler will do...).
You can even use tanstack-query to get all/most of its benefits. (by using its core package instead of react-query)
Yeah. I think mobx is often disregarded as mutable state goes against the react philosophy. Instead they somehow rather make monstrosities of codebases (redux anyone?) just to avoid it.
And mobx is really just signals everyone now loves automated via proxy objects.
My first real job was at FAANG with 2 co-technical leads with 0 reports and 3 people working with them.
They were iOS-specific, and called in to lead (and I was hired) after a sprint where not-iOS people had built an iOS app. It was pretty good!
The problem was, their heads had inflated so much that they had ascended to the heavens in terms of self-proclaimed computer scientist.
So they wasted months and months rewriting the app to have a Redux implementation in Objective-C, 4 years after Swift came out, and pitched it as a final solution to making the app reliable and dev velocity fast, as compared to that horrid codebase they had to inherit.
The relaunched app took 18 months, was missing features, had a 2/3 higher crash rate. And the core problem, network reliability, came down to them acting like the networking code was some prized expert-level thing only they could manage...but the issue was they re-implemented TCP and were blocking ACK packets on frame rendering. So it'd be really fast and normal then hit the ack queue limit, and only be able to send one packet every ~16 ms.
Just thinking out loud because it's very funny to find out Redux also ended up being too much in the JS community, and I hadn't heard till now.
But hey, our managers managers manager really liked that one video of that one stilted live replay the initial 6 months in demo could do.
they are more like star clusters than galaxies. Galaxies usually have a lot of mostly circular momentum with arms forming etc.
might be even the better marketing term "Software star clusters"
not to mention the widely accepted hypothesis that galaxies require dark matter to be held together... we don't want to dive into the analogy here for software, or do we? ;-)
It was announced after the end of Leap was proclaimed, again feeding suspicion that Leap 16 is meant to save some goodwill rather than part of a solid plan of supporting users.
It all looks opportunistic, the total opposite of what users of such distros expect. You can built out your use of it at your peril.
I got a lot of unhappy feedback from SUSE for it, but they did not deliver solid tech info I asked for, even given 2 days to do so.
TL;DR summary: they're focussing on immutable distros now, but unlike rival efforts such as Endless (Debian + OStree) or immutable Fedora (OStree all the way down) or Ubuntu Core (Snap all the way down), SUSE implemented transactional packaging using Btrfs snapshots and plain old RPM.
So, underneath, it's structured pretty much the same as conventional SUSE. That means you can turn the immutability function off, if desired, and be left with something quite conventional.
