Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. ×

Comment Are two hashes better than one? (Score 4, Interesting) 142

... however it's worth noting that there are currently no ways of finding a collision for both MD5 and SHA-1 hashes simultaneously

Any crypto geeks want to weigh in on the truth of this statement? I've often wondered about this. Wouldn't using two hash algorithms be easier and more effective over the long term than getting the whole world to upgrade to the Latest And Greatest Hash every ~10 years?

Comment Is providing a link too much to ask? (Score 1) 24

Neither of TFA's or the /. summary provide a link to Clear Linux. WTF?!?!

Here it is: https://clearlinux.org/

I get why sites like Network World and BetaNews avoid linking to the subject of their articles. Heaven forbid a reader click the link and leave their site, possibly never to return! Won't somebody please think about the advertisers! Reasonable financial motives for bad behavior doesn't change the fact that it's bad behavior.

Comment Re:BASIC (Score 1) 339

I'm old enough to remember the days of 8-bit computing and the ubiquity of BASIC. Those were good times, but the world has moved on. The problem isn't the language -- GUI's simply changed the rules of the game.

Text (command line) programs can naturally be written a linear procedural fashion. Cause and effect are clear. Display something, wait for input, act on input, rinse, and repeat. Classic BASIC fit this model well, and people could easily learn it. You could go from zero to useful in a relatively short time.

At a technical level, GUI programming is inherently event driven. Originally this took the form of event loops dispatching messages, with more object oriented approaches evolving over time. Classic BASIC does not fit this model, but can be extended to do so (e.g. Visual BASIC). The problem is that the learning curve is steeper. Event driven programming is hard for non-programmers to wrap their minds around.

Another problem is that modern computers come with lots of beautiful GUI-based software, and creating similar software takes considerable knowledge and effort. It's MUCH harder for a newbie to create software that looks and feels like "professional" programs. I imagine this could be very discouraging. I clearly remember the feeling of pride and accomplishment I felt back in the 8-bit days, when my own programs met, and then exceeded the standards of the day. I was able to go from zero to that place in a reasonable amount of time; now it might take years.

Submission + - Google interview process big turn off for experienced engineers (businessinsider.com)

mysterious_mark writes: There's an article in the Business Insider discussing how the interview process at Google is really just geared for recent CS grads, and makes no sense for experienced engineers. Apparently the only criteria to work at Google is one's ability to do white board code problems, actual engineering experience counts for nothing. This may explain why the average engineer at Google is under 30, the problem is partly due to age discrimination, and also because older and more experienced engineers simply don't want to deal with the interview process.

Comment Re:Heh, 1 0 0 1 0 0 (Score 1) 89

YouTube video: https://www.youtube.com/watch?...

The Body Electric is Rush at their best. The bass and drums on the intro are instantly recognizable. It's one of several tracks on the Grace Under Pressure album (released in 1984) that showcase the classic Rush sound.

Few rock bands dare to address "heavy" topics, but Rush did it regularly, and with great success. Neal Peart's skill with lyrics is on full display here. Grace Under Pressure included songs about artificial life ("The Body Electric"), the holocaust ("Red Sector A"), and the cold war ("Distant Early Warning"). None are "preachy", and all are quite accessible to mainstream audiences. They all received a good amount of airplay on rock radio.

(Yes, I'm a huge Rush fan, and I'm proud to admit it!)

Comment Re:libressl-2.1.3 (Score 1) 97

Just because one compiler for one platform fails to support a popular C extension doesn't mean the library isn't portable.

Except that the one platform is Windows, which accounts for the vast majority of desktop PC's and laptops, and a significant chunk of servers. And the one compiler is the standard for Windows, used by the vast majority of Windows developers.

You don't have to like this, but it is the truth.

In my opinion, any software that can't compile on Windows using the native toolchain doesn't qualify as "portable". That doesn't make it bad software. It just isn't "portable" software.

Comment Re:libressl-2.1.3 (Score 1) 97

libressl supports pretty much any unix-like OS

Oh good, both Country and Western.

I know there's a guy working on Windows support as well.

