|
You could use different shades of red to indicate the severity of the error...
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Kent Sharkey wrote: I'm so glad that the feedback they listen to is, "we want more colours in the command shell" But that's not the feedback they listened to. The feedback they listened to was "we want more colors in the command shell".
Those British colours will have to wait until the next version.
|
|
|
|
|
Even after seeing the reference article I'm sure you made it up... It can not be real!!!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
NY Times breaking: "In a statement, Yahoo said user information — including names, email addresses, telephone numbers, birth dates, passwords, and in some cases security questions — was compromised in 2014 by what it believed was a “state-sponsored actor.” It did not name the country involved."
[^]
It will be interesting to see if this affect the current possible sale negotiations between Verizon and Yahoo. imho, it also raises a question about why we are finding this out now.
Note: I mis-read the article as saying 500k accounts were hacked, perhaps because I couldn't imagine Yahoo having 500 million users. I still have trouble believing that.
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008
modified 22-Sep-16 16:16pm.
|
|
|
|
|
Oh no!!!
They got all my incoming SPAM!!!!!!
|
|
|
|
|
Not sure what's worse, they covered it up for two years because they wanted to look good to potential buyers, but some disgruntled ex-employee spilled the beans.
or
They didn't even know for two years.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
I don't consider it a big deal as the passwords were hashes (per reuters[^]) and the remaining data is more or less stuff you can find on spokeo or related websites.
The negotiations are complete and I don't see Verizon backing out, but I could be wrong. Verizon is buying Yahoo for advertising and competitive leverage, not for the junky web portal. 4.83 billion for Yahoo Core is pretty cheap if you consider they are in the top 5 visited websites in the world.
I am biased as my junk email service is through them, but more importantly, I've owned shares in YHOO for 2.5 years now. They own 15% of Alibaba and back then, it was the only way you could get your hands on it.
|
|
|
|
|
BillWoodruff wrote: Note: I mis-read the article as saying 500k accounts were hacked, perhaps because I couldn't imagine Yahoo having 500 million users. I still have trouble believing that.
Have you been living under a rock?
Although they are less successful in the west... Yahoo has massive penetration into many Asian-Pacific countries. In the last decade Yahoo had a much larger Asian presence than most other U.S. tech firms... including Microsoft and Google. Some countries such as Vietnam at one point had extremely high percentages of their population exclusively using yahoo.com email accounts.
Much of that success is slowly eroding away over time.
Best Wishes,
-David Delaune
|
|
|
|
|
We all know accounts are not users. How many people have abandoned accounts where spam took over?
Of more interest to me, AT&T uses Yahoo! as the Internet portal for their Internet and Mobile account holders. Is AT&T allowing Verizon to take over responsibility for its accounts without a qualm?
|
|
|
|
|
LinkedIn Learning combines the content from Lynda.com with LinkedIn’s professional data and network. Who better to learn from than the site that lets you know when coworkers are starting to look for a new job?
|
|
|
|
|
LinkedIn don't seem to know what they are at the moment - they tried a bit of social networking stuff with Groups but that seems to be hidden away now, they have user generated articles but again that seems to be on the wane and the news stream is basically Facebook without real life friends...
|
|
|
|
|
LinkedIn Learning combines the content from Lynda.com with LinkedIn’s professional data and network.
How is this different than them spamming me about lynda for the last year and change.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
New name, so it's all new spam?
TTFN - Kent
|
|
|
|
|
With this release, TypeScript delivers close ECMAScript spec alignment, wide support for JavaScript libraries and tools, and a language service that powers a first class editing experience in all major editors; all of which come together to provide an even more productive and scalable JavaScript development experience. In case that's your type
|
|
|
|
|
In Windows 10 RTM last year we introduced a new MIDI API, accessible to UWP Apps on virtually all Windows 10 devices, which provides a modern way to access these MIDI interfaces. "By pressing down a special key, it plays a little melody"
|
|
|
|
|
Kent Sharkey wrote: which provides a modern way to access these MIDI interfaces. And, note how mums-the-word on what, exactly, Windows 7 & 8 "provide[d as it pertains to] a way to access MIDI devices".
|
|
|
|
|
They could make it tighter timing wise.
But no. now the ill fated uw get midi - yawn, and the rest of us get a wrapper and it's overhead.
|
|
|
|
|
Hi All
I'm the author of the blog post here. Through the wonders of the web, I've found you all referencing it.
Some clarification for you:
- We've had (and still have) two previous MIDI APIs: DirectMusic and MME. Both of those are still available, but only work on desktop PCs. They're also not flexible enough to easily handle new transports like Bluetooth in a way we were happy with.
- We did fix some minor MIDI Jitter and timing in Windows 10 RTM when we created this API. In the end, however, you're at the mercy of USB which, given how it routes, is going to add a very small amount of jitter and latency. Those amounts are still less than the DIN MIDI wire speed, though. Of course, Bluetooth has higher latency and jitter and depends on quality of space in the room. We're competitive with what Apple does there (and compatible with them), but it's not as tight as USB. For that reason, many people tend to use Bluetooth MIDI for secondary controls, not for banging our riffs on a keyboard. You can, but IMO, it's not the best experience.
- The way DAWs typically deal with latency and jitter is to schedule MIDI messages. We don't have that yet, but it's on the backlog for consideration.
- In our own testing, the wrapper doesn't add any meaningful latency; it's working at function call speeds. The UWP MIDI APIs were always accessible to desktop applications (not true of all UWP APIs) but some companies felt the ceremony required to call from a Win32 app was a bit ... opaque. I agree, so had this work done by a colleague on the team. Feel free to take a look at the code on GitHub and try it out. We're happy to consider pull requests if you have suggestions.
void winrt_midi_out_port_send(WinRTMidiOutPortPtr port, const unsigned char* message, unsigned int nBytes)
{
MidiOutPortWrapper* wrapper = (MidiOutPortWrapper*)port;
wrapper->getPort()->Send(message, nBytes);
}
...
void WinRTMidiOutPort::Send(const unsigned char* message, unsigned int nBytes)
{
if (nBytes > mBuffer->Capacity)
{
mBuffer = ref new Buffer(nBytes);
mBufferData = getIBufferDataPtr(mBuffer);
}
memcpy_s(mBufferData, nBytes, message, nBytes);
mBuffer->Length = nBytes;
mMidiOutPort->SendBuffer(mBuffer);
}
Beyond that, it's worth pointing out that many have been using MIDI wrapper libraries since the dawn of time. It's never really been a problem.
The C# helper library I wrote is for people more familiar with that language. In that, I'm trying to make it simple to implement MIDI functionality in apps, including somewhat esoteric stuff like NRPN and RPN.
If performance is a primary concern, I'd use the C version. If it's an enormous concern, the source is available so that you can incorporate the calls directly in your app and do things like reuse buffers if you want. In practice, this hasn't been necessary, but we don't want to force the final word there.
Hope that helps.
Pete
|
|
|
|
|
You've only waited 11 years to come back to Code Project Welcome back Pete.
This space for rent
|
|
|
|
|
Heh, thanks Pete. Yes, it has been quit a while.
CodeProject thinks it was 1999 when I was last on, but my message history says it hasn't been quite that long.
Pete
|
|
|
|
|
Pass the word around the office, Pete - a bigger Microsoft dev (or even evangelist) presence on CodeProject would, I think, not be unwelcome.
|
|
|
|
|
Thanks Mick
I'm in Windows now, no longer in evangelism. In DX/DPE, most of the evangelists are doing Azure these days. I would need to look back around here to see if that's a fit.
I feel like there used to be many communities we were all involved with but have since lost touch with. I'm active in some music communities, but not so much in places like Code Project these days.
Pete
|
|
|
|
|
The ambiguity and variance of the architect role, combined with the fact that architect is nominally ‘above’ developers, creates a breeding ground for interpersonal friction. Bonus #0: Isn't it obvious that they other guy is an idiot?
|
|
|
|
|
|
I'd say #0 is, which they do touch on, "Nobody knows what an architect is, even the architects."
|
|
|
|