You can pry my 1080 from my cold dead hands.

I had an internship 15 years ago where I was forced to write C++ with no internet access. I had to use a programming manual and man pages.

Unironically, yes. That’s not nearly as common sense as you may think. There’s no such thing as idiot-proof steps. To some you may very well be a pro from that alone.

This makes sense. I have a friend from way back in HS who interned there while he was working on his degree who said that cloud services was the priority at the time, and Windows was more just a vehicle that they continued to maintain. That continues to be the approximate temperature of the product and is in line with my expectations.

I never understand this mindset because a person who is technically skilled like this is exactly the kind of person who wouldn’t struggle with Linux.

They’re already the kind of person who would be an excellent Linux user. I can only imagine that, for whatever reason, they’ve grown emotionally attached and are simply too stubborn to consider anything else.

Until the next re-bloating update where your settings get reverted and services re-installed.

Being good at de-bloating (as you may very well be to do that in a few minutes!) is an anti-skill that shouldn’t have to exist.

I could imagine a future where Windows is just a proprietary DE over a Linux system. I don’t think it’s coming anytime soon because of the development cost it would impose, but I don’t see why they would go to such efforts maintaining a system they could get for free if the desktop user base keeps shrinking. They’re just too greedy not to do that. Even the backwards compatibility with Windows software is becoming a solved problem.

Aside from my above rant, the PC is definitely fast becoming an enthusiast/business platform. I opened a retirement account the other day through my smart phone!

Precisely. Windows is a side project for Microsoft now.

Not everything is Chrome just yet. We still have Gecko and Webkit holding on.

It was fun! It worked well when compared with IE back in the day which isn’t saying much, but it was a sensible bedfellow with iTunes and all the Apple mobile support software that was common to run alongside for your iPod. I enjoyed using it as my main browser because it was aesthetically pleasing.

Apple used rigged demos and made false claims about their own technology so outstanding that their own project managers were taken aback by how far behind the features actually were vs. what was pushed. There’s already informal documentaries on the massive internal disconnects within Apple that have lead to poor product testing and stagnation.

I did use Safari for Windows back in the day. It was a product they indeed shipped.

I came here just to write this – I thought we clearly chose to leave behind cybersecurity because education and science are bad.

Then use decentralized links or hashes, which is what IPFS uses to identify content. A character limit doesn’t solve this problem fundamentally. Indeed, it’s been a tough problem to solve for decentralized services.

I’m concerned about the large amount of low quality, vaporware/crypto applications built on IPFS which is the same core technology used here. It’s concerning how many clicks it takes to get technical specs for the underlying work, like libp2p for the network layer, which itself espouses only vague ideas on its main website that seems to focus a lot more on presentation than technical merit. Even the GitHub admits that the spec that most of these apps are relying upon is, well, unspecified.

Your project source downloads and runs an executable. That’s a little bit SUS; it would be much better if you compiled/built this core code as part of your build process, else, it’s not much in the way of source code, no? But, it works. It seems to delegate just fine, and few understand how to actually talk IPFS directly. But, this is the most important part!

I think the biggest tell that IPFS borders on vaporware is that there’s very little discussion about concrete specifications and the main problem faced by all DHTs: how you get your data to actually stay hosted on the network over time. These ideas are not new, and you may be better served building your app on technology that has spent vastly more time understanding the fundamental problems.

https://specs.ipfs.tech/

This is how you write a spec without actually writing a spec. And I’ve written a lot of specs.

https://geti2p.net/spec

This is how you write a spec. Excruciating detail of what actually gets sent over the wire at different levels of the design starting from the very bottom.

Anyway, just my 2c. It’s cool you’ve got functionality at this level and that’s commendable, but I feel it’s built on shoddy foundation of an immature technology. At least it should be easy to migrate to something else in the future as the distributed technology is offload to a separate binary anyway.

Note: Various edits for clarification and to ensure I focus on the code and not the human.

This is exactly what some of my extended family uses because there’s literally no other option. Not even cellular.

This isn’t even up in the mountains or something. This is just rural Alabama where kids are struggling to do homework because they just don’t have access, and it all but guarantees that their technology skills will remain woefully outdated.

I remember when they had DSL not that long ago and I would turn off updates on everything because it was a complete waste of time to attempt.

I ask AI to avoid all the AI slop search results I’d have to sift through when I could get my slop delivered directly.

And here I am adopting abandoned ports on FreeBSD and packaging applications that I didn’t even write as a hobby.

Aero the Acrobat for GBA.

Cheap Sonic ripoff? I loved that game. Spent many childhood hours and AA batteries playing it and learning every corner of every level.

We have a dog daycare center around here called Pound Town.