Computing Fails - Revision history

ViciousCarnivore: /* IPv6 Is Badly Designed */

2026-01-19T07:34:03Z

IPv6 Is Badly Designed

2025-06-27T17:47:29Z

Confirmed Fails

2025-06-26T19:50:41Z

Potential Fails

2025-06-26T19:50:04Z

Potential Fails

2025-06-26T19:48:42Z

Windows 11 Incompatibility

2025-06-26T19:48:07Z

Windows 11 Incompatibility

2025-06-26T19:47:52Z

OAuth

2024-12-20T21:07:38Z

Inconsistent flag usage for common commands: chown / scp and the recursive flag

2024-12-20T21:06:59Z

Intel ME

2024-12-20T21:06:23Z

Hidden Files

← Older revision		Revision as of 07:34, 19 January 2026
Line 303:		Line 303:

	It's been said, but if they had made ipv4 5 octets from the start, ip addresses would not have run out for decades. Maybe not ever.		It's been said, but if they had made ipv4 5 octets from the start, ip addresses would not have run out for decades. Maybe not ever.
		+
		+	Also consider that mac addresses are easier to read than IPv6, and much higher than 4 billion combinations (16 ^12, according to: https://stackoverflow.com/questions/44873804/will-mac-address-ever-run-out-of-combinations) It's 48 bits. This brings up the question: What is the best way to represent ip addresses (ipv4, ipv6, mac address, or other), and what is the appropriate number of bits to designate to it.

	==Hidden Files==		==Hidden Files==

@@ Line 9: / Line 9: @@
 * ARM on cellphones. Millions (billions?) of devices that are unusable after 5 years. Landfill.
-* CrowdStrike - Boy, this really "Striked, the IT Crowd / Made the IT Crowd Strike"... Get it?  [https://en.wikipedia.org/wiki/2024_CrowdStrike-related_IT_outages]
+* CrowdStrike - Boy, this really "Striked, the IT Crowd / Made the IT Crowd Strike"... Get it?  [https://en.wikipedia.org/wiki/2024_CrowdStrike-related_IT_outages] If there's one thing they could've changed, it might be to do 'staggered rollouts' instead of all machines at once.
 ==Potential Fails==

@@ Line 15: / Line 15: @@
 * systemd. While it works, it is practically no better than the previous solutions, and is a mess of LOCs.
-* wayland. This may end up making a whole lot of work for people, or it may fix what was wrong with X. See dedoimedo's thoughts on this. I don't know enough to comment.
+* wayland. This may end up making a whole lot of work for people, or it may fix what was wrong with X. See dedoimedo's thoughts on this. I don't know enough to comment. https://www.dedoimedo.com/computers/xlibre.html https://www.dedoimedo.com/computers/wayland-2024.html
 ==Too Much==

@@ Line 15: / Line 15: @@
 * systemd. While it works, it is practically no better than the previous solutions, and is a mess of LOCs.
-* wayland. This may end up making a whole lot of work for people, or it may fix what was wrong with X (whatever that was. I don't know since I don't work with X much).
+* wayland. This may end up making a whole lot of work for people, or it may fix what was wrong with X. See dedoimedo's thoughts on this. I don't know enough to comment.
 ==Too Much==

@@ Line 349: / Line 349: @@
 ==Windows 11 Incompatibility==
-This link is priceless. I took a screenshot since the internet archive 'somehow failed' to save the page. Basically, a logical and sane person asks why his top of the line workstation doesn't work with Windows 11. Imagine paying 5 grand for a GPU CAD workstation only to have to buy another one in 7 years. He is told to use 'rufus', by 'unofficial' support.
+This link is priceless. I took a screenshot since the internet archive 'somehow failed' to save the page. Basically, a logical and sane person asks why his top of the line workstation doesn't work with Windows 11. Imagine paying 5 grand for a (typically GPU CAD) workstation only to have to buy another one in 7 years. He is told to use 'rufus', by 'unofficial' support.
 https://answers.microsoft.com/en-us/windows/forum/all/why-does-windows-11-still-not-support-my-cpu-chips/e2bd3cab-43ca-4f1c-821b-0825ca597666
 [[File:Priceless.png|300px|thumb|right|How to Create Landfill Waste]]

← Older revision		Revision as of 19:47, 26 June 2025
Line 347:		Line 347:
	[[File:Dilbert.gif\|300px\|thumb\|right\|Computers get worse]]		[[File:Dilbert.gif\|300px\|thumb\|right\|Computers get worse]]
	"We need to make it more difficult for users to get their data" - gmail and office365 email monopoly collusion		"We need to make it more difficult for users to get their data" - gmail and office365 email monopoly collusion
		+
		+	==Windows 11 Incompatibility==
		+	This link is priceless. I took a screenshot since the internet archive 'somehow failed' to save the page. Basically, a logical and sane person asks why his top of the line workstation doesn't work with Windows 11. Imagine paying 5 grand for a GPU CAD workstation only to have to buy another one in 7 years. He is told to use 'rufus', by 'unofficial' support. Priceless.
		+	https://answers.microsoft.com/en-us/windows/forum/all/why-does-windows-11-still-not-support-my-cpu-chips/e2bd3cab-43ca-4f1c-821b-0825ca597666
		+	[[File:Priceless.png\|300px\|thumb\|right\|How to Create Landfill Waste]]

@@ Line 330: / Line 330: @@
 There should be an unwritten standard where lower case is used for the most common
 operations. kind of like how there is an unwritten standard for commands to give
-help when you type command -h or --help. Nut there is none. Cases are all over the
+help when you type command -h or --help. But there is none. Cases are all over the
 place. it's a mess. simple things. How many millions of moments have been lost to people
 typing the wrong -r or -R. It adds up over billions of man hours. It's a fail.
@@ Line 336: / Line 336: @@
 Someone really screwed up here.
-A solution, would be for flags to be case insensitive. Is there any reasonable use case
+One solution, would be for flags to be case insensitive. Is there any reasonable use case
 where you'd want to be able to use both -r and -R for different things in the same program?
 It's just confusing.

@@ Line 319: / Line 319: @@
 ==Intel ME==
 See libreboot.org.
 ==Inconsistent flag usage for common commands: chown / scp and the recursive flag==

@@ Line 310: / Line 310: @@
 Hidden files are evil. All ls should be ls -a. They will bite you as often as pcb makers get bitten by incorrect footprints. Its bad design. It will never go away. There's no thinking that you should've been smarter. Lies. Its the human factor. It will always, always bite you someday.
 Hidden files are fundamentally flawed. They will always cause trouble.
 ==Duplication of Work==