Unless you're an independently wealthy jackass, I'm not sure how you can attack non-FOSS software users. I am a software engineer and I get paid to write software. I write some code for fun at home too and if people use any of my projects Im delighted. But if you want bug fixes and reliability and consistent new features and updates to apis and I have to listen to your bullshit complaints about how XYZ is better, you bet your ass I'm gonna charge for that.

It's like a baker making bread who gives out a few loaves for free at first. You don't get to complain if 100s of people show up demanding free bread and he starts charging them. Maybe communism is a system that demands people work for free, but elsewhere you're entitled to whatever wage the market will bear.

"Woke" means whatever anyone wants it to mean at any time.

Or is the theme of the movie about awareness of systemic racism in the US justice system? Haven't seen it myself

He wanted to prove he doesn't care about money and is fully willing to throw away $44 billion dollars on a shitpost

They're running in a datacenter in the netherlands with a ridiculous amount of bandwidth. I did find out they're classified as an "isp and web hosting company".

All our Dedicated Servers have 1Gbit connections with a dedicated 1GigE uplink.

I'd also guess that many of the seeds on any torrent (on a private tracker) are going to also be coming from seedboxes. That might explain why it's so fast too, there is tons of bandwidth between the datacenters themselves. I'm definitely throttled at 100MB/s regardless of how many torrents I've got running (1 or 100), but if they're running 50-100+ instances along with dedicated servers they must have tbps of bandwidth.

So long story medium, unless you can install your home server into a datacenter with a multi terrabit link to the backbone, it will be tough to replicate

How did they taste? Hopefully they were still crunchy

I've used it for 15+ years and it's a huge downside. Older content used to be widely available, but more often then not anything popular is removed within a few months of posting. It is actually pretty great for obscure content that won't get taken down. It's cheap but a whole new thing to learn. It is faster than torrenting directly to your own computer but a seedbox blows usenet out of the water as far as speed. 50-100 MB/s easily (at least using private trackers).

Follow up questions: Were you saving up the shit for 3 days for the sex party? Or was it that you didn't want to shit at a sex party? Was it a personal decision or a house rule? And was that 3 day shit afterwards more enjoyable than the sex party itself? Sounds amazing

There is definitely a huge difference after 6 months of focusing on one thing. I've done hot yoga off and on over about 12 years and I'd say it took 6 months of going consistently before I felt like my body adjusted and it was more enjoyable. After 2 years I didn't feel like I was going to die and it actually became very enjoyable.

I've fallen off recently because it's easier to sit around and initially it does suck because you need to readjust. But I when I had gone 2-3x in a week, man I felt like a god. I started going in my 20s, I was high af all the time and knew I needed some exercise or I was gonna die.

I think it takes a certain person to love lifting weights of all things. But luckily there are lots of things out there

I don't think I truly understood why some people don't like spicy food until reading your comment.

Yep, that's how I write my code too. I took a class in college, comparative programming languages, that really changed how I thought about programming. The first section of the class was Ruby, and the code most of us wrote was pretty standard imperative style code. If statements, loops, etc. Then we spent a month or so in Haskell, basically rewriting parts of the standard library by only using more basic functions. I found it insanely difficult to wrap my head around but eventually did it.

Then we went back and wrote some more Ruby. A program that might have been 20-30 lines of imperative Ruby could often be expressed in 3 or 4 lines of functional style code. For me that was a huge eye opener and I've continued to apply functional style patterns regardless of the language I'm using (as long as it's not out of style for the project, or makes anything less maintainable/reliable).

Then one day a coworker showed us a presentation from Netflix (presentation was done by Netflix software engineers, not related to the service) and how to think about event handlers differently. Instead of thinking of them as "events", think about them as async streams of data - basically just a list you're iterating over (except asynchronously). That blew my mind at the time, because it allows you to unify both synchronous and asynchronous programming paradigms and reuse the same primitives (map/filter/reduce) and patterns in both.

This is far beyond just eliminating if statements, but it turns out if you can reduce your code to a series of map/filter/reduce, you're in an insanely good spot for any refactoring, reusing functionality, easily supporting new use cases, flexibility, etc. The downside would be more junior devs almost never think this way (so tough for them to work on), and it can get really messy and too abstract on large projects. You can't take these things too far and need to stay practical, but those concepts really changed how I looked at programming in a major way.

It went from "a program is a step by step machine for performing many types of actions" to "a program is a pipeline for processing lists of data". A step by step machine is complex and can easily break down, esp when you start changing things. Pipelines are simple + reliable, and as long as you connect them up properly the data will flow where it needs to flow. It's easy to add new parts without impacting and existing code. And any data is a list, even if it's a list of a single element.

Personally I think VSCode is a pretty weak IDE in a lot of ways. Half of the suggestions are more like "guesses" without any real context-aware processing happening. It's performance in automated refactoring or automatically detecting/fixing stuff like import errors is highly language dependent and poor quality for many (esp dynamic languages).

I've used many text editors and IDEs. Textmate 1 was the first I truly fell in love with, and over the years heavily used Textmate 2, Sublime, Atom, and VSCode. Spent a solid 6 months with SpaceMacs (look it up if you want to hurt your brain) but wasn't for me.

I started using IntelliJ at work for a single feature (the diff tool) and eventually switched over entirely to Jetbrains. WebStorm is by far the best web programming IDE I've used (react support is insane, w/ 0 time spent configuring it). I've used a few others (Ryder, CLIon) but IntelliJ is the work horse that gets it done for me.

I sometimes go try out VSCode again or other IDEs. They're fun and shiny for a day or two until the minor annoying issues pile up and the lack of depth in the features / code introspection becomes more obvious. Then back to IntelliJ.

I usually pirate most tools until they've demonstrated substantial value for me, and really hate subscriptions. But Jetbrains entire suite with the "returning customer" discount is like $150/year. And I got the discount on the entire suite because I had paid for Webstorm in the past, which seems really customer friendly. Really not trying to ride their dick or anything, I just feel like they really save me time and mental effort which is my most valuable resource these days.

Personally I try to keep my code as free of branches as possible for simplicity reasons. Branch-free code is often easier to understand and easier to predict for a human. If your program is a giant block of if statements it's going to be harder to make changes easily and reliably. And you're likely leaving useful reusable functionality gunked up and spread out throughout your application.

Every piece of software actually is a data processing pipeline. You take some input, do some processing of some sort, then output something, usually along with some side effects (network requests, writing files, etc). Thinking about your software in this way can help you design better software. I rarely write code that needs to process large amounts of data, but pretty much any code can benefit from intentional simplicity and design.