Never seen WAI before, all I can come up with is Works As Intended or Web Accessibility Initiative?
Anyways- jail breaking requires being or remaining on certain iOS versions on certain specific hardware models. You can’t “just jailbreak” your apple device that you daily drive/use regularly. If you’re not on an old version on the right hardware already, you’re fucked. And waiting for a new jailbreak exploit is a (anecdotally, for me at least) nondeterministic amount of time on the order of O(years), with a significant probability that it will not be relevant for whatever device you’re waiting on.
This has to put them in the top 0.01% of companies that make consumer electronics.
I can think of only a few companies that bother to publish any details... And most of them are focused on industrial customers where it isn't unreasonable to need certain protocol details for integration or even just compliance with certain regulatory systems.
Maybe things are changing?
I have noticed that some of the LED light controllers you see on AliExpress are leaning in to open firmware standards. 5 years ago, you bought the controller and had to flash your own firmware. Now, there's an option at checkout to select an open source firmware. Some even have a USB port built in for flashing!
It really makes me wonder why it's not more common. They literally don't have to write any firmware, just use one of the thousands already available provided that the license allows for it
Is there a ‘right’ (or simple/direct) way to generate this using various buildchains? I remember setting this up so I could use Sublime with intellisense a while ago, and finding that I could only get it to generate with a specific compiler chain on windows (ninja I think?)
Minor annoyance to have to make my c make project generate buildchain files for a compiler I’m not using & copy that file into my project root to commit it- unrelated to the original question, but also annoying that I have to manually generate it every time I make significant codebase changes.
> and finding that I could only get it to generate with a specific compiler chain on windows (ninja I think?)
Yes, you're right about that.
Basically, it boils down to "use CMake with Ninja/Makefile" (even if you don't strictly have to, you could write a script that creates the json yourself, for example). When cross-compiling, you may also have to whitelist compiler paths.
Add -DCMAKE_EXPORT_COMPILE_COMMANDS=ON as command-line arg during the config step, or add the equivalent "set" call to your CMakeLists.txt, restart clangd (ctrl+p, restart clangd), and you're good to go.
There are minor annoyances when cross-compiling (it using clang -- some compile options are incompatible and need to be removed in global user config, and it not extracting default compiler defines from compilers) but they are very easily worked around
You acknowledge the existence of things blocking <something>, and can't imagine that there are people who want to see <something>?
I feel like when <something> is the sky, potential counterpoints can't be that far. For a direct response to your question: the sky and the stars beyond have been present and visible to every human, throughout all of history- how might different people feel about it becoming obstructed? Philosophically? Emotionally? Pragmatically?
The following types of people might feel strongly about this for some reason or another- I feel like steelmaning hypothetical opinions they might have is a really enriching thing to do.
- Photographers / enthusiasts
- Astronomers / enthusiasts
- Those who enjoy nature
I personally have a mixed opinion, probably leaning towards alignment with the above groups, but I can also steelman the thought processes of those who'd think this is cool or fascinating (because of course, it is!)
I'm not trying to convince you of something about the post subject here; The rhetorical questions above are not intended to be read as "how don't you understand this and agree with me", but instead "how/why did these potential viewpoints not find you?" The lack of mention of any other viewpoint comes off as almost poor-faith or naivete.
In the SWE community, people place a lot of emphasis on attempting to find solutions to a problem yourself first, before asking a question (and detailing what you've tried/explored already) to a community. With that mentality, it irks me when I see comments that don't seem to apply the same rigor to rhetorical discussions.
At the risk of being overtly snarky, could you really not conjure anyone that might have an opposing viewpoint?
And fwiw, I also think the image is really cool. It's insane the world we've built, and imagining the context of all the math, physics, and human power of will that are behind those streaks of light is awesome.
But a negative viewpoint can't be that hard to see, right?
Sorry, but the ship has sailed. Fix your problems in software maybe.
> - Astronomers / enthusiasts
Every Starship launch should offer ride-share for a space based observatory. Astronomy will only improve with space based telescopes. Yes, spacecraft are expensive but so are Earth based observatories, but how does it look with launch cost removed from the equation?
> - Those who enjoy nature
Generally can't see the satellites with the naked eye. Should probably concentrate on not walking into a hole / body of water / off a steep precipice.
This complaint about the aesthetics of the night sky is the wimpy enemy of progress. Imagine bronze / iron age people up in arms because suddenly the sea is full of fishing boats and merchant vessels. Or people up in arms because farmland has spoiled the view of forests.
Yes, I think this stuff looks nice without man-made things. I enjoy the night sky. I also enjoy being able to eat and utilize modern technology. There will come a day when spacecraft coming and going will be as routine as we see airplanes now, so our descendants will have that to complain about next, until it becomes as pointless to complain about as the asphalt roads that have lead to and from or houses.
Space based technology will make life better for all of humanity just like every technology that has come before it. The genie is out of the bottle and isn't going back in.
>how does it look with launch cost removed from the equation?
The Webb Space Telescope cost $10 billion, and has a 6.5 meter mirror. With the launch cost removed, it cost $9.5 billion.
The Extremely Large Telescope is located on Earth, costs a little over $1 billion, and has a 39 meter mirror.
The idea of completely replacing ground observatories with orbital ones is so infeasible it's not really worth discussing. If satellite pollution grows so extreme they can no longer function, those capabilities will simply be lost.
Example problem that I’ve seen posted about a few times on HN: LLM scrapers (or at least, an explosion of new scrapers) exploding and mindlessly crawling every singly HTTP endpoint of a hosted git-service, instead of just cloning the repo. (entirely ignoring robots.txt)
The point of this is that there has recently been a massive explosion in the amount of bots
that blatantly, aggressively, and maliciously ignore and attempt to bypass (mass ip/VPN switching, user agent swapping, etc) anti-abuse gates.
Fwiw, my initial thought (from the picture) was less “prove you’re not a criminal” and more “prove you’re not bringing a massive cart into the quick line. Idealistically, this would reduce the number of jerks tying up these lines for people who want the benefit you describe.
Don’t necessarily disagree with you though, I feel like there’s a decent likelihood it just slows everything down in practice.
Anyways- jail breaking requires being or remaining on certain iOS versions on certain specific hardware models. You can’t “just jailbreak” your apple device that you daily drive/use regularly. If you’re not on an old version on the right hardware already, you’re fucked. And waiting for a new jailbreak exploit is a (anecdotally, for me at least) nondeterministic amount of time on the order of O(years), with a significant probability that it will not be relevant for whatever device you’re waiting on.
reply