probably gets better with use but having to remember not to put a loop as the last statement of a function, because it would make it return an array of the last statement of the loop body, caught me off guard enough times to get annoying.
easy enough to add an extra line with just 'undefined' as the last statement of the function of course. but then you do need to remember that.
You can definitely use ReleaseSafe, you can also switch modes during compilation. so you can call '@setRuntimeSafety(false)' at the start of a scope to disable runtime safety for performance critical sections.
while we're wishing for impossible things i'd also love if the consent dialogs were an actual standard. if sites could describe a list of what they needed consent for and the browser supplied the actual dialog, so i could just configure it to always allow all if i wanted to, that would be fantastic.
> if the consent dialogs were an actual standard. if sites could describe a list of what they needed consent for and the browser supplied the actual dialog
There is a standard for this called P3P, which was implemented by Netscape, Firefox, Internet Explorer and Microsoft Edge before eventually dropping support for it. But there was nothing requiring website owners to use it. Various data protection regulations across the world require them to obtain consent for collecting data, but they are not required to recognise consent or non-consent expressed via P3P settings.
These standards will only get used if the website owners are forced to use them, either by regulators or by monopolistic/oligopolistic market forces.
You can get a good quality SLA printer for $200-300, and you can buy FDM printers for tens of thousands of dollars. Just depends on what audience they're targeting.
From what I've seen that's kind of overselling it, his own family hasn't claimed that he said that, an anonymous person who claimed to be a friend of his did.
But I may have missed any further developments to actually verify that his family had been told something similar.
Yeah, his family said "He was suffering from PTSD and anxiety attacks as a result of being subjected to the hostile work environment at Boeing which we believe led to his death". As much as a conspiracy for fear of being next could come into it I'd have to believe it'd be more than a lone and anonymous friend of the family that would speak out if confided with this info.
Between that and the 30 some whistleblowers in the last 5 years that two died close to one another isn't all that damning.
And in Barnett's case, he'd been talking since 2019. Even if one thinks Boeing would be willing to have people murdered, the time to do so would be before they became public whistleblowers, not a half-decade later.
Back around 2002 at least there were some products, ABCpdf is one I used a lot, which ran Internet Explorer on the server to generate PDFs from HTML. Worked pretty well from what I recall.
the phone is likely linked to an apple account. seems reasonable that if the components are approved for a specific phone and that phone is linked to an icloud account, that account could permit a swap?
That assumes that you managed to ask the previous owner to log into iCloud on another phone and "free" the previous one for repairs. I guess you could do that if he's buying a new iPhone from you, but still... it is similar to the Macs that are stuck on the previous owner's enterprise account.
i was more charitable about trying unofficial/unsupported nvidia setups that require hacks in the past, but not any more. they take extra work to set up initially, constantly break on updates, and leave a minefield of unknown unknowns that rear their heads when you’re trying to work. the result is a compounding amount of wasted time.
official support is the way to go for me, so i’m back on X for the time being
For me, Rusts SQLx has been a good option for this. Write plain SQL with a macro and have it verified against a dev database at build time, optionally to a typed anonymous struct to match your query results. The performance isn't incredible though.
I've been curious about sqlx for a while. About the non-incredible performance: Do you mean the performance of the verification in development, or the performance of sqlx execution in a live setting?
Personally I've never had an issue reading through the source for zig std, and if your editor supports it you can just 'go to implementation' on most things. Hopefully the code remains relatively readable since I find it preferable to see the actual code + some basic tests rather than trying to navigate those documentation sites.
easy enough to add an extra line with just 'undefined' as the last statement of the function of course. but then you do need to remember that.