hackujin

I can experience that jumping out of a plane and for way longer than 3 minutes.

They aren't going to space! The thing barely makes it to to edge of the atmosphere. How long are you gonna keep apologizing for them? There's literally no technical innovation here.

No payload. No orbit. No value.

More like "in high altitude, low air pressure environment abort". This thing will never go to space. It's not designed for that.

> while the booster drops back down, kicking in the landing gear and rocket-powered breaking system to land on the ground, unscathed. The capsule, meanwhile, using a pair of parachutes to coast back to Earth

Nope. No weightlessness at all.

Straight up... straight down. No orbit. Nothing to see other than "tourist" flights for people who want to see what space is like but without weightlessness.

While at the same time they've been stripping out vital features or outright disabling them on mobile. It's almost like gasp they don't care about the users but only their bottom line.

Same. My typing precision has gone down due to a lack of tactile feedback with button shapes and what not.

I was given an MBP with a touchbar when I contracted with Comcast for 10 months. Hated it.

My personal laptop is MacBook Pro (Retina, 15-inch, Mid 2014).

I will NEVER EVER pay with my own money for a touchbar mac book.

My number one rule when getting a laptop is a good keyboard. Period.

Plus the USB-C drivers for external displays in the new mac books is complete trash. Misaligned windows, constantly forgetting window positions, occasionally completely not working.

The MBP line of computers keeps on getting worse and worse.

Kosher Jews say the same about shellfish and pork. Calling those sources of protein quote "bottom feeders" and therefor unpure.

Yea.... no thanks. It doesn't even have vital social features like looking up a past event (because pictures). I tend to have to use the website. I uninstalled the Android app and now I just use the mobile website in a browser. I do have messenger installed cause that's what I actually use.

The file becomes invisible to WSL right after it gets edited in Windows. It's because it's doing weird tricks to associate UNIX permissions to files stored in Windows. The Windows app will break those permissions so instead of mitigating that in WSL it simply stops being able to "see" the file.

That's one of the ones I don't run but I can imagine why someone would want to rip it out for various legit reasons.

Personally.... I feel that if I don't use Onedrive I shouldn't see a prominent Onedrive icon always visible in Explorer or have onedrive.exe constantly running in the background using resources.

So I guess I'm stuck with using hacks to keep my operating system from shilling products at me.

I just don't want to use Windows to test my code when production is in Linux. There are things all those tools do when running in Windows that is specific to Windows. And I'm not some anti-windows Microsoft hating guy. My main desktop is running Windows 10 and I was quite excited for WSL to come out so I had Windows 10 Insider Preview running on my machine for more than a year. But at the end of the day when I want to do "real" work I keep going back to my Macbook.

Windows command prompt compared to bash is simply horrible. I personally find Powershell to be just as bad. The console app in windows is still light years behind Terminal in OS X. In fact VSCode's built in terminal wrapper is orders of magnitude better.

Things like wkhtmltopdf to generate PDFs or ffmpeg to work with videos should run as they do in Linux on the production server. In OS X I can use brew to set things up. In windows I have to hunt down binaries, put them in the right place, and set the path manually via an OS level GUI many clicks down in Advanced Settings.

The extra work I need to do to make all those tools work in windows makes setting up a windows dev environment cumbersome and annoying. The way it's laid out in OS X gives me way cleaner interoperability with the way the code actually runs in a Linux environment.

It's one of the reasons I love WSL! Finally I can have a ~/.ssh/config in Windows! But I still can't edit the file from a Windows text editor.

Finally if I'm on a team where the production environment relies on some of these linux binaries being available I don't want to waste work hours researching and writing on boarding documentation for the one dev that feels like working in windows when the rest of us are on macs.

Of course I want this!

Globally installed npm and composer packages live in ~/.npm/ and ~/.composer/ and they both have a global packages.json esque file that I need to occasionally edit. The packages installed in those folders MUST be parsed by VSCode for intelesense to work properly.

All I'm saying is I'm not gonna jump through all these hoops. I'd rather just keep working on my mac.

Hell I'd rather hackintosh a surface pro rather than deal with these issues.

Running VSCode through X is annoying.

That is not a solution. I want to work on files in my WSL home folder. Lots of language based package managers like npm and composer "live" inside a folder in your home directory. It's very important that VSCode running as a windows application be able to read/write to these files.

As it is right now I can't even edit my ~/.ssh/config from VSCode without jumping through hoops.

An OS should not have any bloatware at all.

This should not exist and yet it does: https://github.com/W4RH4WK/Debloat-Windows-10

I can't open files in VSCode that live in the WSL virtual file system. Which is a huge problem for setting up the same exact dev environment I have on my Mac.

It's honestly dumbfounding. VSCode works great on Mac with the existing terminal but the WSL team can't figure out a good way to allow you to edit WSL files from a normal Windows application.