TBH, anything that can make interface casting faster/more efficient in go would be a welcome improvement.
583 karma · joined October 7, 2019
[Verifying my OpenPGP key: openpgp4fpr:4BCF3BA4BE9FC8194C6FF7BC0A6BE3C9CD4A46F4]
TBH, anything that can make interface casting faster/more efficient in go would be a welcome improvement.
The FUD that gets spread around SB helps no one, and other than a small list of exceptions, you are always in control of your system.
SB allows MS to transparently enable Full Disk Encryption by default, which I think is a win for all users. It allows you to do the same on Linux. It lets server operators be sure their systems have not been tampered with. While there are many problems with UEFI, SB is not one of them.
I suppose I'll post the link someday. I literally just started today.
https://help.kagi.com/kagi/search-details/search-sources.htm...
The next question from there might be why do DNS responses change so frequently? I don't have an exact statistic, but most of them don't (I would guess 90%), so you could probably indefinitely cache those. But the ones that do, iirc, it's usually to allow quicker changes (esp. if the site is under active development), load balancing, global distribution, etc.
I hope that's helpful.
That is not the case here.
If that was indeed the case, one would expect the train's diagnostic systems to report that it has detected certain issues that need to be resolved before the train will start up again. But that didn't happen, instead the train simply refused to start, no error codes, nada.
Not only that, but further investigation revealed that the train's firmware contained code that would disable the train if it was present in a competitors shop for a considerable time.
> There should be an opt out system
This mechanism for disabling the trains, was never mentioned in the discussions or contracts for purchasing the train (which is why a third-party could win the repair contract). There was never an option presented to "opt out", that is why people are saying that the trains were sabotaged.
> to what extent is that Tesla's fault?
It isnt. You made unsafe modifications that can be clearly shown to have caused damage, it's your liability.
> Say Tesla made all reasonable steps they could take to detect third party mods and refuse to start the car, do we hate them too?
Depends, did their software present an actionable error or not? If the car gave an error code, and you look in the manual and it says that too much current is going to the motors (idk), and then you fix that and the car starts? Great! But if the car just refuses to start without any indication as to what is wrong, and further even if all repairs are reversed it still no longer starts? That sounds like deliberately sabotaging third-party repair.
But, I am curious why they decided to go with reserving keywords (like if and for) instead of doing what JSX does and just wrapping any Go code in braces.
I definitely think that he may not have told the whole truth, but greedy sleaze-bag liar is not how he comes out in this story (at least for me).
[0]: https://www.reddit.com/r/apple/comments/9pow06/louis_rossman...
As an aside, is there any way I can add functionality to a control surface (that isn't writing C)? I use a behringer X-Touch (heavily) and moved to Reaper because there were plugins that provided much deeper integration with my X-Touch (which as a result has me working a lot faster in certain areas).