Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Functional is useful when not pure (Score 4, Insightful) 411

The best functional programming to me, is the kind being integrated into various primarily procedural languages. I use it daily in C# at work, and find it invaluable in performing complex transformations on data. Python, C#, etc. have the best of both worlds -- the choice to use whatever is best for your situation.

I'll expand further, maybe to start an interesting conversation because I'm sure someone will disagree: purely- or mostly-functional languages are the original hype-driven languages. A lot of people say they're amazing, but don't actually do anything useful with them. Sure, some are making great apps with them, but they're clearly the exception. At the end of the day most of the people I've talked to who preach about how awesome their favorite functional language is have only gone skin-deep. Their experience is limited to the academic or experimental, and has never gone into the practical.

The few times I've tried to really master these languages, I've been left with no epiphanies. I've found it extremely useful for some problems, like data processing mentioned above. But for most everything else, it doesn't get me anything useful. On some level it is nice having the flow of immutability -- it "feels" right, like you've discovered something special. The same way adding an extra layer of abstraction on top of something might feel. But when I'd look back on it and ask myself what I gained from having it, there's really very little to be found. It is, mostly, a dogma.

Comment Not really a big deal (Score 1) 46

The Creators Update adds a fair amount of stuff for desktop systems, but for mobile it's a pretty minor update. They essentially took all the desktop updates, and gave mobile the handful of ones that made sense. There are no mobile-specific updates.

For example... Edge is updated to latest version. And it goes downhill from there. Their really slow biometric login is now a little faster, their digital assistant supports a few more commands, you can uninstall apps that previously came with the OS.

Comment Re:History repeating itself (Score 1) 121

It's a little different this time. This is NUMA-aware design. Something that is actually pretty difficult, requiring broad architectural changes that can't simply be bolted onto an app. Most parallel apps don't bother. And similarly, the change isn't "free" like a new instruction: older apps that don't get with the program will run slower and might hit pathological cases. Realistically, NUMA is going to be needed to efficiently scale CPUs beyond 4 cores. Without it, die size increases really fast and it only staves off Amdahl's law by a tiny amount. So, I think it'll get there eventually where it's big enough that apps start to support it and move to a more share-nothing kind of design. But, I very much doubt we'll start seeing that happen any time soon.

Comment Re:FFS, leave crypto alone (Score 1) 137

The most interesting part to me is the TLAs -- organizations full of experts in the field -- deciding it's worth the risk. That so long as they get to snoop, it's okay to risk literally everything should someone with malice get access to the same backdoor.

How anyone can consider it acceptable with a straight face -- especially in light of the CIA leak -- is beyond me.

Comment What is it useful for? (Score 1) 109

Having a hard time imagining the use case for this.

For consumer gear, almost any SSD sold today will be faster than someone would ever need. Just use that as a cache and save some money.

For pro/enthusiast gear, money would probably be better invested simply getting more RAM -- with 32GB, in many cases I have 20GB or more of that being used as a filesystem cache. Cache tends to very rapidly exhibit diminishing returns, to the point where I doubt I'd even notice an extra 32GB sandwiched between my RAM and SSD.

Maybe as a non-volatile cache for large bursts of writes?

Comment Hahahahah (Score 1) 110

We are asking for your permission to change the licence for your contribution.
...
If we do not hear from you, we will assume that you have no objection.

Yes, and I'm asking for the same permission to own all assets associated with openssl.org. If I don't hear back from you, I'll assume you have no objection.

Comment Re:KeePass FTW! (Score 5, Informative) 126

I'll second KeePass. Not just because it's what I use, but because it takes serious measures to protect your data. Anyone can make a functioning password safe, but the way KeePass does it shows it was designed with an eye toward security. As a dev, I can appreciate it.

A browser extension? Really? Your OS has a massive, old, reliable security feature in that one process can not easily access the memory of another process, and you choose to not use that and instead build support directly into the largest attack vector on your PC, the browser?

Comment Re:A better question (Score 3, Insightful) 243

Cheap laptops (barely more than the price of netbooks, and eventually cheaper and better spec'ed than netbooks) killed it.

Both you and TFA are wrong. Manufacturers killed the netbook because once enough of them joined the fray and started competing, they eroded their margins so much that they forced the market into "chromebooks" or otherwise gimped netbooks that were cheaper to license.

Comment Invert it (Score 1) 347

Start with some practical code/app samples that demonstrate clear trouble. Ask them to participate -- see if they can solve the trouble. Then show how the original dev got themselves into that trouble, and the "professional" thing you would have applied to avoid it.

Bonus points for going comedic with examples that are ridiculous to the extreme.

Comment Re:64-bit (Score 4, Informative) 195

It's 2017 and Visual Studio is still 32-bit.

Unless you have specific use cases 64-bit doesn't always mean better. Most apps don't need the extra address space, and jumping to 64-bit means doubling your pointer sizes, which increases memory usage, reduces locality, and puts a larger burden on cache.

In VS's case they did the math and 32-bit was better. They've said this for years now. It's not a bad thing.

Comment Re:$700 GTFO (Score 4, Insightful) 151

Most people spend more on their phone. Or on food. Or vacationing. This is just another form of entertainment to budget for, are you really too myopic to see that?

For people who want to use VR, or who have a 4K screen, or have a 144Hz monitor, you literally can't get by on anything but high-end. Display tech is outpacing graphics cards right now.

Slashdot Top Deals

The amount of time between slipping on the peel and landing on the pavement is precisely 1 bananosecond.

Working...