251 karma · joined April 1, 2018
I found that to be the "best" performing, although still leaves a lot to be desired and having to open the application, manually sign kernel drivers and then reboot after every kernel upgrade is a little tiresome.
I track everything using myfitnesspal and there's a strong correlation in my weightless during periods where I make an effort to consume around 30% of calories from protein. During less strict periods, my protein intake is usually around 20%. While my calories consumed remains the same, the higher protein diet is far more effective for weight/fatloss.
The biggest issue I've found with this kind of setup is that file change events from the host don't cascade to the virtual machine using VirtualBox's shared folders. NFS handles this better (still seconds delay based on cache values) but that is then a problem for Windows users.
It's been a few years since I switched to using Linux natively so my knowledge on Docker for Desktop Mac mount strategies may be out of date, but at one point docker introduced options such as :cached and :delegated which can have a considerable improvement to container file access speeds. Additionally, I've heard of people using mutagen and nfs for significant improvements, but I've never tried that setup. Here's a long discussion about it: https://github.com/docker/for-mac/issues/1592#issuecomment-6...
If your files are stored within the VM itself, WSL2's access to them is effectively native. However accessing the files from Windows requires going through the \\wsl$ (P9) network share. This presents problems as Windows isn't going to receive file notification events if you do something like `git checkout`. Additionally, if your project utilizes symlinks, Windows only sees them as an empty file.
Users of VS Code largely will not encounter these problems as running `code` from within the WSL layer will start a remote server, it's seamless, that's genuinely very cool. However, if you use anything else, I've found it to be problematic.
The "best" solution I arrived at (other than dual-booting Linux, which is totally worth it!) is to install `xorg-server` from cygwin, install my IDE of choice in WSL2 (IDEA) and use X11 forwarding. This way the IDE has a relatively real-time view of the filesystem, receives notification events, symlinks work, chmod is preserved if using safe-writes etc.
If you need to use bash (and other tools not provided by Git Bash), cygwin is a useful addition. You can also use `mklink` from cmd/powershell to create a directory hardlink to the \\wsl$ folder if you need to copy things into WSL (although it's easier to access /mnt/drive from WSL2). Either way, I've found any direction of crossing Host/VM filesystem boundaries to be slower than WSL1's approach.
In WSL1, access to files on the Windows host is far quicker than WSL2 and symlinks work everywhere.
To try to counteract this, I opted in to the insiders dev channel recently to try the upcoming X11 support, i.e. run IDEA inside WSL. While the performance is quite good, it's broken, e.g. try using find in project, the window disappears immediately 9 times out of 10.
In many ways, I found WSL1 more useable as I could use one shell for both the Windows and WSL filesystems with reasonable performance. I now use cygwin if I want to use gnu linux type tools on Windows.
Once the X11 support matures it will be a pretty good experience overall if people are willing to install things like IDEA in WSL, I'm looking forward to that.
I do not like the feature, but it's not as UI intrusive as the article suggests; it is however privacy invasive. Despite disabling multiple edge features related to telemetry, this is a new default-on option.
I like Edge enough that it's my default browser on Windows, Android and secondary to Firefox on Linux. However, one or two more features like this and I may use something else.
I'm also in favour of Thursday as the mandatory day if I need to be in the office as the last day of the week to do release management, e.g. minimise the risk of a bad deployment on a Friday affecting someone's weekend.
Maybe things are better when comparing the 15" XPS vs 16" MBP but I believe the WiFi chip and precision touchpad hardware/drivers are the same. The shipping of "incomplete" BIOS(es) and coil whine are also applicable AFAIK.
(on mobile and list formatting seems to have single lined, sorry if hard to read)
- Coil whine when connected to AC and IO happens
- Shipped with only S2 (connected standby) support. Battery in sleep would not last more than a day.
- Battery discharge even when fully powered off, do not expect to leave it unplugged for a weekend and it be usable
- Ill thought out microSD card slot, I ended up getting a card wedged between the chassis and bottom of the card reader, scratched the card pins and made the card inoperable
- Buggy Killer WiFi drivers, requiring toggling the adapter off and on
- Poor thermal performance, after seconds of my i7 running turbo(ing), base clocks reduce to 1.3GHz resulting in compilation or any heavy workload taking 3x as long to complete as my 2014 MBP with and i5
- Fan noise, it is almost always on and very audible, even in office conditions
- Lack of care from Dell around their Windows precision pad, e.g. small scroll movements do not scroll in non-"modern" apps such as task manager, or just about anything that is not Edge
Those are just a few points I've picked. I previously had an XPS 13 (standard) in 2015 and issues such as coil whine still existed then.
Additionally, the configuration options are unnecessarily restrictive, at least in the UK. I wanted 32GB memory so had to get the i7 model which is only available with the 4K panel option. Battery life is less than 4 hours.
My specification cost £2200 which is MBP territory but it doesn't feel on the same premium level as a MBP (or now, the incredibly attractively priced M1 MacBook Air).
On the positive side, I mainly run Ubuntu and aside from non functional camera and fingerprint reader that works pretty well, including thunderbolt docking. Although it took about a year for the Ice Lake GPU drivers to become stable and S3 eventually found support, although closing the lid does not always put the system to sleep.
Depending on the Linux compatibility of these I will definitely be interested once there are GB keyboard layouts available.
Once I'd seen it once, the mother-in-law is now prominent. I can still see the wife if I concisely choose to, but the mother-in-law is now the default, strange huh?
I run Ubuntu day to day and it has much better performance and less fan noise (presumed better thermals) than Windows.
True though, this functionality could do with fixing on the Windows side before we can expect it to work via proton.
There are some features that I was never able to get working correctly, e.g. remote Steam Play with Streets of Rage 4 where my friends stream would not load up or controllers would not map, but for single player gaming, this would not be an issue.
Performance is (to be expected) less than Windows and games can exhibit graphical artifacts or crashes but it is not bad enough really complain about given how amazing it is that this exists in the first place. I will often put up with these (imo) minor defects than boot to my Windows install. Steam cloud sync even works correctly for keeping your save data between OS'!
One thing to be aware of that I don't see people mention (maybe because it's a niche setup and game dependent), is that using fractional scaling can completely mess up some games display, I believe due to how fractional scaling uses a framebuffer larger than your real resolution. Make sure to set your scaling to 100% before launching games which have this behaviour, e.g. Tekken 7.
At first I was skeptical about the usefulness of such a feature given my password doesn't take long to type, but it turned it to be a feature I really enjoyed.
While it's arguable that there'll be no perceptible difference listening to 320kbps Vorbis versus "HiFi" on a dedicated device, I imagine there could be a difference when transcoding to AAC. Time will tell.
Windows had a lot of great disc software in the 90s/00s which would handle just about any disc format one would encounter, e.g. Alcohol 120%, CloneCD, Disc Juggler. Some of these were capable of backing up the various protections of the time such as SecureROM and Starforce.
dd is a powerful tool but I often find it the "wrong" tool, e.g. is it desired to clone a 2GB partition layout to a 128GB usb stick for a live CD and have to manually edit my partition tables myself?
The AppImage documentation mentions auto updating an electron-builder image is possible: https://docs.appimage.org/packaging-guide/optional/updates.h...
In no particular order: - cars drive on rails with no AI, this leads to an amusing bug on one of the highways where cars clip through a railing and destroy themselves, repeatedly - NPC's often get stuck in t-pose, the game either cannot work out what to do with them or animations were not completed - the game rarely maintains state of cars and NPC's if they're not visible (e.g. turn around 180 degrees), this can result in cars spawning where your car is while in motion - unbalanced perks such as the body perk which stops enemies from knocking you over has the unintended side affect that a minimal hit and run by an NPC vehicle on the player character results in instant death because you cannot be knocked over - enemy characters path finding failing and clipping through walls, I had to restart a section of the Panam ending 3 times because of this - delayed physics calculations resulting in the player either moving at superhuman speeds or being catapulted through the environment - the number of times my player became naked
There are many more bugs I encountered which I do not imagine to be related to loading times. In addition to the bugs, the game is simply incomplete, the lack of police AI (they instantly spawn behind you and are never seen driving vehicles) being the easiest example to provide.
This is not to say the game cannot be fun, I've put nearly 100 hours into it, but even after the 1.06 patch, I feel cheated by CDPR. The game is so full of bugs, glitches and missing game mechanics (compare what we got compared to their 2018 45 minute gameplay teaser) that it should have been delayed.
As it is, I feel that I've paid £50 to be an alpha tester for what I believed to be a completed retail game.