|
... and many recruiters who fervently believe that Javascript is Java.
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
Or that people have 20 years of experience in Node.js 
|
|
|
|
|
Don't knock it, my next CV will say that I've been doing F# since 1862. It will fool somebody!
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
|
That's brilliant!
I'm still at the struggling with consistent theory of quantum gravity bit but I reckon I'll get there in another year or two!
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
PeejayAdams wrote: consistent theory of quantum gravity
That's a pretty heavy subject, but if you get it right you'll be enlightened 
|
|
|
|
|
Maybe I'm just focused too much on edge cases - that while there are many right tools for most jobs, there are also wrong tools that get used.
Back in the day, I had to work on way too many "solutions" that were PowerShell via Citrix. The devs knew PowerShell, but they needed a remote solution. Every single one of those could have been simple websites, but the devs were unwilling to learn the new technology. Then, because they were stuck with a desktop app, they had to shove it in Citrix to get it out to customers. Adding yet another wrong tool for the job (IMO).
Most languages are perfectly fine for most solutions, but I still assert that there are definite wrong tools for some solutions. By knowing more than a single language, you at least can identify why another tool might be the right one for a specific job. (and it avoids writing one language in the idioms of another).
TTFN - Kent
|
|
|
|
|
New programming languages are created every year, but seldom do they gain the attention of developers like JetBrains’ Kotlin has over the last couple of years. It's still got that new-compiler smell
|
|
|
|
|
Kent Sharkey wrote: but seldom do they gain the attention of developers like JetBrains’ Kotlin
WTF is "kotlin"? I've honestly never heard of it. It sounds like a feminine hygien product.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
A proprietary "better" Java.
Also an island in ... Estonia? I think (too lazy to confirm).
TTFN - Kent
|
|
|
|
|
Russian island closer to St. Petersburg than Estonia but fairly close to Estonia.
|
|
|
|
|
Thank you - lazynet strikes again! 
TTFN - Kent
|
|
|
|
|
It's a language which transpiles to other languages -- You write Kotlin code and it generates Java bytecode or JavaScript (or other).
I only know about it (care about it now) because I'm an Android developer and use Android Studio (also written by JetBrains, the creators of Kotlin) to create apps.
I'm actually learning the language now for future Android development. It's not too bad and it is interesting that it is so very similar to Swift which is Apple's language for creating native iOS apps.
|
|
|
|
|
Researchers found a new vulnerability that impacts the confidentiality of data stored in a computer's memory. Using it, they were successfully able to extract a signing key from an OpenSSH server using normal user privileges. That's it - no one gets to connect to any server any more
|
|
|
|
|
I'm still really skeptical of these types of claims (including Meltdown and Spectre). These reports tend to be long on claims and short on details of their actual experimental setup. If I pointed them to a loaded up server actively running several processes and OpenSSH, would they be able to do what they claim to have done?
|
|
|
|
|
The success measured a rate of 0.3 bits per second and an accuracy of 82%. To obtain the full data, the researchers used a variant of the Heninger-Shacham algorithm that can recover RSA keys from partial information.
A method to reduce the risk of this type of read-side attack is to flush encryption keys from memory immediately after using them. This lowers the chances of learning the secret data because RAMBleed needs it to stay in memory for at least one refresh interval, which is 64ms by default.
I'm not saying that this vulnerability is not real but the article is a bit "click-baity" at least.
Yes, they were able to read memory from out of process space, but if an attacker can get access to the server with enough knowledge of memory mapping and ability to run own programs in address space physically aligned to victim's for so long that 0.3 bits per second will hopefully get them enough portion of the key to figure out the rest… I would say there are definitely easier ways to compromise the server.
--
"My software never has bugs. It just develops random features."
|
|
|
|
|
I agree. In my opinion, the worst part about these things is how they are responded to. The mitigation tactics slow the processor down measurably. I think it would be far better to improve front-end security and prevent malicious code from being launched in the first place.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Where else are you going to steal my data from? The CPU, HA!
(wispers: Specture)
Oh.
|
|
|
|
|
There would be a common approach to making tech pay its share. Guaranteed to work until they realize there are more than 20 countries in the world
|
|
|
|
|
|
By combining PowerApps with Microsoft Flow and its new AI Builder tool, it can allow folks building apps with PowerApps to add a layer of intelligence very quickly. Advance warning about something you'll have to fix later this year
|
|
|
|
|
That's just what the world needed: Idiotic artificial intelligence in the hands of idiots.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
.NET Framework? Mono? Xamarin? .NET Core? Blazor? Java interop? And in the IDE, compile them
|
|
|
|
|
Quote: It's more like the .NET Framework except you can have multiple .NET Cores side by side even at the system level.
Am I the only one who's getting fed up with that line? It's perfectly possible to have multiple versions of .NET Framework side-by-side at the system level. It's how things worked prior to .NET 4.5, when they decided to make all future releases in-place upgrades.
The fact that they don't have the resources to make a new side-by-side version of the full framework doesn't mean that it's impossible to do it, or that multiple side-by-side installs is somehow a "new" feature of .NET Core.
Quote: That enables us to service one common component if there's a security vulnerability. ... I don't think we've serviced .NET Core through Windows Update... We haven't made the decision yet.
Again, having one place to patch when there's a security vulnerability isn't some new thing in .NET Core; it's the default behaviour with the full framework. And the full framework gets updated via Windows Updates; it doesn't require developers to recompile every line of code they've ever written every couple of weeks to fix the security vulnerabilities. 
And surely I can't be the only one thinking that this sounds like XKCD 927[^]?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
My question is why did they f*ck around releasing core when it was eventually going to be rolled up into a new version of .Net?
When that happens, confusion will definitely reign.
What's funny is that as long as I'm working where I'm working, we will never see .Net 5 - or even .Net Core - in our dev environment. The federal government is ALWAYS at least five years behind the curve where dev tools are concerned.
In point of fact, our product will probably be end-of-lifed because we can't rewrite it with more modern frameworks, because we don't have the time or the man-power to do it. The problem is that I'm the only contractor on the team, and am therefore the only one who has a vested interest in seeing the app live on. Government employees don't generally care because they can just be shuffled off to new assignments...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
