https://abrisatechnologies.com/optical-coatings/color-correc...
i feel like this type of search engine would provide more variety than google which is more of a "the one answer". need more meta articles like this
3 karma · joined November 3, 2022
https://abrisatechnologies.com/optical-coatings/color-correc...
i feel like this type of search engine would provide more variety than google which is more of a "the one answer". need more meta articles like this
you can get an Amazon link with some counterfeit or fly by night product and a bunch of knucklehead reviewers saying stuff like "the black cable was indeed black!" and "it took long to ship!", or you can go to the local store that sells all the electronics stuff you need in some subcategory, which you would likely already know. also depending on what you want to look up, google will give you an invalid state approved answer (coming soon)
>If you wanted to find out about a particular IC in the old days, the best thing to do was to find the manufacturer’s data book. If you were in a school or a company, there might be what you wanted in the library.
...and today you get some shithead's 3rd party website with a bunch of pdfs from god knows where encoded into web page slide shows with google captchas
what im saying is that the academic idea of abstraction is far better and less leaky than ruby (dynamic name resolution and such "scripting language" crap) or java (data structures are intended to be used once or twice per program (exaggerating) instead of fluently like you would make trees in a functional language); its just obscured but if everyone understood the motivation it would have replaced stuff like ruby in all use cases.
i see ruby and java as a little shop where the owner will let you instantiate one or two objects according to some terms, and then let you maybe make your own class, but it will essentially just be a wrapper around a few of the shop's objects. whereas in ML you can model anything from the ground up, even numbers, and it will still be nicely implemented and the abstractions will be almost perfect.
> CPUs are now 1GHz
> C is obsoleted outside small sections of code such as image processing
> 23 years later
> "What if we just stopped using C?"
- It has to parse output of commands which may or may not be intended to be parsed and may or may not have a predictable format. The only way to overcome this is if this program becomes one of the Big Four "UN*X command output -> data" converters
- It casts things to "float/int"
- Depending on who made this library, the output itself may not be strict / predictable. Perhaps it will output JSON with two different key names in two different scenarios.
And don't forget that any of these issues will still come up even if they are accommodated for, due to versions of programs changing without the author of this tool knowing.But yeah basic things having intrinsic shortcomings is a given, when you're using UN*X.
From the nested article:
> Had JSON been around when I was born in the 1970’s Ken Thompson and Dennis Ritchie may very well have embraced it as a recommended output format to help programs “do one thing well” in a pipeline.
They had S-expressions and plenty more options. They also could have just made a format as you can tell with thousands of ad-hoc trendy new formats like YAML and TOML being spewed out every recent year now that programmers discovered data structures.