Let me know what the guy working on Windows support actually gets it working. Until then it doesn't count. And by "working", I mean working with the Microsoft toolchain, which like it or not, is the official and most widely used toolchain for Windows.

Comment Re:libressl-2.1.3 (Score 5, Insightful) 97

libressl is NOT portable. Supporting BSD and Linux is not the definition of "portable" (see also: "We play both types of music: Country and Western"). The libressl code depends on the non-standard #include_next preprocessor directive, so it can only build with GCC (and probably clang, which emulates many GCC-isms). Forget about building on Windows using Microsoft's C compiler.

OpenSSL remains the only portable SSL library that can be used by both open source and commercial developers alike. Which is really a shame, because OpenSSL sucks. All the bad things the libressl people have said about OpenSSL are absolutely true.

Comment Re:Thank you! (Score 2, Interesting) 125

... check out OpenBSD before checking out FreeBSD, and I cannot stress this enough. FreeBSD developers don't use their own operating system; they run it in a Virtual machine on their Macs, and it shows.

Citation needed.

Suspend/resume has been broken there since 2008, and drivers for any recent Intel graphics adapter will not run (you cannot switch from Xorg to a console and back) properly.

Yeah, it can suck to run a server-focused OS on a desktop/laptop.

FreeBSD devs do not care about their OS

This is objectively false. Any devs working for free must care, of they'd hack on something else. Any devs being paid must have an employer who cares. The problem is that the people hacking/funding FreeBSD don't care about the same parts of the system that you do.

Comment Re:are the debian support forums down? (Score 3, Informative) 286

... the way systemd has turned into something similar to the bloated beast that is the Windows 'svchost.exe' ...

+1 to the anti-systemd sentiment.

-1 to using svchost.exe to make your case. svchost is just a container process. The real issue is the Windows architecture/philosophy that encourages a proliferation of services.

(I like Unix and I like Windows. Each has their place. Trying to turn one into the other is a big mistake.)

Comment Good luck with that (Score 1) 139

Option #1: Valve has no physical presence in Australia, and tells the Australian government to go fuck themselves. Government responds by banning Valve from doing business in Australia. Good luck enforcing that. To the extent they do manage to enforce it, it will be taking action against Australian citizens, since they have no power over Valve.

Option #2: Valve doubles prices in Australia. Y'all can have all the consumer protection you want, but you're going to pay for it.

Comment The fix is to delete the font cache (Score 5, Informative) 179

The way to fix this is to delete \Windows\System32\FNTCACHE.DAT. The file will automatically be regenerated on the next boot.

(Information found on Microsoft Support Forum and used to successfully fix my own system.)

How do you delete the file if you can't boot?

(1) Press F8 during boot to get to the Windows boot manager advanced options screen.
(2) Select "Repair".
(3) Provide password for a local account that's a member of the Administrator group.
(4) Select "Command Prompt".
(5) Find drive letter assigned to Windows partition (may not be C: in the repair environment!).
(6) Delete \Windows\System32\FNTCACHE.DAT.
(7) Exit command prompt and reboot system.
(8) Fixed!

----------

And now, since this is /., here is the required Windows bashing...

This bug demonstrates the danger of running your GUI in kernel mode (win32k.sys). One stray pointer can ruin your whole day. In this case the pointer was sufficiently invalid to cause a bugcheck. A stray pointer that silently scribbles on other kernel data structures is even worse.

"Those who would give up essential Safety, to purchase a little temporary Performance, deserve neither Performance nor Safety."

Comment The Mill (Score 2) 125

I think NVidia tied their hands by retaining the ARM architecture. I suspect the result will be a "worst of both worlds" processor that doesn't use less power or provide better performance than competitors.

In order execution, exposed pipelines, and software scheduling are not new ideas. They sound great in theory, but never seem to work out in practice. These architectures are unbeatable for certain tasks (e.g. DSP), but success as general purpose processors has been elusive. History is littered with the corpses of dead architectures that attempted (and failed) to tame the beast.

Personally, I'm very excited about the Mill architecture. If anybody can tame the beast, it will be these guys.

Slashdot Top Deals

The sooner you fall behind, the more time you have to catch up.

Working...