Hacker Newsnew | past | comments | ask | show | jobs | submit | Borg3's commentslogin

Normally, its the one who understand technology, can control it. Unfortunately, its not the case anymore. Stuff got unnecessary complex and bloated, hard to grasp it alone. Also, now AI plays the new role too.

Dark times ahead...


The technologists can control it, the moment they can remove that stupid disclaimer saying that AI can make mistakes.


What's stupid about the disclaimer?


It basically says "we have no control over it", and "we don't know how it works".


Both of those things happen to be entirely true, though.


Yes, that doesn't make it less embarrassing.

My point remains: they can control it if they can control it. Because right now they can't even take responsibility for it.


And if someone without billions of dollars in backing released a product like that they'd actually be held responsible for the consequences.

Sure but theres a level of uncertainty being expressed for a paid service that you don't see elsewhere.

Imagine if every time you booked an uber it was like "your drive may crash the car". Or whenever you ate at a restaurant, the waiter said "there is a chance the chef will poison you". Or your bank statement said something like "these numbers may be wrong".


Exacly. And I love its written in C. You need to extend Ruby w/ your favorite Graph Library? You just slap .c glue code and vioala it works like a charm!


Nah, its not rose tinted glasses. Win2000/Win2003 were amazing. I still run Win2003 because it just workz. GUI is great, it snappy, I have all the tools to tinker here and there.. Leaked SRC code helps tiny bit ;)

Win7 wasnt that bad, you still could set classic GUI. If they only kept it like this and plow money to improve kernel...


In 2012, I was working for a company that did all the development for its Windows clients on an ancient version of Visual Studio running in a Windows 2003 VM, and I discovered that the Windows 2003 running in a VM could transfer files over the network faster than Windows 7 running on bare metal. I feel like transferring files over the network has been horrible in Windows ever since. Transferring over USB was often horrible as well, but that seems somewhat better now.


Hmm I wonder how stable it is.. It cannot render correctly Window control buttons (Minimize, Maximize, Close). If it fails on such basic task, I wonder where it crashes...


That's a graphics driver problem. Fairly common to see when running Windows 9x/Me under QEMU.


Hah, amazing.. And unresolved for all those years?


There's not a whole lot of interest in making Windows 9x run well on QEMU.

These days especially, it's better to just use 86Box for those operating systems.


We are reaching society shown in "Johny Mnemonic" movie.. So much (useless) information around that people gets overloaded. I barely read anything these days on NH, too much (crap) information. I skim and only read stuff that is very close to my interest.

I used to read a lot more in the past, not the case anymore..


Well, half the articles I see posted now, the author didn't even bother to write themselves, but outsourced to a machine.

I've heard this sentiment: "If you didn't even bother to write it, why should I bother to read it?"

But often there is real value there, and I sometimes force myself to cringe my way through the GPT-isms, to find the gems buried within.


It works exacly as it was designed to work.. GIT as VCS.. Version Control System.. for text code sniplets. It can handle small binary blobs just fine.

If you need (D)VFS aka Distributed Versioned Filesystem, grab right tool. Or write one.

This is exacly way I wrote DOT (Distributed Object Tracker). Its pure DVFS repo manager, to handle binary blobs and that it.. Nothing more.

People complaining about GIT not working well w/ big data just handling GIT wrong. Linus said it from the begining, its NOT tool for such datasets. Just move along.


http://borg.uu3.net/~borg/?ipv6

Now, if only those people who designed IPv6 were smarter.. Hex aint that bad, LONG hex addresses are pain to use.

Now, lets say you have LAN like this [::1:0:0/56]. So, ::1:0:24 is easy to remember right? Managable? right?.. Also, bonus for :: shortening is, you immediatly know what are you dealing with, ::1 is loopback, ::1:1 is LL, ::1:0:1 is LAN.. everything else is Internet.

The truth is, IPv6 is really 64bit, the other 64bit part is just randomish node address...


> The truth is, IPv6 is really 64bit, the other 64bit part is just randomish node address...

So anyway it gives 128bits in total, 64 for network and 64 for node.

But I wish there was a better way to write just the local node part and global part being taken automatically.


10:14:05 up 2336 days, 22:17, 4 users, load average: 0.00, 0.00, 0.00



Connections... It was always like this..


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: