If I was going to switch anyway, I wouldn't switch to Azure DevOps Server, I'd switch to GitHub Enterprise. I don't think there's much of a future for Azure DevOps.
The lead architect of the PS5 said that NVMe drives will need to be a bit faster than the built-in SSD to make up for the fact that they don't have the optimizations that Sony has for the built-in controller. Essentially only the highest performance PCIe 4.0 NVMe drives will be fast enough for the PS5.
I once spent ages trying to determine why a Python unit test that sorted timestamps constantly failed on Windows. In the test, we compared the timestamps of performed operations, and checked to confirm that the operations happened in sequence based on their timestamp (I'm sure many of you see where this is going). On Windows, the timestamp for all the actions was exactly the same, so when sorted, the actions appeared out-of-order. It was then that I discovered Python's time library on Windows only reports times with a resolution of ~1ms, whereas on Linux the same code reports times with a resolution of ~10us. That one was actually super fun to track down, but super disappointing to discover it's not something that's easily remedied.
(For those about to suggest how it should have been done, the application also stored an atomic revision counter, so the unit test was switched to that instead of a timestamp.)
I'm glad Microsoft is doing development out in the open, but I really wish they'd do a better job of isolating features like WSL from the underlying OS. I'd gladly run an insider build of WSL, but with their track record of stability for their general releases, it terrifies me to think of running an Insider build of Windows.
I picked Louisiana because they reported their first COVID case a few days after New Zealand reported theirs. I think it's an apt comparison in their current outcomes, just to indicate that strong action could have prevented virtually all of the deaths that have occurred.
That being said, I do agree that the long-term implications of their actions aren't something we can really discuss at the moment. My biggest concern, however, is the increasing number of cases of heart damage following COVID infection. We may find ourselves in a situation where deaths _after_ COVID are significant. A vaccine won't help the almost 7 million people who have likely already suffered that damage. I sincerely hope that in a few years time the most significant damage COVID has is on a country's economy, since that's something that can recover.
> There is no perfect compliance to masks, lockdowns etc. and masks, lockdowns etc. are not 100% effective.
They don't need to be 100% effective, only reasonably effective. Take New Zealand for example. They have a population of about 4.8 million, yet have only had 25 deaths. Louisiana, a state in the US with a similarly sized population has had 5,375 deaths as of writing.
Just because the lockdowns in the US didn't work isn't a flaw of lockdowns in general; it's a flaw in the response of the US government. We needed swift, strong, decisive action, and we needed it when cases first started appearing. We didn't get that, and now hundreds of people are dying each day.
> Ever get into a situation where there's on-ramps and off-ramps on both sides, you've never been on that stretch of road before and there's a lot of traffic?
One advantage cars with large sensor suites have over humans is that they can see and process information from all around them. In your specific example, the car can watch both on an off ramps at the same time, isn't phased by the "newness" of the road since other cars have navigated this section of road hundreds of times before it has, and can keep tabs on cars obscured by line of sight due to the car's ability to bounce signals off of vehicles.
I'm already a Matrix/Element user, and I honestly don't see the point in using a bridge for my personal IRC usage. I think it's cool for groups that want to maintain IRC after switching to Matrix, but it feels like it's a bit too much complexity to use Matrix as a UI for IRC.
The Lounge is the first app to make me really use IRC. The ability to have it running on my home server and be easily accessible from all the devices in my house through a nice, mobile optimized web interface is an absolute delight.
For what it's worth, Kindle Previewer 3 runs without issue under Wine (well, at least the CLI). I use it to convert epub files to KFX to add to my Kindle.
That is not an apt analogy because the switching costs for grocery stores is no where near as high with iOS. If you want the full argument I highly recommend reading the full legal filing.[1]
I think we're on the same page here. Are you saying that the application of Apple's TOS can't be considered retaliation since it's something Epic agreed to be held to?
Sorry, to clarify, I wasn't trying to imply that what Epic did wasn't against the TOS. My point was that Apple has the authority not to terminate Epic, but has chosen to do so, even when they've allowed other apps that have done things against the TOS to retain their developer account.
Epic very specifically defined the "market" as iOS devices. Their argument is based on the assertion that Android is not an alternative to the App Store since it's a completely different operating system. So, Apple actually has 100% market share of the iOS market.
> I just follow the rules in my TOS and block them like I do others who don't follow the TOS
I'm fairly sure Apple doesn't terminate the developer account simply for failing an app review. I think this is a specific executive decision based on the fact that Epic is unlikely to rectify the issue, which could be seen as retaliation.
Just to clarify, 476kb of WebAssembly != 476kb of JavaScript. Still, your point stands in that wasm-based sites will likely never beat their pure JavaScript counterparts in terms of data transfer; you'll need to make up the increased cost of wasm somewhere else. One place that browsers attempt to make up the difference is in the use of streaming compilers, where the browser can start compiling wasm as it's coming in from the network, whereas with JavaScript browsers have to wait until the entire resource is delivered before the parsing stage can begin.
After reading this, I checked what topology my UPS is using and was happy to see it's line interactive. I have two CyberPower CP1500PFCLCD units, and am approaching the one year mark. It looks like the batteries are even hot-swappable, which I'm sure will come in handy when replacing them.
I was really disappointed to see that it's not an open protocol (at least not yet). It would have been awesome to add this functionality to Windows and Linux desktops.
Yeah I think the big issue here is that HEIF is typically used to get JPEG level quality at a lower file size. Increased bit depth would negate those file savings, and I bet Apple/Google would just prefer you use RAW.
The iPhone defaults to HEIF, and all Android devices running at least Android 9 have the option to save images in HEIF. That being said, I have no idea if you get any of the benefits of a higher bit-depth.
Obviously I can't speak for anyone but myself, but using GitHub Dark[1] has been the single biggest improvement to my experience with GitHub on a day-to-day basis. I have a large monitor, and spend hours a day looking at issues and code on GitHub. Having a dark theme is essential since the alternative is to deal with being blinded when switching from my editor back to GitHub.
I suspect many of those who are ad-averse like me use third party clients and ad blockers, and have an inherent distrust of ads, so I doubt I'm worth much to an advertiser considering my engagement rate is zero.
That's it. I pay $12/month not to see ads on YouTube, and I'd easily pay that same amount for an ad+algorithm-free experience in the Twitter native app.
I actually helped my previous company migrate from Magento to BigCommerce, and found their offering incredibly compelling compared to Shopify. I do think BigCommerce is focused more on medium-sized businesses whereas Shopify is targeted towards smaller businesses or businesses that aren't really focused on their e-commerce side. My favorite feature of BigCommerce was the ability to run the site locally for development, using live product data from the site. I even made a few open source contributions to that framework, which was a nice change of pace compared to Magento development.
I think that the laser focus on the use of the word "lazy" isn't really warranted considering the author isn't a native English speaker. His use of "lazy" meant more along the lines of "taking the easy way out". It was a reference to the WebKit team giving a list of several APIs that they were not going to implement because of privacy concerns. It takes little to no effort for the WebKit team to simply throw their hands up, yell "Privacy concerns!", and then refuse to implement or engage in a discussion on how to improve the APIs. That's why the term "lazy" was used, and while I would have phrased it differently, I think it's abundantly clear that the author wasn't calling a person or persons lazy, merely describing their actions as the easy way out.
Sure, and that's why a good number of UWP apps have ARM64 versions. But UWP apps represent a miniscule fraction of the .NET Windows apps out there. What makes it even smaller is the fact that .NET Native is even a subset of .NET Standard, so some things like Reflection don't work without some additional tweaking. Can you write a UWP app using .NET that runs on ARM64? Sure! But basically every non-UWP Windows .NET app needs to wait for .NET 5 to build for ARM64.