Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×

Comment Re:Make 2.0 (Score 1) 513

Don't overlook the fact that comments are HTML formatted.

  • No funky BB code or markdown-flavor-of-the-day.
  • Just straight, sanitized hypertext markup language.
  • Acts as small difficulty bump to raise that submission bar.
  • All the bold and fancy font variations you want.
  • No blink but lynx compatible links

At least keeps one in practice for writing real web sites.

Slashdot's moderation system is still hands down the best I've come across.

And for April first implement radio controls so you can toggle categories.

But lock it so that you can only turn on Funny. Or enable only Troll when set for +5 only.

Comment Re:What tripe! (Score 1) 92

Or, may be they are not really fools and, like a few rulers of the past, the “legacy” stuff they make is merely there to impress their contemporaries. In short, yes, just more bloody advertising.

You could always sell copies to doomsday prepers and people dreaming of becoming backyarders.

On the other hand it might take a few cycles of civilization collapsing and being rebuilt before we get a good test of how to build and what to include.

But then on the third hand I'm hoping that humanity isn't actually the race that spawns the Motes with a great need for working, reliable civilization bootstrap systems.

Comment Re:Good grief (Score 1) 259

Furthermore I have a dim view to say the least of people like you who tell others to 'give up and give in' to having their privacy and their lives invaded by shitty corporations and shitty governments who want to stick their little brown noses in people's private business

Nobody has to tell anybody else to 'give up and give in'. The listening device on my phone will records your conversations just fine.

Privacy is still a Thing, it's worth protecting and fighting for, and it's criminal so far as I'm concerned to tell people otherwise.

People have always traded for convenience. We traded away our community for a semblance of privacy. Originally privacy was never a thing. When people lived in small bands and villages you knew everyone's business. Privacy and the expectation of it briefly became a thing when society got spread out enough with enough people that it wasn't worth it given the technological limitations. Now those limits are going away and privacy is going away again. This time the town gossips are news agencies with agendas and corporations operating without morals or only ethics of blind profit.

I'll look down my nose at you and everyone like you, but do NOT go around telling people to be like you.

You can choose to not do business with or permit access to people who carry a 'smart' device of any kind. But in the first world that means limited yourself. Depending on the market you will not doing business with a lot of people. They will simply find someone with your skills but who doesn't care about cellphone surveillance (cell-veillance?).

They will look down their noses at you and wonder 'what bad things have you done that you must hide?' You become the 'rude weirdo' that asks people to put their phones in radio-bags before hanging out with you at lunch.

But if you want a return to that brief period of personal privacy you'll have to start a cultural and legal revolution. Eventually all new "private" buildings with come with these fixed smart hubs. First to provide 911 assistance or as a selling point for a luxury home. Then as part of parole terms for the poor criminals. Like those who don't double-plus-good-think in our brave new world of corporate group-think.

Comment Fire sale on the CD Collections (Score 4, Interesting) 123

That leaves, what? Linux Format: the 400 Lbs Gorilla of Linux reading material, with a price to match, Linux Magazine and distro-focused publications like Full Circle?

I do hope they get a chance to make a final run of the back edition PDF collection.

Many of the columns, such as David Taylor's work the shell, are timeless and quite useful.

There is value even the Letters to the Editors where smart or at least smart ass people suggested better or alternative ways to implement the various little projects detailed in LJ.

I also enjoyed the Linux Kernel Mailing List (LKML) summaries and discovered Reuven Lerner's python series through the magazine.

And there are always the Geek Guides.

Comment Re:Functional (Score 2) 70

While the sudo manpages get short shrift, the Sudo release notes are one of the best examples of open-source release notes.

They are

  • published in a convenient "permanent" location
  • provided in multiple formats (direct email, mailing lists, usenet, webpages, version control strings, package logs)
  • searchable format (text)
  • ordered reverse chronologically (newest first when reading top to bottom)
  • available in common languages
  • clearly written in short, technical language
  • mentioning new features including searchable strings or examples
  • providing references, links and IDs of relevant tickets, bugs and background information

So, for example, if you needed to do something like figure out when the includedir option was added? Google it, get that page, find the version on that page and you are done.

Note that I use the present tense form in this. The legacy of the written word applies to Shakespeare as equally as it applied to your public Git commit messages. Or release notes. Once you publish your release notes they are always providing that information. They are providing information right now, just possibly to new people.

And please, don't just make your release notes a compilation of your commit messages. Unless they are really really good.

Comment Re:Falsifiable test? (Score 1) 264

