Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×

Comment Fascinating ... (Score 1) 63

I find it fascinating how these days companies can charge bizar amounts of money for things we have enjoyed for free for decades. IRC is a perfect solution and yet people buy into slack - itself an IRC rippoff with an OK web interface included.

Same with Office Products. Office365 costs 40 Euros per seat and month. And people are actually paying for this. Imagine Microsoft coming up with such a thing in the 90ies. People would've peed their pants laughing.

It's fascinating the way our entire society is being brainwashed into access culture. Scary but fascinating. Like sheep. And they don't even notice.

Comment Re:This again? (Score 1) 398

"Assembly" is not a programming language...

I think you need to rethink that statement.

The earliest computers were often programmed without the help of a programming language, by writing programs in absolute machine language. The programs, in decimal or binary form, were read in from punched cards or magnetic tape, or toggled in on switches on the front panel of the computer. Absolute machine languages were later termed first-generation programming languages (1GL).

The next step was development of so-called second-generation programming languages (2GL) or assembly languages, which were still closely tied to the instruction set architecture of the specific computer. These served to make the program much more human-readable, and relieved the programmer of tedious and error-prone address calculations.

The first high-level programming languages, or third-generation programming languages (3GL), were written in the 1950s. An early high-level programming language to be designed for a computer was Plankalkül, developed for the German Z3 by Konrad Zuse between 1943 and 1945. However, it was not implemented until 1998 and 2000. - Wikipedia

Comment Turkish dorkery is off the charts ... (Score 1) 45

Living in Germany turks and people of turkish descent are a part of everyday life. We've got roughly 3 Million people with turkish heritage, many in 2nd and 3rd generation, and turkish is the second most spoken language here.

What I've long since discovered is that when Turks go dorky, they clear the bar for dorkyness in an instant.
The video and the tacky pseudo-transformer it features is about as turkish as it gets in that regard. :-)

Comment On a sidenote: (Score 1) 277

If you don't know what you're doing, you might want to stear clear of blackbox devices in your private LAN.
I personally wouldn't trust an IOThingie that I didn't build myself with a Rasberry Pi, Arduino or something.

Oh, and not being able to find out if your device is part of a botnet counts as 'not knowing what you're doing'.

My 2 Eurocents.

Comment Re:Rust gets it right (Score 1) 87

Unfortunately, habituating your developers to call .unwrap() on everything (with the tacit "oh I know it's bad, but..." approval) doesn't really put you in a better place.

What you have with Result<T,E> and especially Option<T> is the concept of null delivered in a purposefully non-ergonomic form, with the theory being that the extra explicitness will drive developers to write better code by default. However, that unwrap() escape hatch is mighty convenient; time will tell if the theory was right or not.

Comment Re:Do away with them (Score 1) 87

Failure is the best default. It's a harsh path that leads to stronger guarantees about data and behavior.

Sentinel values (like 1900-01-01) generate hard-to-find bugs and threaten the trustworthiness of your data. If you can't remember to check for null, you're certainly not going to remember to check for a sentinel value.

The recent shift in language design to favor non-nullability by default is probably a good thing: if you don't need null, it's nice to let the compiler/database enforce that for you. However, if you do need null--if the value of a variable/field can be unknown, for instance--it's best to use it and do the extra work. Muddle things with a sentinel value only if the inevitable consequences are acceptable.

Comment Destroys Rasberry Pi? (Score 1) 205

You mean the board actually stood up, walked over to the Rasberry Pi standing nearby and crushed it to pieces? ...
What happend to normal sentences like "Runs XYZ benchmark 5 times faster than the Rasberry Pi using half the energy" or something like that?
Is this the effect the US political debate has on language? Probably.

Comment Re:**Anything** can be used as money (Score 1) 87

"Anything can be used as money." => Nope, not really. The item must be in suitably common supply while still being somewhat scarce; it must be hard to forge; the recipient must be able to readily trust the authenticity and denomination of the item; it must be be fairly divisible; it must be durable/preservable, transportable, and convenient to exchange. And of course, it must be accepted by a critical mass of commercial participants.

Comment The more efficient a system gets ... (Score 1) 108

... the more fragile it becomes.

Hanjin - a major korean shipping corp recently gone bankrupt - has massive containerships standing at sea, not allowed to run into harbours because the harbour authorities are afraid they won't see their fees. As a result, companies relying on their shipments done with Hanjin are on the brink of bankruptcy, because they can't deliver. And on it goes down the foodchain.

This is what happens if you cut it too thin and expect dirt-cheap stuff and services everywhere, every time and all the time. Same with Uber, Lyft, MyHammer and now this. This sort of race for the bottom line will end up with deflation and eventually a lot of companies and individuals going out of business.

Slashdot Top Deals

Multics is security spelled sideways.