It’s not just one generation receiving an education vs. another one that didn’t. It’s that the platforms the generations used are fundamentally different.

Gen X / Millennials grew up with Macs and PCs, computers that were fundamentally not locked down. You could install any software you wanted. You could modify the OS in many ways. DRM wasn’t really a thing in general, and there were almost always easy ways around it.

Gen Z / Gen Alpha grew up mostly with cell phones. The phones they had are much more powerful than the PCs from 20-30 years ago, but they’re incredibly locked down. The only applications you’re allowed to use are the ones that Apple / Google allow on their app stores, unless you root your phone which is a major risk. It’s very hard to even load up your own audio files, movies or images let alone “dodgy” ones. DRM is everywhere, and the DMCA means you risk serious prison time if you bypass access controls.

Gen X / Millennials grew up at a time when there were still more than 5 tech companies in the world, and the companies out there competed with each-other. There were plenty of real standards, and lots of other de-facto standards that allowed programs to interoperate. Now you’re lucky if you can even use an app via its website vs. using a required app.

It’s not just a difference in education. It’s that companies have gained a lot more power, and the lack of antitrust enforcement has made for plenty of walled gardens and “look but don’t touch” experiences.

That’s not really a common situation though. Sure, people might use the BSD license on something they did as a hobby, or just to learn things. But, the scenario described here is more like:

A group of people all have the same little problem, and they work together to come up with a solution for it. They solve the main problem, but their solution has a few rough edges and there are similar problems they didn’t solve, but they’re not motivated to keep working on it because what they have is good enough for their current needs. So, they put out some flyers describing how to do what they did, and inviting anybody who’s interested to keep working on improving their fix.

A company comes along, sees the info, and builds a tool that solves the problem but not quite as well, and for a small fee. They spend tons of money promoting their solution, drowning out the little pamphlet that the original guys did. They use as much IP protection as possible, patenting their designs, trademarking the look and feel, copyrighting the instructions, etc. Often they accidentally(?) issue legal threats or takedown notices to people who are merely hosting the original design or original pamphlets.

Maybe the original inventor didn’t get screwed in this scenario, but you could say that the public did.

This headline sounds a lot funnier if you assume “it” means Signal, like I did.

Theoretically, this could hit Linux too. You could run a Linux kernel mod containing closed source stuff from a third party vendor which causes the system to kernel panic. The difference is really cultural. Linux admins would howl at that kind of setup, whereas for Windows it’s more standard.

Code review, QA team, hours of being baked on an internal test network, incremental exponential roll out to the world, starting slow so that any problems can be immediately rolled back. If they didn’t have those basics, they have no business being a tech company, let alone a security company who puts out windows drivers.

No they won’t, not if they’re in the slightest bit competent.

Blameless post-mortem culture is very common at big IT organizations. For a fuck-up this size, there are going to be dozens of problems identified, from bad QA processes, to bad code review processes, to bad documentation, to bad corner cases in tools.

There will probably be some guy (or gal) who pushed the button, but unless what that person did was utterly reckless (like pushing an update while high or drunk, or pushing a change then turning off her phone and going dark, or whatever) the person who pushed the button will probably be a legend to their peers. Even if they made a big mistake, if they followed standard procedures while doing it, almost everyone will recognize they’re not at fault, they just got to be the unlucky person who pushed the button this time.

Doubleclick has been Google for decades now. The difference is that (at least these days) most companies wouldn’t accept it if doubleclick ads had obnoxious pop-ups. But, they choose to have a Google sign-in form that has an obnoxious pop-up. Yes, it’s annoying that Google made an annoying login pop-up. But, much worse is that places like Reddit choose to go with that obnoxious pop-up instead of saying “we don’t want to force that on our users”.

What I mean by it not being a Google thing is that it doesn’t just appear there on its own, like it might if it were a Doubleclick ad or something.

This is something that companies like Reddit see and think “Yes, I want that obnoxious thing on my site”.

Worth noting, this isn’t really a Google thing. It’s something other websites do to allow you to login with various other credentials: Facebook, Google, Amazon – Twitter used to be common. It’s just that Google is obnoxious because when say Reddit allows you to login with your Google account, the login widget Google uses is an obnoxious pop-up.

The one freedom the GPL removes is the freedom to be a leech. If you’re linking to GPL code, you are agreeing to follow the same rules as everybody else who has contributed to that code. Nobody gets a pass

Work for hire is a completely different situation. You have to accept the terms of whoever’s paying you to do the work.

This comic is more about someone doing something as a hobby project, or writing their own software not under someone else’s direction, where they have full freedom to choose their own license.

That’s like saying “Watch my new TV show, it’s better than the other shows because our scripts are printed on an Epson printer!”

When you view or edit a text (.txt) file in a text editor like Notepad, you’re most often opening a file in ASCII encoding that uses the ASCII binary values for common letters, numbers and punctuation. The only values allowed in that kind of file are lowercase letters, uppercase letters, numbers and punctuation.

You can also view or edit binary files, like executables (.exe), but you typically need a hex editor. If you tried to open a binary file in a plain text editor it wouldn’t know how to handle all the binary values that are not part of the standard ASCII set of letters, numbers and punctuation.

Hex editors show the data in hexadecimal format. They convert the binary data to numbers from 0 to 15 where the numbers 10 to 15 are replaced by the letters A to F. Often to make it clear people are talking about the hex number they add “0x” in front of the number. So, 0 becomes 0x0, 9 becomes 0x9, 15 becomes 0xF, 16 becomes 0x10, and 255 becomes 0xFF. This is an efficient way for people to work with binary data because 16 is 2⁴ or 222*2.

Within binary files, there will still be a lot of sections that are in ASCII. For example, any error messages that have to be printed out for the user to see, like “this program cannot be operated in DOS mode”.

Razor 1911 is an infamous cracker group that has been around for decades. They often “sign” the programs they crack by putting “Razor 1911” inside the files, in a way where you can see it if you open it with a hex editor, but so it doesn’t affect the program.

So, what this is suggesting is that a program that Rockstar has released on Steam is not something they built themselves, but they’re actually distributing a cracked version that was released by Razor 1911.

Some of the low hanging fruit would just be to pick one pronunciation of “oo” and stick with it:

• book
• blood
• floor
• brooch
• boot

The problem is that English has far more vowel sounds than vowels. And that’s without even having certain sounds that are common in other languages like “ü”.