MobiusHorizons
Joined 1,882 karma
- MobiusHorizonsAre you saying you bought an electric car with functional 84kwh pack for less than 3 grand? If so I think the outlier is you. That is a better deal than I have seen.
- Sometimes you don’t have all the relevant details in scope at the point of error. For instance some recoverable thing might have happened first which exercises a backup path with slightly different data. This is not exception worthy and execution continues. Then maybe some piece of data in this backup path interacts poorly with some other backend causing an error. The exception won’t tell you how you got there, only where you got stuck. Logging can tell you the steps that led up to that, which is useful. Of course you need a way to deal with verbose logs effectively, but such systems aren’t exactly rare these days.
- What you are proposing sounds like a nightmare to debug. The high level perspective of the operation is of course valuable for determining if an investigation is necessary, but the low level perspective in the library code is almost always where the relevant details are hiding. Not logging these details means you are in the dark about anything your abstractions are hiding from higher level code (which is usually a lot)
- I also generally find that people looking for “best practices” to follow are trying to avoid that “sitting down to think about the software and its role in the overall system” piece.
- At least do a google takeout backup. I believe there are ways to import that into software like immich (a self hosted alternative)
- I live in a pretty urban area, so maybe that's why I haven't seen so many brights. I've heard the autobright theory and it certainly makes sense though, especially in areas where people have a reason to use their brights.
> [0] https://www.youtube.com/watch?v=H3pTHSIYFlg
I believe this technology is generally called adaptive headlights, and is implemented in quite a few cars. I believe some quirk of US laws (which specifies brightness at various points in the beam) actually prevents this feature from being implemented. Really sucks, because these new LED headlights are really hard to stand at night.
- at some level it's not really an engineering issue. "bug free" requires that there is some external known goal with sufficient fidelity that it can classify all behaviors as "bug" or "not bug". This really doesn't exist in the vast majority of software projects. It is of course occasionally true that programmers are writing code that explicitly doesn't meet one of the requirements they were given, but most of the time the issue is that nothing was specified for certain cases, so code does whatever was easiest to implement. It is only when encountering those unspecified cases (either via a user report, or product demo, or manual QA) that the behavior is classified as "bug" or "not bug".
I don't see how AI would help with that even if it made writing code completely free. Even if the AI is writing the spec and fully specifies all possible outcomes, the human reviewing it will glance over the spec and approve it only to change their mind when confrunted with the actual behavior or user reports.
- I don't actually think people are driving around with high beams on. Modern LED headlights are just brighter, and cars are higher up than they used to be, meaning older lower cars, especially sedans are just in the path of regular beams. I actually yelled at someone once to turn off their high beams because I was so convinced that's what it was. turns out, they just drive a tesla, which just have blinding lights. I guess there are also probably people with high beams, but most of the ones that are terrible aren't high beams, they are just modern.
- I think you meant to write “when, not if” instead of “if, not when”
- Thanks for the explanation. I see where I got confused now
- Ah that makes sense, thanks for clarifying.
- Ah I see. I guess if the design files are available that might be possible. Not sure about component availability though. I don’t remember for sure, but I thought there was something custom about the Broadcom Soc they were using, although that might have been for a different model.
- Those boards have a lot more on the board than just the cpu. At a minimum they have power conditioning and ram, usually also storage. A lot of what you pay for with an sbc is that routing and layout. If it’s got WiFi as well, you could be paying for the testing that goes into rf micro strips and potentially certifications on em emissions.
It is, of course possible to do all that yourself, but the system on module exists, because this integration has value that people are willing to pay for.
- I think the question is “how are the behavior of random spammers on your search page getting picked up by the crawler”? The assumption with cache is that searches of one user were being cached so that the crawler saw them. Other alternatives I can imagine are that your search page is powered by google, so it gets the search terms and indexes the results, or that you show popular queries somewhere. But you have to admit that the crawler seeing user generated search terms points to some deeper issue.
- Ah. The parent mentioned several frustrations that I am not familiar with (presumably since I also pay for premium and don’t block the ads), but my impression was that the delay was caused by the code refusing to play the video until the time slot for the ad had completed even if the ad failed to load (as would happen when blocking the ad http request)
- Interesting, I thought Apple Silicon was still ahead on raw numbers, would you mind pointing me at any resources to learn more?
Is that still true when you consider the whole system power consumption vs performance? I was under the impression that Apple's ram and storage solutions give them a small edge here (at the cost of upgradability / repairability)
- It’s still C though, and rust is not an option. What else would you call it? Lots of c libraries for embedded target C89 syntax for exactly these reasons. Also for what it’s worth, SDCC seems to support very modern versions of C (up to C23), so I also don’t think that critique is very valid for the 8051 or stm8. I would argue that c was built with targets like this in mind and it is where many of its quirks that seem so anachronistic today come from (for example int being different sizes on different targets)
- It's mostly embedded / microcontroller stuff. Things that you would use something like SDCC or a vendor toolchain for. Things like the 8051, stm8, PIC or oddball things like the 4 cent Padauk micros everyone was raving about a few years ago. 8051 especially still seems to come up from time to time in things like the ch554 usb controller, or some NRF 2.4ghz wireless chips.
- Please don't get me wrong. I'm glad the world has mostly transitioned over to HTTPS, but what are you actually concerned about with reading a blog post over HTTP? If you had to log in or post form data, or hosted binaries or something I would get it. But what is wrong with reading an article in the clear? And how would SSL prevent that?
- You likely pay for YouTube premium if you aren’t noticing adds