So? That book is not universally regarded by many grammarians (note the passive voice).
Computers are not an American invention. You did well though to nab Germans to build rockets for you.
20-30MB is larger than the deployment for enterprise applications I've written / worked on and would describe as "sprawling", but which also helpfully include substantial functionality and do useful work.
Adding that to every application download, and installing dozens of "WORA" libraries on every machine is way beyond being a little suboptimal (it's a nice demonstration of Java having completely failed to deliver on its original goals though).
> I mean, forgive me, but it seems that this is a vast improvement. Who wants a
> system that's basically a collection of scripts? That just seems so fragile and un-documentable.
Did someone tell you "script" is a bad word?
You have a choice to keep this represented in a higher layer (text file scripts laid out sensibly written in a high-level architecture-independent language), or as a set of compiled binaries forming a monolithic Windows-style system with a multiplicity of hidden inference rules.
And the current init files can be improved if you don't like the layout or want to make new facilities available - do you think it's impossible to add dependency graph tracking in a way that is accessible to scripts rather than having a "registry"?
> instead of bombing my system back into the 60s.
Ironically we were going to the Moon in the 60s and had supersonic passenger flight. We don't now.
> Why would you want to convert rich information into a string and shove it down a pipe before you make use of it?
I think you've lost sight of the purpose of an OS and the purpose of logs. An OS is not running for the sake of running an OS, and logs are not persistent structured application data, but ad-hoc information about the behaviour of the system for human consumption.
They need to be filtered, sliced, and flattened as needed *post-facto* to be of any use. Given that you don't even know what I want to log, from where, how is that going to be normalised in a centralized journal? Will it let me query by anything more than straight filter on app or PID etc - like I can already do?
> programmers need to start being held accountable for the quality of their work.
But I guess you mean that people who aren't paying for your work, and companies which aren't paying for the processes and professional services necessary for some level of quality, should hold programmers who don't have any kind of engineering or financial relationship with them accountable.
> If that really worked, there would be no QA dept. for software.
No, that's just poor reasoning.
Quality must be built-in, not added-on. QA expectations and improvement scope are largely imposed on any QA department, therefore the level of 'quality' reached can never be an absolute bar.
Developers in general need to minimise the vector product of bug count/severity that could be exposed before it gets to QA. This allows the bar to be raised, and focus to be spent on where it should be rather than catching obvious mistakes, or dealing with unnecessary performance/cognitive/configuration complexity.
Link to Original Source
It is reported to fly faster than the speed of sound, and is the prototype for the UK's first stealth combat drone, due to be operational in the 2030s."
Link to Original Source
Change happens, and for those of us who work with technology for a living it is the only constant. Change is a process and in and of itself is not a bad thing when it offers improvement. Unfortunately the change that has been offered negatively impacts the look, interface and most importantly the functionality of Slashdot.
Many people have had trouble reverting back to the classic interface. The new interface simply does not offer the functionality of the old. Things like statistics, comments and layout are very difficult to find. You have a community that lives and breathes data and want to know their data. How is my comment ranked, how many people responded – it’s really all about the dialogue. Can I get the information that I want in a readily digestible format?
As you’re well aware the new site does not offer the very thing that people come here for. This in and of itself is not why your community has organized a boycott of Beta. The boycott was originated because the new version will be implemented whether the community wants it or not.
I want to explain why this change has gone down people’s throats about as well as Windows 8’s Metro interface. The reason has absolutely nothing to do with the interface and everything to do with the perception that the editors and management of Slashdot appear to have.
The message that has been consistently handed down is that we are “your audience”. We are not your “your audience” we are your product. People do not come to Slashdot for the news stories, there are untold other sites that provide those as well as professional and original writing about them. People come here for the community of insiders from across the industry.
Please respect the community and stop what you’re doing. You have commented that you don’t want to maintain two code bases. Your community works in the industry and understands this, which leads many to suggest you abandon the new code base entirely so that you are only maintaining once code base. Tell us what your trying to accomplish and I would imagine that a wide range of experts would be more than willing to help you meet your goals."
I lurked for a long time, joined a long time ago (this isn't my original UID, which I can't remember).
There isn't anything wrong with Classic. It's probably the only discussion site which is worth checking daily, includes a diverse interesting and clued-in community of people, works quickly, self-limits the sillier side, and works on any browser platform.
Better to me means quicker, retains old members + fresh blood, works on even more browser platforms.
There we go, have we helped define it?
Next time I log onto slashdot, if it directs me to beta, I'm not coming back.