NEW INTERVIEW: Former Chairman of Sony Entertainment on Nintendo's Everlasting Intellectual Property

'Mario is probably impervious to extinction'

$NTDOY

https://t.co/MI0mMmSDsf

Nintendo has 100 years of experience in gaming.

'They are the masters in this field'
'As a platform holder, our job is to create a wider audience, continually.'
'I think Nintendo really understands the game design maxims for a handheld platform and then how to leverage their very powerful IP vault in that medium.'
It seems Fortnite and Roblox is additive to the industry and not exactly zero-sum vs AAA games?
Parallels between gaming and film IP

'because gaming is so tied to technology (which) has to keep moving forward in order to bring more immersive experiences, previous generation games are not compatible with the new technology'
'If you talk about the IP power of gaming, it’s true, but it has these breaks in the cycle, where entire franchises can disappear, because you can’t access them anymore''
The faster technology moves, the greater the challenge in sustaining the value of the IP

'Given their history, I think it would be very difficult for Nintendo to do a bad iteration of Mario'

More from Tech

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
One of the best decisions I made during a very turbulent 2020 was to leave conventional coding behind and embrace the #nocode movement. @bubble made this a reality. Although my own journey thus far is premature, I’ve learned a lot so here’s a power thread on....


‘How I created @buildcamp sales funnel landing page in under 2hours’.

Preview here 👇

https://t.co/s9P5JodSHe

Power thread here 👇

1. Started with a vanilla bubble app ensuring that all styles and UI elements were removed. Created a new page called funnel and set the page size to 960px as this allows the page to render proportionately on both web and mobile when hitting responsive breakpoints.


2. Began dropping elements onto the page to ‘find the style’. These had to be closely aligned to our @buildcamp branding so included text, buttons and groups - nothing too heavy. Played around with a few fonts, colors and gradients and thus pinned down the following style guide.


3. Started to map out sections using groups as my ‘containers’ to hold the relevant information and imagery needed to pad out the sales pitch. At this point, they were merely blocks of color #ff6600 with reduced opacity set to 5% to ease page flair.

You May Also Like