I switched back to Windows 7 from 10—here’s my thoughts so far

It has been exactly a week since I installed Windows 7 Ultimate onto my daily driver laptop. There’s some parts about it I like, some I don’t, but for now, it seems that I’ll be staying on it.

Pros

I like a lot of parts about Windows 7, arguably more than the things I like about Windows 10 or any newer Windows operating system

Speed

Windows 7, at least on my laptop, is able to keep my pace. Windows 10 would continuously drag its feet whenever I tried to do the most basic of tasks.

For example—logging in. On Windows 10, I would have to wait nearly 16 minutes combined just to even begin using my computer. That’s atrocious, especially for a computer that shipped with the operating system. This was already after I had cut out bloat where possible, such as switching to a local account, removing HP bullshit, and killing anything non-essential to the OS. However, even that isn’t enough with the horrendous amount of background processes 10 kickstarts for no reason. Windows 7, on the other hand, only takes a combined 1 minute for me to log in. I don’t have to start it up early like you’d heat up a car in winter before driving. I boot it up, and I get to work (or whatever I am doing on my computer).

Another example is UWP apps. Windows 10 (and lets be honest, most modern apps) expect you to have a fully specced out workstation or gaming computer. That isn’t even a concept when it comes to my laptop. Nada. No no. This means that most apps will pretend they are running on a regular old potato, when they in fact are running on a “fully capable” laptop. The UWP Windows Settings app roleplays as a sloth, and my computer gets hot enough to toast an egg. That’s not a computer issue, that’s an optimization issue. Since UWP doesn’t and literally cannot exist on Windows 7, you get the older native apps that actually run decently. It’s not like these apps are missing much functionality, anyways.

Looks

This definitely isn’t a new point of discussion, I talked about this in my “Why Windows 7 is better than newer Windows versions” blog post. However, it’s just too big of a point to ignore or avoid. Windows Aero is beautiful, and it is a great showcase of the features and functionality Windows 7 has to offer—certainly more than Windows 10 or 11 exhibit, anyways. Even the Windows Basic theme isn’t necessarily bad, just not exactly preferable in comparison to the Aero theme.

Every icon just has this sense of realism to it, and every application just feels right at home on 7. Hell, even just get a modern app like OBS, slap on the light Aero theme to it (yes you can do this by setting the theme to “System”), and it looks relatively decent and fits in well, even if not as well integrated as, say, the Windows Live Essentials pack or the pre-installed applications. With the Aero theme, there’s no app that doesn’t look at least decent.

There’s not much more for me to say that I haven’t said already. Windows 7 simply looks great, that’s that.

Gaming

This may come as a surprise to you, but Windows 7 is actually great for gaming—or rather, retro gaming.

There’s actually some fair reasoning behind this, most of it having to do with the backend of the operating systems, not what the user actually ends up seeing. Windows 10 has mostly killed retro gaming on itself, unless you are under very specific circumstances. This is because likely in an attempt to “streamline” the process of running apps and games, most older DirectX stuff was ripped out, even the parts that weren’t full blown DirectX frameworks. Additionally, a lot of the older .NET things, like .NET framework 2.0 or 3.0, were just completely removed, further battering the corpse of what might have been retro gaming on 10 natively. Some other things, such as a replacement of long-standing tools other games used being launched into orbit, just completely break older games on Windows 10.

Windows 7, on the other hand, honors these games (for the most part). Even if it itself cannot exchange the correct things, it’ll guide the game in the right direction so that it does work and doesn’t completely crumble to pieces. This is what allows somewhat ancient games like Comanche 4 to run natively, even if a little buggy. This is a lifesaver in the case of games such as Half Life (unpatched, not the tampered version on Steam today), The Sims 1, and GTA: Vice City. All of these would be ripped to pieces on 10.

Simplicity

It was part of the original advertising campaigns: Windows 7 is simple. Not too simple to the point where you can’t do anything productive on it (ChromeOS ahem ahem), but not so sophisticated that it alienates half of the userbase that came to it for something that just… works. Balanced. You buy the shiny laptop with 7 preinstalled, you plug it in, set it up, and done. A poweruser? Build your own rig. Get a Windows 7 install disk. Customize it to your heart’s extent. I’m gonna be honest, I genuinely don’t think there will ever be another Windows OS quite like 7.

Cons

Drivers

Do you want to know what isn’t simple? Drivers! Drivers are a pain in the arse nowadays, in terms of Windows 7.  They’re like a necessary evil—your computer is convinced that it is secretly running with an Intel 486 chip and a Big Mac as a GPU without them, but finding them can sometimes feel impossible. Most hardware past like 2019 that had Windows 7 drivers just started dropping like flies. Now, with real gaming rig-level hardware, it’s nearly impossible to make the two be kind to each other without straight up downgrading some parts or hacking together a custom driver that has a 50% chance of working, 50% chance of bricking your install until you enter Safe Mode. Even on older hardware that isn’t necessarily that old, finding drivers that work, let alone bring Aero to the table, is all holy hell. Tools lke DriverIdentifier have made this process a bit quicker, but it is stll so, so annoying.

Compatibility

You probably saw this coming from a mile away, but here it is. Compatibility. It is miserable on Windows 7, when you’re trying to run newer apps and games. Saw that shiny new game on the Steam Store page? Suck it up, Windows 10 support and higher. Java SDKs newer than version 17? Forget it. New-ish apps in your optimized workflow? Sorry, find a Windows 7 alternative. It is pure pain. Most of my workflow already supported Windows 7, but if yours didn’t, you were just out of luck.

