1,389 karma · joined March 21, 2012
Interests: Books, DevOps, Gaming, Programming, Web Development
---
The idea holds across many acoustic instruments though.
It's no accident that musicians spend a lot of money on instruments -- even electric guitar players -- an instrument that is electronically amplified and often distorted and otherwise augmented -- will have strong feelings about the particular type of guitar they use. Leaving shape-based decisions out of it (and pickups), hollow bodies are going to produce a different sound than solid. Different wood types will produce different tonal characteristics.
So the things that are directly controlled are less like terroir, more like choice of grape used maybe? While the make of the instrument, the shape of the room a recording was made in, these are much more like terroir I think.
But it's probably just not a great metaphor.
Meanwhile, food packaging is unregulated and has been shown to be a major source of PFAS. Water bottles are particularly guilty.
https://www.consumerreports.org/health/food-contaminants/dan...
Sneak was right -- by default iCloud backup is enabled and is backing up all iMessage, SMS, and MMS messages.
I was just caught up on the difference between iCloud for Messages and iCloud backup of messages.
Apple support article that lays out what's backed up by default:
TIL.
iCloud backup IS enabled. But Messages in iCloud is off.
Further, Apple ended up rolling out Advanced Data Protection for iCloud in 2023, so users who truly don't want Apple holding those keys can effectively take them from Apple.
https://support.apple.com/guide/security/advanced-data-prote...
EDIT: Just confirmed with a test device and test apple id, iCloud for Messages is not enabled on it.
Here's what I see them as providing:
- Simple async, no wasted CPU on I/O
- Strong typing defaults
- Reliable static analysis
Half of the "pros" he lists for using GraphQL are just provided out of the box using ASP.NET Core with NSwag to document the endpoints. If they want to keep the client-side composability, create some OData endpoints and you've got it.
> Self-documentation of exact return type
> Code generation of exact return type leads to safer clients
> Our various apps (user app, support app, Wave agent app, etc.) can mostly share one API, reducing complexity
> Composable query language allows clients to fetch exactly the data they need in a single packet roundtrip without needing to build a large number of special-purpose endpoints
Bias flag: I'm primarily a C#/.NET developer. I came up on python and ruby but have had more success in my region getting paid to work on .NET code.
> the EU probe found that iMessage falls outside the legislation because it is not widely used by businesses
Apple does offer a specific service for businesses, Apple Messages for Business, but their documentation claims it's actually different from iMessage:
https://register.apple.com/resources/messages/messaging-docu...
> Apple Messages for Business differs from the widely known iMessage by being a business to end-user service. Additionally, the encryption mechanism slightly differs from a traditional iMessage.
Given that businesses can interface with AMfB using APIs rather than the Messages app on an Apple device, it seems that would fall pretty far outside the iMessage gatekeeping definition.
If the attacker got a list of passwords from a leak and your password was on it, the 2nd factor provided by the TOTP will still save you.
So, it just depends on your threat vectors. I’d rather people I support keep unique passwords alongside TOTP in a manager they’ll actually use than skip or use SMS TOTP because of a vague concern about targeted hacking of their manager.
As others have said, benchmark frameworks are great. Many systems have support for high-resolution perf counters these days. Just ran a quick test on my local system, it's able to make a timer accurate to 100ns.
Benchmark frameworks let you hook into your code in such a way that you can easily run a single fragment 10k-10m times and produce an analysis of the result that includes mean time, std deviation, and memory allocations. They usually let you setup a side by side comparison so you can directly compare 2+ methods.
If you use a language with a JIT then good frameworks for those include a warmup period to get the best-JIT version of the code in place before collecting data.
https://www.backblaze.com/cloud-storage/pricing
$6/TB/Month. Very manageable egress-fees. If you're using it for cold-backup, hopefully you rarely have to pay them.
I never really clicked with biology in school - but learning about systems is always fun. A bit of a pop-sci read on the subject that's very approachable. Most chapters are <10 pages. Dettmer manages to distill information very effectively though, he paints a fascinating picture of the complicated machinations of the human immune system.
If the foreground app requires more resources than are available due to background apps, it will suspend background apps to free up those resources.
Apps don't really have much they can do to get around this, assuming you're not jailbreaking or installing local profiles.
Well-built applications will have already saved state with every interaction. When they go to the background they will start unloading unnecessary resources and prepare for possible suspension by saving any additional data. Then when they're suspended, their state is saved to a snapshot that they can load in later so it's as though they never were suspended.
There _is_ more capacity in recent versions of iOS for an app to use background resources, and to start a background process automatically. Still, the system treats background processes with a lower priority and terminates them for using too much power way more aggressively.
I didn't keep a great log of how the battery handled before that, but it does seem like I have to charge it less than I used to.
I only force close apps when they're clearly stuck.
I'm pretty religious about what apps are allowed background data, and notifications in general. But I never turn off any of the radios.
I love the Oasis, I'd like it if they made a slightly larger variant with USB-C. Basically the form of the Scribe, but I'd rather skip the pen input.
In my experience, the OS does matter. I can’t believe how bad the rest of the industry is at this. Amazon’s Kindle line is incredible at this IME, but those are pretty atypical devices.
Screenshot from said iPad’s battery screen: https://postimg.cc/xcHpy5Sr
If Apple were to package their laptop line with Qualcomm powered cell modems, I have to imagine the prices required would really take people aback, hence why they're so steadfast in trying to create their own modem.
As for why it's better than tethering, it just works without having to do anything. For some users who are always on the go, that's a huge convenience. Also, tethering eats at the cellular device's battery, which is usually a lot smaller than the battery we lug in our laptops.
I don't think satellite comms are on any sort of track to meaningfully replace cellular ones. Everything I've seen in that vein is more supplementary to the existing networks, rather than trying to completely replace it.
[1] https://arstechnica.com/tech-policy/2019/05/how-qualcomm-sho...
that would require people cut back on meat consumption
You chose to only quote the
Would rather die part.I’m simply asking you consider something beyond the meals you want to partake in.
You’re absolutely correct- I never have worked in that industry. My family has worked the chicken industry in Georgia and South Carolina. I’ve seen the result of that labor first-hand. If that brain washed me then so be it. That labor is inhumane. It is hardly the only inhumane labor that we rely on.
The thing is I believe you’re capable of seeing more than your comment lets on. I wasn’t hand-fed some propaganda and I don’t think you were either. It’s a weird world out here.
What amount of suffering in the world would cause you to even consider the option of eating less meat? Is it something you’re willing to contemplate? Not just animal suffering either. Think of the complicated web of problems that come out of people eating too much meat. The antibiotic use discussed in this thread. The methane byproduct discussed in countless others. The inhumane conditions of most butchers (for workers! Let’s forget the animals still).
It’s okay if none of that bothers you. We’re only human. I’m a former vegan, I’ve likely considered it all more than strictly necessary. I don’t think anyone _has_ to be anything. But for what it’s worth it _could_ be about more than an individual’s health.
LVT cleans up this incentive some by putting taxes in place in areas where the land is more valuable. I think Georgists would argue for doing that _and_ removing property taxes, specifically so you aren't taxed for the things you own.
Since 2014 they've released Community Editions of Visual Studio, with a lot more useful features and less restrictive licensing than the old Express editions.
But if you're used to writing Python in Notepad++ I'd skip VS entirely. You can install the dotnet SDK and just keep using Notepad++.
Here's literally everything to write a CLI app in .NET 7:
A csproj file:
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>net7.0</TargetFramework>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
</PropertyGroup>
</Project>
A program.cs file: Console.WriteLine("Hello, World!");
Then open a terminal and navigate to the folder you put the files in and run `dotnet build`. Or just pass in the folder in the argument `dotnet build .\demo\demo.csproj`.Voila. A CLI executable is built in the .\bin\Debug directory.
There's a pretty good starter tutorial for the Web API one here: https://learn.microsoft.com/en-us/aspnet/core/tutorials/firs...
Or here for the Web App MVC one: https://learn.microsoft.com/en-us/aspnet/core/tutorials/firs...
Then a 2nd shortcut to reverse everything back to how I like it in the daytime.
I'm planning on going back and playing the Divinity: Original Sin games that Larian made before it. I hear they're fantastic as well.
A lot of the Japanese rice cookers cook it a bit lower/slower than you'd normally do on a stovetop in a pot. The result is usually rice with nicer texture and flavor, but if you're only ever buying the cheapest rice, or value the speed it can be cooked, it's probably not worthwhile. Just stick to the really cheap rice cookers that usually take around 20 mins.
Here's a screenshot from the Zojirushi Fuzzy's manual, it generally takes around an hour to cook any rice.