While this kind of policy doesn't seem like a stretch for most companies, YouTube management doesn't seem to understand how their own platform works. Making videos bitching about YouTube is a pastime that all YT content creators do, and generates a lot of views and ad-revenue to boot.
I've seen hundreds of YouTubers posting videos in my recommended feed just this past week complaining about the new changes to the YouTube monetization program. To YouTube's credit, they let people criticize them to no end, unlike some of their competitors (e.g. VidMe), at least until now.
For musicians specifically, I've noticed that many I have followed over the years have moved to Twitch and Patreon because monetization seems to suck on YouTube.
In the case of YouTube, they've done a shit job with advertisers too. The mass pullout of advertisers from things like the Adpocoylpse is proof of that.
The Adpocoylpse shows Google has no clue how their own platform works. All these drama-alert things like Pewdiepie and Logan Paul are not a surprise to normal YouTube viewers, yet caught YouTube management off-guard.
And it also shows Google has no idea how to pitch, negotiate, and sell to advertisers, because the bottom line has been that the demographics that advertisers seek to reach actually want to watch the stuff advertisers are freaking out over. Google should fire their current management and hire away big media execs that understand the biz and and have sway with advertisers.
I didn't forget. I just didn't think it would be interesting to the OP.
- I didn't think optionals would be a familiar concept to a C++ programmer. They are also integrated with the type system and I already listed the type system.
- C++ has lambda functions now. Swift has simpler syntax, but I already listed syntax.
I am curious if you say C++ lambdas are not first-class citizens. What are examples of its limitations?
This doesn't break shipped apps. Any app using Swift right now deliberately has everything compiled and bundled to be self-contained. Changes to Swift have no impact on shipped binaries.
- Emphasizes compile time & native code much like C++ - More powerful type system - Safer language by design - Native string type built into the language that is Unicode compliant (not a library like C++) - No header files - Large standard library (Foundation) being made cross-platform with built-in things like networking, date handling, file system abstractions, regex - Features to replace the runtime things that GUI programmers found useful in Obj-C/Cocoa, but doing them at compile time and with stronger type safety - Syntax is not constrained by C legacy compatibility - Will eventually have stable ABI so you can share binary libraries
I know they're going to pick something super lame like Oreo, but given they are launching during the eclipse I'm half hoping for a pattern breaking "Android Occultation" or at least Oatmeal Cookie if they gotta stick with the sweets.
Is Microsoft paying Canonical for all this? As I understand it, the Linux subsystem for Windows required Ubuntu up until now. Seems like this would entail some kind of licensing agreement for Ubuntu.
So I wonder if Microsoft is paying Canonical. If the number is large enough, Microsoft could ultimately influence the direction Ubuntu takes.
I miss the hard physical write-protect tabs we had on floppy disks.
Nowadays, if you plug in a USB stick or external hard disk, you have to trust that the OS won't write or screw up your data in any way. Ignoring bugs and and "helpful" OS's who try to reformat if they don't recognize the filesystem, with viruses and other malware, you can't trust software to enforce read-only modes.
Watch Casey Muratori's Handmade Hero, where he codes a game live on Twitch from scratch with no 3rd party libraries.
His entire effort is fueled by his desire to educate the next generation of developers with an understanding of how computers *actually* work, which is something he feels is both important and has been lost.
The second is from all the new languages like Go, Rust, Swift. All these new languages need libraries so they all built in good C interoperability so they could be useful immediately without requiring ground up new implementations of everything. So I'm seeing more new pure C libraries being created now than I've seen in a very long time. Library developers know that their libraries will be usable from every language if they write it in pure C.
The third is from IoT. Embedded developers never left C. Now with IoT growing, C lives on.
In all of these cases, they might fly under TIOBE's radar. Most of these people probably don't need to search for C. They already know it and are too busy working on their projects.
Apple also has sandboxing for Mac apps and every Mac App Store app is required to use it. Non-MAS apps can enable it when signing with Developer ID (which also makes GateKeeper happy).
The Mac file browser is now a special process that is designed to work with the sandbox. When you user uses the system file panels in a Mac app, it is treated as an explicit opt-in to tell the sandbox that the user has granted permission to access the file.
For most apps, this sandboxing system works very well and everybody should be using something like this.
Building a sandboxed Tor browser on Mac should be a straight forward thing and I hope is a short-term goal for Tor.
Though I should say that it would be a good idea for Samsung and other manufacturers to come up with their own game.
Largely ignored by everybody is how good Apple's OS engineering team with respect to battery consumption and performance. Apple invested a lot of resources to keep their software stack very efficient. This is how they can get away with shipping ultra-thin phones with long battery life with relatively boring/conservative battery specs.
Unfortunately for Samsung, the problem may have crossed the threshold of marketing disaster. While the typical hype might be forgotten quickly, this problem turned into a federal offense to carry these phones on a US carrier.
The fact that air travelers must now suddenly be aware of their phone's make and model, and explicitly be aware of the Galaxy Note brand as "the banned one", is a PR disaster.
Most people don't know or care about these details which is why most of these events blow over after a few months. But this time, you are inconveniencing *all* air travelers to check their phones and become aware of the Samsung Galaxy Note brand in a bad way. So it's not just Samsung owners who have to pay attention to this. And the threat of breaking US federal law by not paying attention to this forces people to actually pay attention and inconvenience themselves, which helps drill in the bad brand connotation in a longer term way.
Then Samsung setting up recall kiosks at airports, while the right thing to do, is also a negative reinforcement of the brand image.
Samsung's saving grace is that they seemed to try to handle the problem in an honest way, without any coverup. (YouTube takedowns notwithstanding.) This helps keep the trust with their customers. If it later comes out that that Sansumg did something questionable, then they will have another PR disaster and I bet they will ditch the brand for sure.
Most people aren't using a data cable any more. Remember when Apple finally allowed people to "cut the cable" and the rest of the world said, "about damn time"? Also, remember that the majority of people have Windows PCs, not Macs, and iTunes on Windows is a favorite past time for everybody to bash. Hence, the vast majority of people are using their iPhones in cordless mode, and presumably real world Wi-Fi on the iPhone is not enough to saturate the write limit.
And for those who do still transfer by cable, the vast majority of them are copying data back to their PC, not the other way around. The 32GB storage is too small. People are trying to offload pictures and videos they recorded on the go to free up space. So the write speed on the iPhone isn't significant for this case.
The most mainstream, intensive, data writing operation I can think of is video recording with the phone. As long as the iPhone's storage can keep up with how fast it can encode/dump bits, that is all that is needed. That was probably Apple's internal target spec, and paying any more for faster write performance is throwing money down the drain for both Apple and the customer they pass the cost on to.
While this kind of policy doesn't seem like a stretch for most companies, YouTube management doesn't seem to understand how their own platform works. Making videos bitching about YouTube is a pastime that all YT content creators do, and generates a lot of views and ad-revenue to boot.
I've seen hundreds of YouTubers posting videos in my recommended feed just this past week complaining about the new changes to the YouTube monetization program. To YouTube's credit, they let people criticize them to no end, unlike some of their competitors (e.g. VidMe), at least until now.
For musicians specifically, I've noticed that many I have followed over the years have moved to Twitch and Patreon because monetization seems to suck on YouTube.
In the case of YouTube, they've done a shit job with advertisers too. The mass pullout of advertisers from things like the Adpocoylpse is proof of that.
The Adpocoylpse shows Google has no clue how their own platform works. All these drama-alert things like Pewdiepie and Logan Paul are not a surprise to normal YouTube viewers, yet caught YouTube management off-guard.
And it also shows Google has no idea how to pitch, negotiate, and sell to advertisers, because the bottom line has been that the demographics that advertisers seek to reach actually want to watch the stuff advertisers are freaking out over. Google should fire their current management and hire away big media execs that understand the biz and and have sway with advertisers.
I didn't forget. I just didn't think it would be interesting to the OP.
- I didn't think optionals would be a familiar concept to a C++ programmer. They are also integrated with the type system and I already listed the type system.
- C++ has lambda functions now. Swift has simpler syntax, but I already listed syntax.
I am curious if you say C++ lambdas are not first-class citizens. What are examples of its limitations?
This doesn't break shipped apps. Any app using Swift right now deliberately has everything compiled and bundled to be self-contained. Changes to Swift have no impact on shipped binaries.
- Emphasizes compile time & native code much like C++
- More powerful type system
- Safer language by design
- Native string type built into the language that is Unicode compliant (not a library like C++)
- No header files
- Large standard library (Foundation) being made cross-platform with built-in things like networking, date handling, file system abstractions, regex
- Features to replace the runtime things that GUI programmers found useful in Obj-C/Cocoa, but doing them at compile time and with stronger type safety
- Syntax is not constrained by C legacy compatibility
- Will eventually have stable ABI so you can share binary libraries
Google used to be more ambitious.
From googol (100 zeros) and indexing all the worlds information, reduced to ABCs and counting like Sesame Street.
If they were still cool, it would be XLII, the answer to life, the universe, and everything.
Good thing they changed their name to Alphabet. They'll never have any problems with that.
I know they're going to pick something super lame like Oreo, but given they are launching during the eclipse I'm half hoping for a pattern breaking "Android Occultation" or at least Oatmeal Cookie if they gotta stick with the sweets.
Android Ocular Jelly
With all the positive buzz around tea, I would have liked to see another group in these studies for tea vs. coffee.
Is Microsoft paying Canonical for all this? As I understand it, the Linux subsystem for Windows required Ubuntu up until now. Seems like this would entail some kind of licensing agreement for Ubuntu.
So I wonder if Microsoft is paying Canonical. If the number is large enough, Microsoft could ultimately influence the direction Ubuntu takes.
MOD UP. This is a really important detail about Alibaba and Mayer's role.
That's the other thing I miss: just being able to kill the power without an OS shutdown phase (like with MS-DOS).
I miss the hard physical write-protect tabs we had on floppy disks.
Nowadays, if you plug in a USB stick or external hard disk, you have to trust that the OS won't write or screw up your data in any way. Ignoring bugs and and "helpful" OS's who try to reformat if they don't recognize the filesystem, with viruses and other malware, you can't trust software to enforce read-only modes.
Watch Casey Muratori's Handmade Hero, where he codes a game live on Twitch from scratch with no 3rd party libraries.
His entire effort is fueled by his desire to educate the next generation of developers with an understanding of how computers *actually* work, which is something he feels is both important and has been lost.
https://handmadehero.org/
I enjoyed his recent performance in Star Trek: Prelude to Axanar. I was really looking forward to him reprising his role for the real Axanar.
RIP Richard Hatch
I'm seeing a resurgence in C. It seems to be coming from several different directions.
The first is from people like Mike Acton:
CppCon 2014: Data Oriented Design
https://www.youtube.com/watch?...
The second is from all the new languages like Go, Rust, Swift. All these new languages need libraries so they all built in good C interoperability so they could be useful immediately without requiring ground up new implementations of everything. So I'm seeing more new pure C libraries being created now than I've seen in a very long time. Library developers know that their libraries will be usable from every language if they write it in pure C.
The third is from IoT. Embedded developers never left C. Now with IoT growing, C lives on.
In all of these cases, they might fly under TIOBE's radar. Most of these people probably don't need to search for C. They already know it and are too busy working on their projects.
Damn it!
"The man with the golden pipes", Gary Owens passed away last year. He is best known for Laugh-In, Space Ghost, and the Space Quest narrator.
If he just lasted a little longer, his voice could have been preserved forever with this kind of technology.
And a product that gives snarky, sarcastic, yet funny responses in an awesome sounding voice would be fun.
User: "What is the weather like today?"
Gary Owens response: "The air smells damp and oppressive, like a wet nun."
RIP Gary Owens
====
A Tribute to Gary Owens
https://www.youtube.com/watch?...
Funny Radio Liners By Gary Owens - Comedy Commercials
https://www.youtube.com/watch?...
Ways to die Space Quest 4
https://www.youtube.com/watch?...
Memorable Moments and Lines from Space Quest 4
https://www.youtube.com/watch?...
Memorable Moments and Lines from Space Quest 6
https://www.youtube.com/watch?...
Apple also has sandboxing for Mac apps and every Mac App Store app is required to use it. Non-MAS apps can enable it when signing with Developer ID (which also makes GateKeeper happy).
The Mac file browser is now a special process that is designed to work with the sandbox. When you user uses the system file panels in a Mac app, it is treated as an explicit opt-in to tell the sandbox that the user has granted permission to access the file.
For most apps, this sandboxing system works very well and everybody should be using something like this.
Building a sandboxed Tor browser on Mac should be a straight forward thing and I hope is a short-term goal for Tor.
Though I should say that it would be a good idea for Samsung and other manufacturers to come up with their own game.
Largely ignored by everybody is how good Apple's OS engineering team with respect to battery consumption and performance. Apple invested a lot of resources to keep their software stack very efficient. This is how they can get away with shipping ultra-thin phones with long battery life with relatively boring/conservative battery specs.
To support your point, remember what Samsung designs looked like before the iPhone?
Here's a photo reminder:
http://photos2.appleinsider.co...
Apple support has always treated me well.
When I had a problem with my Mighty Mouse ball (out of warranty), they gave just me a new one on the spot at the Apple Store.
When they made a screwup with my developer account, they gave me a free peripheral of my choice (I asked for a second Macbook Pro charger).
When I had a problem with my iMac (under warranty) they sent me boxes and shipping labels and offered to have it picked up to my house.
Apple has given me among of the best customer service of all the companies I've ever done business with.
Wow, a Donald Duck diamond sounds cool! Make it a Scrooge McDuck diamond, and I'm sold.
For all the hype about being a Mac event, seems like a massive disconnect that there is no Mac support for the TV app. (AppleTV, iPhone, iPad)
They even showed a Macbook Pro with 3 displays during the event. (Hello? How about putting TV on one of the displays?)
Come on Apple. I expected better from you.
Unfortunately for Samsung, the problem may have crossed the threshold of marketing disaster. While the typical hype might be forgotten quickly, this problem turned into a federal offense to carry these phones on a US carrier.
The fact that air travelers must now suddenly be aware of their phone's make and model, and explicitly be aware of the Galaxy Note brand as "the banned one", is a PR disaster.
Most people don't know or care about these details which is why most of these events blow over after a few months. But this time, you are inconveniencing *all* air travelers to check their phones and become aware of the Samsung Galaxy Note brand in a bad way. So it's not just Samsung owners who have to pay attention to this. And the threat of breaking US federal law by not paying attention to this forces people to actually pay attention and inconvenience themselves, which helps drill in the bad brand connotation in a longer term way.
Then Samsung setting up recall kiosks at airports, while the right thing to do, is also a negative reinforcement of the brand image.
Samsung's saving grace is that they seemed to try to handle the problem in an honest way, without any coverup. (YouTube takedowns notwithstanding.) This helps keep the trust with their customers. If it later comes out that that Sansumg did something questionable, then they will have another PR disaster and I bet they will ditch the brand for sure.
Most people aren't using a data cable any more. Remember when Apple finally allowed people to "cut the cable" and the rest of the world said, "about damn time"? Also, remember that the majority of people have Windows PCs, not Macs, and iTunes on Windows is a favorite past time for everybody to bash. Hence, the vast majority of people are using their iPhones in cordless mode, and presumably real world Wi-Fi on the iPhone is not enough to saturate the write limit.
And for those who do still transfer by cable, the vast majority of them are copying data back to their PC, not the other way around. The 32GB storage is too small. People are trying to offload pictures and videos they recorded on the go to free up space. So the write speed on the iPhone isn't significant for this case.
The most mainstream, intensive, data writing operation I can think of is video recording with the phone. As long as the iPhone's storage can keep up with how fast it can encode/dump bits, that is all that is needed. That was probably Apple's internal target spec, and paying any more for faster write performance is throwing money down the drain for both Apple and the customer they pass the cost on to.