|
A new platform developed by MIT and Harvard University researchers ensures that web services adhere to users' preferences on how their data are stored and shared in the cloud. "I am Vinz, Vinz Clortho, Keymaster of Gozer. Volguus Zildrohar, Lord of the Sebouillia. Are you the Gatekeeper?"
It just needs everything to be re-written, and you still have to trust the devs to follow the policies you've accepted. Yeah, this is practical. 
|
|
|
|
|
There is no data, only Zuul. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Typical MIT.
Basically, one of the lecturers has "discovered" proxy servers, and is going yampy with them.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Is open-source past its prime? Does it need to be replaced? Some companies say yes, while others say nonsense! Can we call them 'fauxpen source'?
|
|
|
|
|
See what happens when there's one bad apple?
No, sorry, "apple" is an inappropriate word, in this context, because they're blameless.
Let's try again.
See what happens when there's psychopathic monster running a company like amazon?
Nailed it!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Today we are taking a look at a bit controversial one. It’s a possibility to provide default interface methods implementation. So... a base class?
|
|
|
|
|
Quote: ... this feature will not work with .NET Framework! Only CoreCLR and Mono stack runtimes are going to receive these new updates.
Possibly the most important line from the article.
It's not yet clear whether this will be added to a future version of dNF, or whether dNF is now in "maintenance mode" and everyone's being dragged kicking and screaming nudged towards CoreCLR.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
What a PFF (pointless f*ckin feature). Like you said... base class. Another (better) solution is to simply create another interface that ionherits the old interface:
public interface IOne
{
void Method1();
}
public interface ITwo : IOne
{
void Method2();
}
public class OldClass : IOne
{
public void Method1() {}
}
public class MyClass : ITwo
{
public void Method1() {}
public void Method2() {}
}
The dowwnstream classes can be modified as needed. There's absolutely no need for this kinda crap/fluff. Let core keep that crap.
".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
|
|
|
|
|
Do that means we finially have somthing similiar to multiple inheritance in C#? or just the con side of it?
|
|
|
|
|
Isn't that an old Java feature?
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
|
|
|
|
|
It’s essentially a hub for launching recent documents, accessing the Office desktop apps, or simply finding the free web versions of Office. Because you need an easy way to switch from Word to Excel?
Did they run out of icons to update or something?
|
|
|
|
|
Kent Sharkey wrote: Did they run out of icons to update or something?
No... just another way to bring Clippy back to life
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
This...
I'll stop there, because I don't want to get RSI.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
A new take on the age-old question: Should you rewrite your application from scratch, or is that “the single worst strategic mistake that any software company can make”? Turns out there are more than two options for dealing with a mature codebase. "Good programmers know what to write. Great ones know what to rewrite (and reuse)."
Yeah, sorry about posting an item from Medium. I've been trying to cut down
|
|
|
|
|
I miss Roslyn on that list.
|
|
|
|
|
Quote: Should you rewrite your application from scratch
Better question: should you rewrite your application with scratch? Might make it more fun.
|
|
|
|
|
I'm working on software that is in it's 11th year of life. Over that time, well over two dozen programmers have contributed to the code base. And it looks like it (both age and multiple contributors). We deploy updates every four months (for the last 11 years), and it has never had a rewrite. The business rules change every few months, and the database wasn't really designed to accomodate that. As a result, we have stored procs that are THOUSANDS of lines long. Believe it or not, there is functionality to run a series of sql jobs that take almost nine hours to complete. From the website.
If there was any software that needed a rewrite from scratch, this is the one. Frankly, I don't want to be responsible for it, but it has to be done, and with a modern software stack.
".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
|
|
|
|
|
Google said there’s absolutely, positively, nothing to worry about the secret microphone in your Nest Secure smart home hub that it didn’t tell you about. Nope, not at all. Just an oversight, said Google. No need to be alarmed. Everything is just fine. They just 'forgot' to tell anyone about it
I may be a dinosaur, but I still don't really see the need (or use) for these things.
But I'm probably just a dinosaur.
|
|
|
|
|
Techcruunch said: After Google, which owns Nest, realized its customers didn’t like being deceived or having their privacy violated
Um... Wha..?
Say again?
They didn't realise something so central to their core business?
Yeah, OK.Google said: The on-device microphone was never intended to be a secret and should have been listed in the tech specs
Yes, be fair.
The tech specs only list important, complicated things like sticky tape, so it's obvious that something as trivial as a hardware element that has to be bought, brought to manufacture, and physically installed (along with drivers and software written to support it) could be overlooked.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Ah, the "We're not evil, just hopelessly incompetent" defense.
|
|
|
|
|
/shrug. It works for governments. 
TTFN - Kent
|
|
|
|
|
Kent Sharkey wrote: I may be a dinosaur, but I still don't really see the need (or use) for these things.
These things? Home security systems? Give me your home address and I'll stop by to discuss.
If you're talking about the plethora of ridiculous home assistant "smart" speakers... yeah, I totally agree with you.
The Beer Prayer - Our lager, which art in barrels, hallowed be thy drink. Thy will be drunk, I will be drunk, at home as it is in the tavern. Give us this day our foamy head, and forgive us our spillage as we forgive those who spill against us. And lead us not to incarceration, but deliver us from hangovers. For thine is the beer, the bitter and the lager, for ever and ever. Barmen.
|
|
|
|
|
Mike Mullikin wrote: If you're talking about the plethora of ridiculous home assistant "smart" speakers... yeah, I totally agree with you.
Yeah, those things, sorry. 
TTFN - Kent
|
|
|
|
|
Translation:
It was never intended to be a secret once it became known and went viral.
|
|
|
|
|
you mean its bugged.
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
