Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
Note: You can take 10% off all Slashdot Deals with coupon code "slashdot10off." ×

Comment Re: Brought about by the internet? (Score 1) 649

The logic behind my words: that AC post has an IP address associated with it in Slashdot's database. If "jcr" decides to sue, his attorney will be able to obtain that IP address. From the IP address they can determine the ISP, and can then legally obtain the customer who had the IP address on 2015-08-29 17:39.

I agree the AC's words are worth little and are dishonest. I disagree that interacting with fools is a useless endeavor, in other words, I won't ignore ACs merely because they refuse to identify themselves. There is no true anonymity, anyway, as I described above.

Comment Re:It's absolutely stunning how WAY OFF most of yo (Score 1) 649

Again, the comparison to the Bible is apt. Do you think that "context is important" with respect to the Bible, and that the government should enforce its sale only if it includes said government-approved contextually-added comments? (Analogies are important, even if this one isn't car-related.)

Comment Re:It's absolutely stunning how WAY OFF most of yo (Score 1) 649

The swastika is not a "Nazi symbol" any more than a pyramid or eye is a "US symbol". It is one of many similar symbols used in religions throughout the world. In India, for instance (a coworker from there informed me), they use it both "forwards" and "backwards", e.g. "SS" and "ZZ", as power symbols.

It's amusing that "Mein Kampf" is legal to be sold only if it contains revisionist remarks! That'd be like the US government making the Bible illegal to sell, if it didn't contain the US government's "explanatory remarks" -- laughable and ridiculous. Definitely not amusing for those forced to live under such restrictions, though.

Comment Let's get this straight... Numbers dropping, but (Score 1) 649

can't talk about it?

The number of deaths on the plaques at the camps have been dropping, one fell by 2.5 million (IIRC it went from 4 million to 1.5 million).

So, 6 million minus 2.5 million is only 3.5 million. Yet the Tribe keeps saying "6 million died!" -- as Mark Knopfler said in "Industrial Disease", "Two men say they're Jesus; one of them must be wrong."

If it's a crime to make it less of a tragedy, are they prosecuting those who changed the plaque?

The "gas chambers" were woefully unsealed, and would have killed the guards standing outside if they had been used. The chimneys were added after the war, to make it look more dangerous. In reality, they were merely showers, in which they deloused people -- typhus was what killed most of those who died.

I'm fortunate not to have ridiculous laws restricting my ability to question and understand my present and past.

Very few members of the Tribe are descendants of Shem, so it's illogical to call those who point out their crimes "anti-Semite".

Comment With someone else's money (Score 1) 207

The whole thing about the left, is that they say they are nice because they want to spend someone else's money to do what they want. If they got up and did whatever they wanted to do, on their own, they wouldn't need government. But nope, they want to take everyone else's money to build their wonder society because their own society is too useless to build anything for itself. It's like a cancer, consuming everything in the body of the nation.

Comment Re:Jim Stone reports Hawking died years ago (Score 1) 167

"Skilled in the art" -- thank you sir! I don't think that myself, I just receive inputs from disparate sources and attempt to put them together into something coherent and usable. Nobody has survived as long as Hawking has, with the disease that he has. So, as they say, "extraordinary claims require extraordinary evidence." From wikipedia and wikipedia:

The diagnosis of motor neurone disease came when Hawking was 21, in 1963. At the time, doctors gave him a life expectancy of two years.[38][39]

The average survival from onset to death is three to four years.[8] About 10% survive longer than 10 years.[4]

The evidence that Hawking is still alive is lacking, just as the evidence that the earth is a globe is lacking. And, apparently, intentionally ridiculous (the "SEX" in the clouds in the newest photo from a month ago; the perm sported on the space station (how did she spray, without everyone else coughing it up?); the bubbles seen rising in the Chinese "space walk" video; the "thunk" that can be heard as an Apollo astronaut tosses something and it hits the (completely turned off) lander, so the sound was picked up through the suit's microphone ... in vacuum ...; and many more instances of their intentionally showing us the fakery, not to mention The Shining).

While I used to find your signature amusing, I now understand that they (politicians) only act as imbeciles, while they rape the country and its resources. Look at Hillary's behavior, selling 18,000 documents to foreign powers, a true Bolshevik communist, and now all the media distractions keeping that story from the surface (the fake shooting in VA, "Cecil the lion", etc).

Submission + - Learn FPGAs with a $25 board and Open Source Tools->

An anonymous reader writes: Hackaday has a 3 part tutorial with videos of using open source tools with a cheap ($25) FPGA board. The board isn't very powerful, but this could be the "gateway drug" to FPGAs for people who don't want to spend hundreds of dollars and install 100s of megabytes of software and license keys just to get their feet wet. The videos are particularly good--like watching them over their shoulder. As far as I know, this is the only totally open source FPGA toolchain out there.
Link to Original Source

Submission + - Book review: Effective Python (59 specific ways to write better Python)

MassDosage writes: If you are familiar with the “Effective” style of books then you probably already know how this book is structured. If not here’s a quick primer: the book consists of a number of small sections each of which focus on a specific problem, issue or idea and these are discussed in a “here’s the best way to do X” manner. These sections are grouped into related chapters but can be read in pretty much any order and generally don’t depend on each other (and when they do this will be called out in the text). The idea is that you can read the book from cover to cover if you want but you can also just dip in and out and read only the sections that are of interest to you. This also means that you can use the book as a reference in future when you inevitably forget the details or want to double check something.

Effective Python stays true to this ethos and delivers 59 (not 60, nope, not 55) but 59 specific ways to write better Python. These are logically grouped into chapters covering broader conceptual topics like “Pythonic thinking”, general technical features like “Concurrency and parallelism” as well as nitty gritty language details like “Meta classes and attributes”. The range of topics is excellent and cover relevant aspects of the language that I’d imagine pretty much any developer will encounter at some point while developing Python programs. Even though there is no required order to reading the various sections if you want to read the book from cover to cover it’s organised in such a way that you can do this. It starts off with getting your head around coding in Python before moving on to specifics of the language and then ending with advice on collaboration and setting up and running Python programs in production environments.

I really enjoyed the author’s approach to each of the topics covered. He explains each item in a very thorough and considered manner with plenty of detail but manages to do this while still being clear and concise. Where relevant he describes multiple ways of achieving a goal while contrasting the pros and cons of various alternative solutions, ending off with what he considers the preferred approach. The reader can then make up their own mind based on the various options which applies best in a given situation instead of just being given one solution. The author clearly understand the internals of the Python language and the philosophy behind some of the design decisions that have resulted in certain features. This means that instead of just offering a solution he also gives you the context and reasoning behind things which I found made it a lot easier to understand. The discussions and reasoning feel balanced and informed by the experience of a developer who has been doing this “in the trenches” for years as opposed to someone in an ivory tower issuing dictats which sound good in theory but don’t actually work in the real world. The vast majority of the topics are illustrated through code samples which are built on and modified at each stage along the way to a final solution. This gives the reader something practical they can take away and use and experiment with and clearly shows how something is done. The code samples are easily comprehensible with just enough code to demonstrate a point but not so much that you get distracted by unnecessary additions.

While most of the topics are Python specific plenty of the best practices and advice apply equally well to other programming languages. For example in one section the author recommends resisting some of the brevity offered by the Python where this can lead to unreadable code that is hard to understand but the same could be said of writing code in many other languages (I’m looking at you, Perl). This also applies to a section related to choosing the best data structure for the problem at hand — if you end up nesting Maps within Maps in your code then you’re probably doing something wrong regardless of the language. Still, the main focus here is Python and the author does not shy away from going deep into technical details so you’ll definitely need some knowledge of the language and ideally some experience using it in order to get the most out of it.

Effective Python is not a book for complete newbies to Python and I think it’s suited more to intermediate users of the language wanting to take their skills to the next level or advanced programmers who might need some fresh takes on the way they do things. The subjects and opinions in this book could either convince you to do something differently or reassure you of the reasons why you’re already doing things a certain way (external affirmation that you’re right is also useful at times!) I’m no Python expert but I found the book drew me in and kept my attention and I certainly learnt a lot which will come in handy the next time I put on my Pythonista hat and do some Python coding. Highly recommended.

Full disclosure: I was given a copy of this book free of charge by the publisher for review purposes. They placed no restrictions on what I could say and left me to be as critical as I wanted so the above review is my own honest opinion.

Comment Re:In other words. (Score 3, Insightful) 282

The law should NEVER, EVER, EVER, provide protection over any data available behind public sector activity.

The public sector frequently claims the release of information will be burdensome; however, the public sector actors are not always forced, by statute (as they are in Minnesota) to ensure records should be held in a way which the sector cannot claim burden in failure to comply.

This needs to change.

Comment Re:Just what I need for an old car! (Score 1) 87

Hopefully this is not continuously tracking your car and sending details of every minute of your travel to Verizon.
If you want to know where grandpa is, it could just send a message to the car and retrieve the position.
If there is a fault code or an accident, it could just send a message.
The data use requirements for this should be minuscule (and so should the price).
It seems targeted at clueless technophobes who are willing to pay for (false) security.

Comment Re:NASA needs more Antarctica defense money (Score -1, Troll) 77

It's not funny, and it's not a troll. It's Informative, but since there was a globe in the first classroom you ever entered, you've been programmed to dismiss this knowledge.

I sincerely apologize for the cognitive dissonance. It took me a bit to get through as well.

If I'd known computer science was going to be like this, I'd never have given up being a rock 'n' roll star. -- G. Hirst

Working...