One important differences between physics and natural philosophy is the assumptions of universality and non-uniqueness.

The claim is that you have no privileged point of view to the universe. In space or in time. This is so you can test something in a lab and the test is equally valid everywhere. Given the rest of physics, if your lab were orbiting a super-massive black hole powering the furthest quasar billions of years ago on the other side of the Universe it should have the same result.

Science Fiction has already asked both the question "what is this isn't true?" and "what if it were aliens?". Vernor Vinge wrote A Fire Upon the Deep almost a quarter a century ago. A key plot point in part of that novel is that some physics is not natural. You'll have to read the book to find out what that is, though.

Whole civilizations are born, grow into interstellar civilizations and then die because of these "hard" limitations in their physics. All the while just next door are people doing impossible things because they are not so limited. The effects are even done to hide the appearance of jaggies like ShanghaiBill brought up.

The only real way to is get the ground truth. We just have to get off this flying ball of rock and go see for ourselves. Anybody up of that, though? Getting up a gravity well is pretty hard. (At least on Earth.)

Comment Re:No, because meaningful whitespace (Score 1) 808

A good programming editor has the ability to make 'whitespace' characters visible somehow. IMHO, lack of that feature is one of the criterion for being good or being suitable for programming. (Yes, you can also write War and Peace in notepad.exe if you really have to.)

VIM has 'set list'.

Sublime shows whitespace on selected text.

Atom has the editor.toggle-invisible setting (and lots of packages to add menu option for it.)

Visual Studio has CTRL + R, CTRL + W Menu: Edit -> Advanced -> View White Space

In EMACS you have to write a little lisp code.

At the end of the day this is about as annoying as finding the missing semicolon in ALGOL-style code.

Comment Re:Cool stuff (Score 2) 221

Jakub's Mastering Git book discusses briefly that git is less a version control system in itself and more a tool for building version control systems.

Alternative user interfaces like Zit, Cogit and Yap show that there is some merit to this view.

Git's content-addressable data store with locally computable global identifiers can form the basis of a generic storage engine. Microsoft has created what appears to be another file system out of git. There are many other filesystem implementations.

The git wrapper and workflows used by the Linux project can be seen as just the demonstration of one implementation. Collaboration and hosting sites like GitHub and GitLab show that you can turn a git repository into a project management tool. People have even built code review tools out of git (Critic, git-issues, etc.)

