> Floating point is deterministic, what are you talking about?
Order of operations can change a result, for example. I suspect you mean that the algorithm never changes. While op means that mathematical operations which most folks would expect to be reliable are not.
There are enough problems for a 44 page paper titled "What Every Computer Scientist Should Know About Floating-Point Arithmetic"[1] I don't quibble on the language because I know what people mean.
Most folks won't encounter most of the issues, generally. But expose your code to a large enough dataset, or be like me and write a CAD/CAM system with motion control and experience most of them.
It's an infinite precision exact constructive real with excellent performance characteristics and approximation only at explicitly named lossy export functions.
... checks math ... Starship should have enough cargo capacity for this. One launch. We could put the whole senate up there. The house might take a couple launches unless we really pack 'em in. /s
We just need to setup a fake corporate sponsor meet and greet. We camouflage Ship to look like a hotel ball room, with a door for "private meetings" that leads to the cargo bay.
Not just mass optimization either. Intense effort and cost are expended through verification because a single payload simply must work. But using commodity hardware with reduced verification effort, launching many, and tolerating some amount of attrition has resulted in reduced costs for Starlink.
Testing of using commodity parts was part of the Mars helicopter and it worked well enough that making many of them seems plausible. I'd love to see multiple drones flying faster/further than rovers. Just not really sure what instruments would make them useful.
That's another great example. And ridesharing on the mission allowed them to prove it very inexpensively and with much lower risk than a dedicated mission.
I think the question of technical possibility answers differently from the question of organizational feasibility. Starlink is optimizing costs because they have a financial incentive to do so. The less each satellite costs, and costs to maintain, the more income they make. I fear incentives are not so direct in governmental orgs. Outside contractors performing most of the work have outsized influence, and incentive to inflate costs. Budgetary decision makers all want to see investment in their own districts.
I think Starlink and cubesats have definitely proven the approach can reduce costs.
The engineering does not seem as challenging to me as figuring out how to get such a policy approved and pushed through all the administrative and decision making layers without watering down and budgetary inflation.
Maybe if we launched 30 Starships carrying 30 rovers each. With only 30 units, the prices would likely be similar to current commercial satellites, which are already built on standardized platforms.
I'd go even more radically low cost, and kit the first lander out with wifi, and a half dozen each of every commercially available robot dog, humanoid, and wheeled or tracked robot of any interest. Rumble in the Mars Robodome. Bit of publicity for the existing manufacturers who may be willing to pay for the privilege, and who will undoubtedly learn valuable things about how their designs fail and can be improved. And you figure out in one stroke if there's a COTS platform you can buy for $30k that gets you 80% of what you need. If any of them function for any period of time, you use them to prepare the space for future landings. Rinse, repeat. After a few iterations, you have a half dozen manufacturers with commercially produced platforms with a few strategic modifications to which you can bolt your science instruments.
All I can think about now is a bunch of e-waste littering Mars. At some point, other visitors will show up to investigate Mars and come to the conclusion that the Earthlings are just so trashy their trash even started filling another planet.
The surface of mars is roughly the size of Earth's dry landmass. They'd have to spend quite a lot of effort looking for it to find it. And at that point it'd probably look more like a treasure trove of useful thermoplastics, refined metals, magnets, and other useful things otherwise difficult or expensive to source on Mars directly.
I'm not BoingBoomTschak who you're replying to, but he's right. My experience comes mostly from decades of reading xiph.org and ffmpeg mailing lists where such things are discussed, rather than implementing them myself. But there is constant discussion of encoder performance / quality trade-offs in software and hardware encoders. Hardware encoders, especially ones attempting to meet strict performance targets, simply cannot take advantage of some of the most complex quality improvements as they depend on information only present in past/future frames. Sometimes as many as 30 frames away.
It seems like you are interpreting this as a slight against the quality of Apple's hardware encoders, which may legitimately be very good. As are Nvidia's, Intel's and AMD's. But all of them will produce larger file sizes and lower quality than equivalently optimized non-realtime software encoders, which simply have more information and more time, memory, and flexibility to compute over it.
We're talking about fundamental properties of compression and computational time/space trade-offs. Even Apple can't design around them.
That doesn't mean Apple's hardware encoder is in any way bad or unusable. All lossy compression will be imperfect, yet much of it is useful. And most modern codecs and encoders seem to be capable of high quality results. The implications of the differences under discussion are percentages of a bitrate or tiny nearly imperceptible artifacts or breadth of available resolutions, refresh rates, and color modes or codec choice. Software encoders are always at the bleeding edge of what's possible. Hardware encoders are necessarily a snapshot frozen in silicon with limitations imposed by the implementation. The middle ground is largely already occupied by SIMD and other transform-specific ISA extensions already present in most CPUs.
> I've never enjoyed languages that plant a flag on one mechanism and force users to adapt.
Well, the hardware designers have chosen one (or at most a small number of) mechanism[s] and implemented in silicon. The farther you diverge from their implementations, in terms of abstractions, language features, and the like, the more you will pay in performance. Your choice.
Not op, but that's a very interesting proposition. While the law and legal code are technically property of the people, I'm not aware of any single point of download for it all.
There’s no single point of download for it all because there’s thousands of autonomous entities that issue law and adjudicate cases, at least 51 of them distinct sovereign entities.
We could enforce (suggest?) a common format / api at the federal level. Especially if it’s incentivized with funding that more than justifies the cost of maintenance. Similar to how federal interstate funding is only available to states with a 21+ drinking age.
Yeah, going to the courts and municipal code seems like it's going to be a heavy lift. Many of them seem to hang off of municode, though, so maybe it's not a huge number of unique crawlers.
There is none, not for statutes and definitely not for case law; even at the appellate level where you have multiple federal circuits, then 50 states, then territories, military, tribal and a whole host of other niche courts. And the appellate court systems can be split into districts, and by lower and higher levels.
Then if you want to really get into it, The People should also be able to access trial court level, and at that point you have over 3000 distinct court systems with their own access systems, usually requiring logins and CAPTCHAs, and half of them not even having anything accessible online at all, and the other half only having recent stuff online and the rest rotting in a flooded basement.
That’s awesome! I especially like RECAP as a method for freeing things from PACER.
Seems like you all are already doing a lot of what I’ve been aiming for with mine. Are there useful ways to contribute, or have you all gotten it to a pretty good place technically, and it’s mostly a matter of spreading it at this point?
No no the invisible hand of the market will fix it, you see. Car manufactures will become so big and pay so many taxes that we could pave every road with rail.
Wow I wonder how much of that differential is them operating at an extreme loss, and how much is the relative cost of their new models vs old. If a significant portion of that is net losses, I'm very concerned for their business model :|
Order of operations can change a result, for example. I suspect you mean that the algorithm never changes. While op means that mathematical operations which most folks would expect to be reliable are not.
reply