Sopranos, Game of Thrones. Basically anything produced for HBO.
I caught the first 2-1/2 seasons of The Wire because of a promotion on Hulu.
It boils down to: I’m a cheapskate.
Sopranos, Game of Thrones. Basically anything produced for HBO.
I caught the first 2-1/2 seasons of The Wire because of a promotion on Hulu.
It boils down to: I’m a cheapskate.
They’ve been separate desktop environments from the start. From top to bottom they share nearly nothing. The compositors, window managers, toolkits and shells are all different.
They also are ideologically opposed. If they merged, which direction would they go? The more feature-rich KDE? Or the more streamlined Gnome? Such a merger would lead to infighting and stagnation.
This is before even talking about the actual code underlying both environments.
I think it’s better for everyone if they stay as two separate projects.
My guess is that some genres are going to be more problematic due to more extensive use of anti cheat. What are some of the games you’re having trouble with?
8pm thru 12am is prime time for streaming. Netflix would need to pivot or go out of business.
Since most phones networks now operate over IP, overnight customer service would break. The US can no longer use call centers in India for daytime call centers.
Batch jobs requiring Internet access can no longer run overnight. Instead they would need to run during the day, tying up bandwidth and CPU for other users. System engineers would need to take this into consideration.
It would be more difficult to coordinate with friends when going out at night. You could no longer order an Uber at 2am if you’re drunk off your ass. DWI events would increase.
Well I guess these aren’t sex stones.
What is a sex stone, you may ask?
It’s a fucking rock.
Yes. The customer doesn’t necessarily know what’s possible or know how to articulate what features they want. I spent one week in a position where I was using my own software for production and immediately made several simple enhancements once I had hands on experience with the expected business process.
Every programmer should go through an exercise like this at least once in a while.