Microsoft, Skype is your platform. You are the one who decides which adds get to be shown…
So why oh why do you allow deceptive and abusive adds like the one in this sreenshot?
These adds are tricking people into believing there Windows computer has problems that aren’t really there. These adds are bad for the reputation of Windows. That other companies don’t care about this I understand, but I would have expected Microsoft itself to be more protective of it’s own good name.
Please stop allowing adds like these!
SEE ALSO: Oracle turns Java into malware!
It’s been a while since I last posted here. That’s because I’ve been very, very busy. I joined a startup company mid december and things have been very hectic.
The company is named Brautschloss (which is German for ‘Bride Palace’) and we are organizing a bridal fair where bridal stores can purchase the dresses for in their store from the various brands.
Breaking the 50,000 view barrier with just my own ramblings. Wow.
Who would have thought?
Thanks to you all for reading my blog.
And thank you VERY MUCH for commenting!
On now to 100,000!!
There are a maximum of 4 bytes in a single UTF-8 encoded unicode character.
And this is how the encoding scheme works in a nutshell.
|Bits of code point
||First code point
||Last code point
||Bytes in sequence
Source: Wikipedia (also confusingly showing 6 possible bytes when truly 4 is the maximum)
Wait, I heard there could be 6?
You heard wrong.
Today at work we found a subtle issue that will sometimes break your code in very difficult to find ways. Read this if you don’t like days of bug hunting for mysterious issues only occurring on high-load production machines.
Ever wrote code like this?
private static final DateFormat FORMAT = new SimpleDateFormat("yyyy-MM-dd");
Most of us did. It’s the most intuitive way to use a DateFormat to format some Date object as a human-readable String.
Unfortunately, it’s wrong.
When used in a multi-threaded context (e.g. in a Servlet), this will end up breaking. Sometimes. When you least expect it.
Back in september of 2010 I wrote a blog post about the Breaking Float rendering bug I found in WebKit, the rendering engine backing the Safari, Chrome and Opera browsers. In april of 2013 the WebKit team landed a patch which would eventually end up in the browsers relying on WebKit. Case closed right? Well, not quitte…
Blink brought it back
Coincidentally, in the same month that the Breaking Float bug was fixed, Google forked WebKit into a new project called ‘Blink’. And the fix to the Breaking Float bug was not in the fork. Over time, the Chrome browser switched over to using Blink instead of WebKit, bringing back the issue in all it’s breaking glory.
Just after midnight on monday I posted my first sports-related post. I’m not much into sports myself but I happen to know someone who is and often makes predictions about sports matches that come true. So I thought it would be fun if he would share some predictions about the 2014 World Cup that is drawing to a close right now. So I wrote a post about his World Cup predictions.
The Oracle’s first prediction was on the money
My ‘Oracle’ as I will call him from now on predicted that Germany would convincingly beat Brazil. Well it does not come much more convincing than winning with 7 to 1!
The Brazilian supporters where shocked at what they were seeing. Germany walked all over Brazil and they are off to the finals!