| General > General Technical Chat |
| [Banter] What is the worst software you have used for its price? |
| << < (22/32) > >> |
| Zoli:
--- Quote from: free_electron on May 24, 2022, 04:53:10 pm ---... One of the founders is still in dispute about a piece of beach he illegally owns (or doesnt) --- End quote --- He owns the access to the beach; this kind of behaviour is worse then just fighting over the beach in question, IMNHO. |
| bd139:
--- Quote from: mansaxel on May 24, 2022, 08:39:55 am --- --- Quote from: bd139 on May 24, 2022, 06:45:20 am ---Regarding kexts I really think those need to die. Windows is doing the same to some degree as well. It stops the whole “relabel generic serial adapter with different vendor code” garbage. We have USB standard device classes and AirPrint. No drivers needed! --- End quote --- This is not for USB serial (but yes, it used to be. Now they've got all the ususal suspects in-kernel, which is second best to device classes). It's for arcane but very useful things like network file systems. Ever heard of OpenAFS? It is a horrible concoction, slow and requires a level 7 magician juggling lots of moving parts in reasonable lockstep. It also is 1000x better than any other network file system. And since I am a grumpy old Unix greybeard, I happen to think that the current "API means a badly documented HTTPS-carried pile of JSON poo to a load balancer (implying broken caching as well, for lulz) because distributed eventual consistency is hard" trend should be taken out and shot, I think that the classic file system model still wins. --- End quote --- Problem with filesystems is they only deal with streams of bytes. Problems are slightly more complicated than that as are transactions, consistency and locking. Not to mention disconnected devices and latent consistency. Agree with your assertions about APIs however. HTTP and JSON are the wrong solution. I probably went on about this before but I am partially through implementing something completely new to bridge these two problems. It's long, complicated and painful and my motivation is lacking at the moment :-DD |
| mansaxel:
--- Quote from: free_electron on May 24, 2022, 04:53:10 pm --- --- Quote from: mansaxel on May 24, 2022, 06:13:21 am ---Solaris manpages written by people who would rather write a dissertation using Complicated Words than tell people how to run the fucking program. --- End quote --- well they are all Stanford alumni , so they thumb their nose at you. talk about an evil company.... giving away their hardware to universities so students get used to it and then demand the same machinery (waaaay overpriced) when they go to work somewhere. --- End quote --- SUN hardware and software, excluding the SysV doldrums from 5.1 through 5.6, and not talking so much about the low-end SunBlade machines with IDE disks, was mostly excellent. The manpages sometimes are horrible. And their attempts at building a system for patching the OS did leave something to be desired, but it could mostly be circumvented. A Java GUI program that insisted to be run on the actual console, wouldn't that be a splendid idea for a server OS that runs on Real Computers? (A Real Computer runs Unix, is natively Network Byte Order, and has a serial console at 9600 8n1, that isn't an afterthought which will only do 83% of what the graphical console, if it even exists, can do. This obviously excludes anything X86 from being a Real Computer) This is all completely irrelevant now, because Oracle bought them and turned it all to shit. --- Quote from: free_electron on May 24, 2022, 04:53:10 pm ---One of the founders is still in dispute about a piece of beach he illegally owns (or doesnt) --- End quote --- Rich people, regardless of which software company they founded / funded (or not), will do these things. It is irrelevant to the discussion and smacks of axes to grind. Let's save that for Larry Ellison, shall we? |
| mansaxel:
--- Quote from: bd139 on May 24, 2022, 10:08:18 pm --- Problem with filesystems is they only deal with streams of bytes. Problems are slightly more complicated than that as are transactions, consistency and locking. Not to mention disconnected devices and latent consistency. --- End quote --- I'm going to be even more back-asswards and state that RDBMS is far from dead, and has solutions to this. But it is not fancy to use it, because developers have not been allowed in to mess with it, and therefore they insist on using glorified BDB hashes instead. --- Quote from: bd139 on May 24, 2022, 10:08:18 pm ---Agree with your assertions about APIs however. HTTP and JSON are the wrong solution. I probably went on about this before but I am partially through implementing something completely new to bridge these two problems. It's long, complicated and painful and my motivation is lacking at the moment :-DD --- End quote --- I'd be delighted to read more when you're bored with moving house and have taken that up again. |
| bd139:
--- Quote from: mansaxel on May 24, 2022, 10:31:55 pm --- --- Quote from: bd139 on May 24, 2022, 10:08:18 pm --- Problem with filesystems is they only deal with streams of bytes. Problems are slightly more complicated than that as are transactions, consistency and locking. Not to mention disconnected devices and latent consistency. --- End quote --- I'm going to be even more back-asswards and state that RDBMS is far from dead, and has solutions to this. But it is not fancy to use it, because developers have not been allowed in to mess with it, and therefore they insist on using glorified BDB hashes instead. --- End quote --- Yes. One of my solutions I have implemented before was actually a disconnected SQLite replicated to a master DB. The replication was over HTTP / JSON though so you won't like it :-DD. Ironically this is the same thing Apple use for their cloud stuff (Core Data) even though I didn't know at the time when I blindly reimplemented everything they did. I use Apple's API every day for tasks, notes, music and spreadsheets and it works quite well. --- Quote from: mansaxel on May 24, 2022, 10:31:55 pm --- --- Quote from: bd139 on May 24, 2022, 10:08:18 pm ---Agree with your assertions about APIs however. HTTP and JSON are the wrong solution. I probably went on about this before but I am partially through implementing something completely new to bridge these two problems. It's long, complicated and painful and my motivation is lacking at the moment :-DD --- End quote --- I'd be delighted to read more when you're bored with moving house and have taken that up again. --- End quote --- I'll stick it on github when I get a chance to remove all the embarrassing bits and document it. It has evolved a cranky Forth like programming language since I last mentioned it which allows you to distribute code with workload rather than compile it into node controllers like the first version. Eventually it'll evolve into a mutant of a distributed lisp machine and kubernetes and then I'll look like an idiot :) |
| Navigation |
| Message Index |
| Next page |
| Previous page |