On Sat, 5 May 2018 01:31:58 +0200 marc <marc...@welz.org.za> wrote: > > > On top of that I'll only buy hardware that can be free software > > > down to the bios. It should be nothing to them what runs in the > > > bios, so I'll wait and see if they can be more flexible there > > > (for however long it takes). > > > > I've been trying that for a while now, but my server is starting to > > fail. > > > > It may not be an option unless I want to get out of computing > > altogether. > > If one peers closely enough at the various speculative > execution bugs alluded to in this thread, and the horrible > modern web-browser in the thread next door, one realises that > they are just different facets of the same problem. > > If browsers were simple and didn't contain javascript > interpreters, then the CPU bugs wouldn't be that serious on > a single user machine as it would be much more difficult to > get hostile code to run on the CPU. > > In the same way, the biggest memory and CPU hog on a modern > computer is the web browser - it is not uncommon to have > browsers consume multiple gigs of RAM to display data which > contains a few hundred bits of actual information (train > time-table, bank-balance, tomorrow's weather forecast). > > So if were not for the browser a PC from the last century would > do, and that would mean that a simple, single core CPU without > wild speculative execution modes, insane pipelines, > signed microcode or management engines would suffice - the kind > that enthusiasts occasionally build in verilog, and the role > that maybe RISCV will fill more comprehensively. > > So maybe don't give up on computing, nor give up on the > internet, but give up on the web. Maybe we should all host > things gopher, ftp or bittorrent and related protocols... talk > via irc or smtp, not web forums. Read mail with an actual mail > client, not a web frontend.
I think you're painting all Javascript with the same brush. See my pricing page: http://troubleshooters.com/utp/courseware_cost_calculator.htm Loads almost instantly. Does exactly what is needed. Replacing it with a calculator on the back end would require a send to the back end and (remember, no Javascript, no AJAX) the back end sending an entire page to the browser. Don't blame Javascript because some programmers think it's hip to throw in fifty layers of abstraction to get "just the right look" without "reinventing the wheel." Blaming Javascript for force fed pig websites is like blaming C for systemd. SteveT Steve Litt April 2018 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