I wonder if Microsoft could implement something like etckeeper for the registry? (It would be nice to be able to run git blame after corruption by some vendor's installer.)

I do find it odd that Microsoft is switching to git so the team can put Windows into a single, giant repository while trying to modularize the product. One would think that the prior Perforce based system would have suited the modularization goal. That was forcing multiple repositories on the developers to meet the scale of the codebase. Perhaps the intent is to centralize then reorganize and break out into logical modules again? (It could be a control freak VCS team that is jumping at the chance to become the gatekeepers.)

The article does mention that "the company wanted to develop a single engineering system ('1ES'), spanning not just version control, but bug tracking, building, and more, that could span the entire company. " This makes the next version of Team Foundation Server sound a lot like GitHub Enterprise from Microsoft. Should Microsoft offer this 1ES environment for sale? It could certainly add a twist to the corporate on-premise or could-based git hosting market.

Comment Non-Free Repositories (Score 4, Interesting) 415

The lack of patent encumbered algorithms in MP3 means two things:

  1. 1. The MP3 gstreamer codecs can move from the non-free repositories to free for Linux distributions. So no more complaints from software like Amarok about missing MP3 support libraries on your Linux desktops. That's one less step to setup Mint, Ubuntu, Fedora or openSuse. Even though there are plenty of reasons (CAD software, WMA support, etc) to seek out the non-official or non-free package sources I expect less use.
  2. 2. Corporate users will be able to download, integrate and use the MP3 format in their projects with only a cursory approval from legal. I used to see quite a few video game projects use .ogg files and fmod for their sound. I expect to see more of them ship with MP3s instead.

Audio snobs won't stop arguing about the format of the week or FLAC verses DSD or the best bit rates on PCM encoded WAV files.

Mere consumers shall continue on with our plebeian fidelity sound as always.

Online buyers will continue to download low bit rate MP3s to squeeze a few more hundred tunes onto their Zune. Everyone you know will still play studio damaged music through tiny earbuds.

Comment Re:Don't buy this (Score 1) 441

Do you have a cat in your house? How well does hang-drying handle pet dander?

The answer pet owners want to know is how does this sonic dryer fare at removing kitty's mess of fibers.

Don't think that pet hair can lodge itself into cloth pretty well? It's amazing what is floating around the air or well hidden in the pattern on a sofa at a pet owner's house during springtime. I don't need to save 35 minutes on a 55 minute cycle once if I have to spend 5 minutes every day lint rolling everything I wear for decades.

At least I can go do something else while the clothes are in the dryer.

Comment Re:Perfect timing (Score 2) 48

Having such a huge wealth of public domain images all together on one seemingly well-designed search engine will be great for finding substitutions.

The images and videoes are searchable by tags. They have really good descriptions that break into keywords well. Lots of images of hardware, astrophotographs, locations, mission patches, buildings and people.

This is a huge resource of labeled images for supervised machine learning. A massive gift to anyone wanting to do image processing.

Comment Re:Lies? (Score 1) 548

Just because the standard for a title where you live is low enough to admit anyone who self-identifies does not mean that other people place a lot of value in their definition of that title.

Depending on where you work there is a very clear line for being an engineer. In many cases Engineer is a protected title with legal obligations.

Only passing the PE as an EIT can you actually call yourself an Engineer in Texas. Even software developers in Texas, USA have to site before the Board of Professional Engineers and pass the Exam to call themselves an Engineer.

You can't just walk in with your freshly minted Software 'Engineering' degree from an ABET certified college program. You have to be a Texas Engineer in Training (EIT) to register to take the PE exam. That is usually having worked under a PE mentor in the capacity you are training for.

This is very similar to other protected titles in other counties like Registered Pharmacist in the UK.

This title caries with it a lot of ethical and legal requirements that most "coders" or "programmers" would not be able to meet just based on the code they write. But such titles carry with it the authority to tell management where they can stick it when they ask for faster, cheaper by cutting corners that are not Salespeople Features.

The biggest lie, just based on the number of empty GitHub Projects is probably "I can do this."

Comment Cargo Cult Metrics without science (Score 1) 234

The Road to Performance Is Littered with Dirty Code Bombs

Unexpected encounters with dirty code will make it very difficult to make a sane prediction.

Dirty code is defined as ' overly complex or highly coupled.' As a programer you are expected to deliver X number of features by Y date. Unless one of those features is 'simple and loosely coupled code' what does that have to do with predicting anything? For performance you don't predict. Experiments are the only thing you have that work: test and change and re-test and un-change and re-test, endlessly. Anything else is voodoo programming, not to insult the pracitioners of Santaria, Vodou or Hoodoo.

How about predicting the schedule? I recall that Steve McConnell once joked that to get better at estimating we need to get better at estimating. (This may have been someone else.) Greg Wilson showed we can do this in programming, and Computer Science in general. We only have to do scientific experimentation with various methods. We throw away what doesn't work (instead of writing pulpy business books to bilk people out of money.) But you'll still have to run a lot of tests to do that, too.

It is not uncommon to see "quick" refactorings eventually taking several months to complete. In these instances, the damage to the credibility and political capital of the responsible team will range from severe to terminal. If only we had a tool to help us identify and measure this risk.

It is my opinion that any refactoring that cannot be done by an automatic program isn't refactoring. The original definition of refactoring is just 'factoring' or re-organizing the code. It is not a re-writing as in an 'several months' effort.

Misuse of a sexy, trendy name from the 90s does not change this. All re-writing suffers the risk of second-system syndrome and not in the throw-one-away sense of prototyping. Do you have a button to press in your IDE to make the change? Do you have in mind a short sed statement, simple awk program, EMACS macros or a on-hand shell scriptlet to do the transformation? If not then you cannot get away from re-thinking the problem. This will require re-design of the solution and re-implementation of the feature. Each of these carries time risk at least as high as the original work.

What if the problem is overly complex or highly coupled? The code may merely be an expression of this. In this case only a paradigm or perspective change by the customer, developer or user can untangle the problem. The computer cannot help you do anything but automate making a mess if the problem is a mess. Changing perspective is often an unbound-in-time problem for human beings. Good luck with estimating completion dates for that.

In fact, we have many ways of measuring and controlling the degree and depth of coupling and complexity of our code. Software metrics can be used to count the occurrences of specific features in our code. The values of these counts do correlate with code quality.

In fact, Greg Wilson showed in his presentation that almost every metric on the market when analyzed showed no better and usually equal predictive power as simple counts of Lines of Code.

The situation in programming is almost as if more code equals more bugs while less code equals less bugs.

This seems obvious and trivial, but this is quite real and has serious implications. One of those is the increasing spread of syntactic sugar in programming languages. Another is the proliferation of VM models that take over more features like threading and memory management over time. This is enabling less skilled programmers to do things that once required lots of skill, training and thought to implement. This also forces certain performance requirements for applications, e.g. the arguably fictitious idea that Java Virtual Machine is bloated and slow so all Java applications must be bloated and slow.

One downside to software metrics is that the huge array of numbers that metrics tools produce can be intimidating to the uninitiated. That said, software metrics can be a powerful tool in our fight for clean code.

But if they are no better than simple counts of Lines of Code, why should the uninitiated bother? If you know that the more you write the more bugs you are going to have, why not seek to write less instead?

They can help us to identify and eliminate dirty code bombs before they are a serious risk to a performance tuning exercise.

The fastest code is that which is never run. The only code without (implementation) bugs is code that doesn't exist. Why is quicksort so quick? Because it does less than other sort algorithms.

This is also, I think, why a lot of great programmers are known for writing either some major tool or a programing language. Rephrase the original problem in a well-matched language or tool's command interface. Then you only have to write a little amount of code. Writing parsers is so well known of a task that many tools exist to process a description of a language into a compiler automatically. The real trick is realizing you need to do this the first time, not the second time around.

This is well covered by the other advice in the Contributions like Unix Tools and Simplicity and Automate.

Comment Re:It's not the highway infrastructure (Score 1) 469

It is funny to note that one of the original - and never met - goals of the original President Eisenhower Federal Highway system was to replace bad city-planned roads to reduce congestion. The ironic fact the system increases congestion it by creating choke points to get on and off it is lost by many.

The real root of the problem is that people are either unwilling or unable to live within a short distance to their workplace. Many large cities were not designed to handle the volume of commuters that we have had for at least 20 years. People live in the suburbs (for a variety of reasons; some due to economics, others due to a desire to live in areas with lower population density), and commute to the city centers to work.

The highway system in the United States is rather unusual. Most countries would design a system to maximize the utility. Lots of high density living near high density employment plus walking, cycling and mass transit. Then minimizing problems like traffic jams by using turnabouts and parallel paths. Instead, the United States highway system was built for the military instead. It was created by the Federal-Aid Highway Act of 1956, popularly known as the National Interstate and Defense Highways Act (Public Law 84-627).

Originally this system got raw material from one side of the country to another to manufacture planes, guns, ammo and ships. It was also envisioned as a great lever on the economy. But the immediate social cost of this high-speed bypass was destroying little towns that grew up on existing roads like Highway 66, a road that already crossed the entire country.

But the system was funded at a time when Nuclear War was the next big thing just around the corner. One intention or clear effect is spreading living out into the new suburbs and exurbs to reduce the impact of a nuclear strike on the core of a city. In fact the roads around every major city aren't designed to avoid traffic jams but instead to ensure:

the importance of the Interstate System to evacuation of cities in time of national emergency.

-- the Clay Commission.

This was the time when everyone was told on the brand new TVs that success means 'a steady job, a home out of town, a car, two kids and husband+wife.' That is when they weren't practicing duck and cover.

Where these yahoos intended to put these people fleeting the burning inner cities during war? The imaginary copious amounts of farmland that planners though should be able to support them. Yes, this was during a time when farming was already well on it's way to consolidating into agribusiness.

No, people didn't decide that suddenly the suburbs were the peak of civilization (even if we parody that in the movies.) The citizens of the United States bought a big pile of propaganda. The sad fact is that the people who wrote that propaganda actually believed it was to help them.

The problem can only be solved by reducing the need for people to commute. There are a lot of ways to do this:

Tell that to three generations of management that believe in face-to-face time. Google and other Stack-ranking "Internet Native" companies design their HR system to terminate remote workers or flex workers as fast as they can hire them. Sixty years of white flight, black flight, Mexican-ization, gentrification, urban blights, drug wars, gang wars, the real estate collapse and protectionist nimby laws the problems haven't been solved by staying at home. In places like Irving, California, that are built on the Internet, things got much worse. The demographics keep changing but the work culture and laws didn't.

And the roads? The roads pretty much stayed the same. Literally. As in until you couldn't really drive on them anymore.

Infrastructure's expensive. Someone's gotta pay to make it then someone's gotta pay to keep it up.

Slashdot Top Deals

The most exciting phrase to hear in science, the one that heralds new discoveries, is not "Eureka!" (I found it!) but "That's funny ..." -- Isaac Asimov

Working...