My thoughts and a conclusion

I personally think that for the issues, there’s always two benefits to Windows 7, which is why I will be staying on it. Most of the issues are just things you work around, anyways—you get your drivers, you’re done. No more time wasted on the involuntary scavenger hunt. Same deal with the apps. Take from this what you will. If you’re a Linux bro that couldn’t care less about Windows, keep not caring. If you’ve never even heard of me before and are intrigued about my content, read my other posts. If you were contemplating the switch, use this as guidance. I don’t care. I just don’t want this to be a big ol waste of time, there needs to be some value you get from this post. Anyways, if you want more tech related extravaganzas, tune in to the CheeseBlog for another post. Cya!

The pros and the cons of serverless architecture

 Heyo! This was a thought that popped into my mind when I was thinking about apps I could make, and I realized that this would actually be a pretty solid blog post. 

 This isn't usually a decision most developers have to make, as it is almost always clearly cut out. Need to fetch or process stuff from a database? Use a server. Making something simple like a notes app or a calendar? Easy peasy, that goes into serverless. However, there's a few edge cases that force you to make this decision, so I'll help explain what benefits you'd gain from it and the cons you'd gain from it.

For anyone new in the scene of programming, serverless architecture is when you develop an app that does not use a server. Simple, right? All computation needed is done entirely on the client, which can save a TON of money, due to the costs of a dedicated server being super expensive. Whether you're using a server host such as Linode (not sponsored) or even self hosting, costs can rise quickly. Serverless architecture eliminates that extra cost, only leaving you with the cost of hosting the client, which, depending on how much research you do and the type of app you're making, can be free.

 Now, let's start with the pros. I already went over one of them: the cost. If you skipped over that section, I'll do a quick summary: servers cost hella money, no matter what form you choose them in. Serverless architecture doesn't use that money, letting you allocate it to more important things like hosting the client or paying devs for making the app, if you've got a team you pay. Another useful thing that you benefit from it is automatic scaling. If you're a type of person that does minimal feature launches for your projects or products and then slowly expands (think the way Google releases products), this can actually be really useful. The app grows with you, but with a server-based architecture, you'd be forced to periodically upgrade servers which would be really expensive, or get a massive server off the bat, which is insanely risky (what if your product is a total flop?), because then you'd just.. have it. Not much to do with it, unless you decide to split it between projects. Additionally, serverless architecture just frees up your hands and space on the clock. You don't have to spend any extra time dealing with maintenance because a storage unit died, you don't need to investigate why it is returning garbage data with tested-okay code, etc etc. You just deal with the client, and that's it. More time to work on development, more focus on what you need focusing on, so on so forth. Next, the cons.

 A major con about serverless architecture is just how much it relies on the device it is running on, and there isn't exactly any other device to relieve resource usage because all of the code is being ran on the client device. It makes the bold assumption that whatever you're doing and whatever you're using is on the same firmware as the device(s) you test it on, and that the computer is even powerful enough to run it. Please, tell me the last time you saw Minecraft with full shaders running on a Galaxy S2 smartphone (the answer: you probably haven't, let alone at the standard 60fps/120fps of the phone). Instruct me on how to get Firefox 115 running on Windows 98 SE. This is one of the biggest reasons for why servers exist: they do the bulk of the computation. YouTube would NOT be able to run the algorithm everyone tries to manipulate for views without their servers with 10 exabytes of storage for videos with their accompaning metadata and above-the-line processors. And not to mention, serverless applications make exploiting them for personal gain so much easier to do, because exploiters and decompilers will take your program in its full and rip it to shreds just to find a single vulnerability. Better make sure it doesn't connect to the internet!

 Anyways, I had a ton of fun writing this, but that is to be expected when you haven't written any blog posts in over half a year. I really hope you learned at least something decent or useful from this, because that'd make me happy (and maybe attract more viewers to my blog if you REALLY liked it). For more tech related insights and accidental forkbombs, tune into the CheeseBlog for more posts just like this. Cya!

Why this blog has been dead and my plans for the future

Heyo! I'm well aware that I haven't posted anything in multiple months. This wasn't really my choice, but I'm going to explain what has been happening in my life that has been stopping me from blogging.

Number one: school. This may sound like a weak or fake excuse, but it is very real to me—I've been drowning in classes and homework, and with a household that isn't very forgiving when it comes to making space on the clock, I just haven't had the opportunity to finish my work, let alone write a blog post. I'm not really planning to drop from any classes, so I'm just going to have to stick it out until the end of the year.

Number two: my computer finally croaked. Dunno what caused it, but the laptop that I've been using for pretty much all of my work everywhere that is digital, just decided to die. Thankfully, all of my data remains, but the laptop doesn't. I'm in the process of backing up everything to an external drive and getting a new Windows 7 laptop, but tight budgets make this very difficult and time consuming. Very unfortunate, but oh well. At least everything is there, right?

There's a few more things, but I'm not going to get into those because they dig a little too close into my personal life. I'm sorry that I haven't really done anything here, and I hope you understand. 

In the meantime, I'm trying to get a decent-ish setup on my phone so I can at least try to blog on here. Still, don't expect much.

If you really want to see new content from me, I'm trying my best to still get new stuff onto my site, the cheese spot, so go check that out. Once I finally fix everything and return to normal routine, remember to check out the CheeseBlog for more tech related shenanigans. Cya!