Technical users that are comfortable at a command line often use WinGet these days. It works in Windows Sandbox too; you just need to manually install it.
dan
joined 2 years ago
Wow, there really is a game for everything.
I'm glad I'm not the only person that does this.
Usually, feature branches mean that all the work to implement a particular feature is done on that branch. That could be dozens of commits and weeks of work from several developers. The code isn't merged until the feature is complete. It's more common in the industry compared to trunk-based development.
My previous employer had:
- Feature branches for each new feature.
- A dev/trunk branch, where features branches were merged once they were done.
- A beta branch, branched from dev once per week.
- A live/prod branch, branched from beta four times per year.
This structure is very common in enterprise apps. Customers that need stability (don't want things to change a lot, for example if they have their own training material for their staff) use the live branch, while customers that want the newest features use the beta branch.
Bug fixes were annoying since you'd have to first do them in the live branch then port them to the beta and dev branches (or vice versa).
On the other hand, feature flags mean that all the code goes directly into the trunk branch, but it's turned off until it's ready. A basic implementation of feature flags would be a static class with a bunch of booleans that get checked throughout the code, but they're usually dynamic so a misbehaving feature can be turned off without having to redeploy the code.
Some codebases use both feature branches and feature flags.
It caters more for a linear workflow, though. So modern large teams won't find joy with SVN
For what it's worth, I work at a FAANG company and we don't use branches at all. Instead, we use feature flags. Source control history is linear with no merges.
All code changes have to go though code review before they can be committed to the main repo. Pull requests are usually not too large (we aim for ~300 lines max), contain a single commit, aren't long-lived (often merged the same day they're submitted unless they're very controversial), can be stacked to handle dependencies between them ("stacked diffs"), and a whole stack can be landed together. When merged, everything is committed directly to the main branch, which all developers are working off of.
I know that both Google and Meta take this approach, and probably other companies too.
The bottom picture should be SVN. I miss incremental revision numbers.
Are any drink manufacturers fully vertically integrated? I think most of them outsource can and bottle manufacturing, even big manufacturers like Coca-Cola. They're in the business of making drinks, not making cans and bottles (which don't have any special features compared to cans and bottles used by other companies), so it makes sense to use a vendor that has experience in that area.
Generally, if it's just a plain word or something you can read easily, then it's safe to keep it. If it's a jumble of seemingly random letters, it's probably a tracking code of some sort.
This is kinda true but also kinda fear mongering. UTM parameters are just to track where you clicked the link from. They're usually not dynamic, and don't contain anything about you personally. The example in the screenshot utm_source=newsletter is probably added to all links in a company's newsletter email, so they can tell that people get to the page via the newsletter.
In addition to this, a lot of movies and TV shows are going to use the same DRM mechanisms, whereas with games it's different for every game. The developers (both of the DRM systems and of the game) learn what works and what doesn't work and adjust the system for their next game.
Edit: Also, games often have anti-piracy measures hidden throughout the game, so whoever is cracking the game likely has to play the game quite a bit to ensure they've caught them all.
This is how I handle it for most software: Read (or at least skim) the changelogs for all minor and major versions between your current version and the latest version.
If you're using Docker, diff your current docker-compose to the latest one for the project. See if any third-party dependencies (like PostgreSQL, Redis, etc) have breaking changes.
If there's any versions with major breaking changes, upgrade to each one separately (eg. 1.0 to 2.0, then 2.0 to 3.0, etc) rather than jumping immediately to the latest one, as a lot of developers don't sufficiently test upgrading across multiple versions.
Take a snapshot before each upgrade (or if your file system doesn't support snapshots, manually take a backup before each upgrade).
...or just don't read anything, YOLO it, and restore a snapshot if that fails. A lot of software is simple enough that all you need to do is change the version number in docker-compose (if you're using Docker).
I have a 10Gbps internet connection. On a system with a 10Gbps Ethernet card, I can get ~8Gbps down and ~6Gbps up:
I'd expect this to easily max out a 2.5Gbps network connection. However, while the upload is maxed (or close to it), I can only ever get ~1.0 to 1.5Gbps down:
Both tests were performed on the same system. The only difference is that the first one uses a TRENDnet 10Gbps PCIe network card (which uses an Aquantia AQC107 chipset) whereas the second one uses the onboard NIC on my motherboard (Intel I225-V chipset).
This is consistent across two devices that have 10Gbps ports and two devices that have 2.5Gbps ports.
I'm using an AdTran 622v ONT provided by my internet provider, a TP-Link ER8411 router, and a MikroTik CRS312-4C+8XG-RM switch. I'm using CAT6 cabling, except for the connection between the router and the switch which uses an SFP+ DAC cable.
I haven't been able to figure it out. The 'slower' speeds are still great, I just don't understand why it can't achieve more than 1.5Gbps down over a 2.5Gbps network connection.
Any ideas?
I couldn't find a "Home Networking" community, so this seemed like the best place to post :)
My house has this small closet in the hallway and thought it'd make a perfect place to put networking equipment. I got an electrician to install power outlets in it, ran some CAT6 myself (through the wall, down into the crawlspace, to several rooms), and now I finally have a proper networking setup that isn't just cables running across the floor.
The rack is a basic StarTech two-post rack (https://www.amazon.com/gp/product/B001U14MO8/) and the shelving unit is an AmazonBasics one that ended up perfectly fitting the space (https://www.amazon.com/gp/product/B09W2X5Y8F/).
In the rack, from top to bottom (prices in US dollars):
- TP-Link ER8411 10Gbps router. My main complaint about it is that the eight 'RJ45' ports are all Gigabit, and there's only two 10Gbps ports (one SFP+ for WAN, and one SFP+ for LAN). It can definitely reach 10Gbps NAT throughput though. $350
- Wiitek SFP+ to RJ45 module for connecting Sonic's ONT (which only has an RJ45 port), and 10Gtek SFP+ DAC cable to connect router to switch.
- MikroTik CRS312-4C+8XG-RM managed switch (runs RouterOS). 12 x 10Gbps ports. I bought it online from Europe, so it ended up being ~$520 all-in, including shipping.
- Cable Matters 24-port keystone patch panel.
- TP-Link TL-SG1218MPE 16-port Gigabit PoE switch. 250 W PoE power budget. Used for security cameras - three cameras installed so far.
- Tripp Lite 14 outlet PDU.
Other stuff:
- AdTran 622v ONT provided by my internet provider (Sonic), mounted to the wall.
- HP ProDesk 600 G5 SFF PC with Core i5-9500. Using it for a home server running Home Assistant, Blue Iris, Node-RED, Zigbee2MQTT, and a few other things. Bought it off eBay for $200.
- Sonoff Zigbee dongle plugged in to the front USB port
- (next to the PC) Raspberry Pi 4B with SATA SSD plugged in to it. Not doing anything at the moment, as I migrated everything to the PC.
- (not pictured) Wireless access point is just a basic Netgear one I bought from Costco a few years ago. It's sitting on the top shelf. I'm going to replace it with a TP-Link Omada ceiling-mounted one once their wifi 7 access points have been released.
Speed test: https://www.speedtest.net/my-result/d/3740ce8b-bba5-486f-9aad-beb187bd1cdc
Edit: Sorry, I don't know why the image is rotated :/ The file looks fine on my computer.
view more: next ›
Aren't they at least hashed, so WinGet can verify that the package hasn't been tampered with?