designers-react-to-the-new-ps5-logo-(and-it’s-not-pretty)

(Image credit: Sony)

The new PlayStation 5 logo has been revealed, to much fanfare, at CES 2020. To say the moment was an anticlimax would be an understatement. In short, the new PS5 logo looks exactly like the old PS4 logo. Which, to be fair, looked an awful lot like the PS3 logo. See it in all its glory above.

Sony has been slowly releasing information about its next console over the past few months. It’s due to be released “Holiday 2020”. Sadly, this latest revelation wasn’t quite as exciting as we might have hoped – Sony has clearly decided the logo wasn’t broke, and no fixing was required (for more enduring brand marks, check out our guide to the best logos of all time). 

We quite like that the new logo gives the impression that it’s just the ‘2’ of the PS2 logo reversed and flipped (it’s not, incidentally, the PS2 logo was a whole lot more angular), but other than that there’s not really much to say.

PlayStation logos through the years

PlayStation logos through the years (Image credit: Sony)

If Sony execs thought this was a safe design choice that wouldn’t attract too much vitriol from the PlayStation community, they were sorely mistaken. The claws are out and the memes are rolling in fast. Read on for our pick of the most savage takedowns so far (you might also want to check out Twitter’s hilarious reaction to the Xbox Series X last month).

Many commenters are calling out Sony for being lazy…

Sony’s lead graphic designer coming up with the #PS5 logo#SonyCES pic.twitter.com/7xOJXBWHCFJanuary 7, 2020

You had one job Sony! #PS5 #PlayStation5 #SonyCES pic.twitter.com/jZVx4cZMQZJanuary 7, 2020

Don’t tell Sony but they accidentally emailed me the PS6 logo by mistake pic.twitter.com/gFHb4D6B4CJanuary 7, 2020

… but Mike Drucker’s tweet is probably a little closer to the truth.

The funniest part of the PS5 logo being identical to the PS4 logo is you *know* there were HOURS of meetings and discussions and notes and follow up calls and approvals for this design https://t.co/V9KLZCctbhJanuary 7, 2020

Or are there hidden messages that we’re missing? 

If you turn the PS5 logo upside down it spells SSD which means – and this is pure speculation – it will contain an SSD. pic.twitter.com/WfXL2lTbkpJanuary 7, 2020

Hmm. Find out everything we know so far on our sister site GamesRadar ‘s PS5 news and rumours roundup.

Read more:

why-i-moved-from-react-to-svelte-and-others-will-follow
Featured image

Photo by Aryan Singh on Unsplash

React was my go-to choice for many years

On October 14, 2015, I hosted the inaugural React Vancouver meetup. It was at a point were I had used React for the better part of the year and wanted to bring like-minded developers together.

React back then was, dare I say it, revolutionary in the web frontend world. Compared to the alternatives such as jQuery, Backbone.js or Angular 1.x, developing with React felt intuitive, refreshing and productive. Personally, the idea of isolated building blocks (aka components) really appealed to me as it naturally led to a structured, well organized and more maintainable code base.

Over the coming years, I kept a close eye on Angular 2.x , Vue et al but none felt like a wortwhile choice to jump ship.

Then I learned about Svelte

I first learned about Svelte in mid 2018, almost a year before version 3.0 was released (see below). “Computer, build me an app.” by Rich Harris is what got me hooked on Svelte.

If you’re not familiar with Svelte (https://svelte.dev/), please go to the website and spend 5 minutes reading the intro.

Read it? Really? Excellent ?

Once I watched the video, the main question in my mind was whether or not it’s worth learning Svelte and starting to use it for new or even existing projects. In all fairness, Svelte impressed me but it still wasn’t enough to embrace it fully.

Svelte 3.x

April 22, 2019 – Svelte 3: Rethinking reactivity was the blog post I had been waiting for.

Please take some time to read the blog post and watch the video – it’s about spreadsheets but I promise it’s fun ?

Why was this such a big deal? For one, the Svelte team had been talking about version 3 quite a bit and I wanted to see it in action. On the other hand, Svelte and its promise excited me even more than React did when first I heard of it.

I mentored web developers at that time and had spent quite a bit of time bringing them up to speed on React. Things like JSX, CSS-in-JS, Redux, create-react-app, SSR and other concepts needed to be learned, understood and to a certain degree mastered in order to develop React apps.

None of that was necessary with Svelte.





Hello {name}!

App.svelte

Simple enough? I agree. In fact, it is so simple I recommend it to my mentees who are new to web development.

Real quick, what’s going on in that code?

The script tag is where the component’s logic lives.

The style tag defines this component’s CSS – none of this leaks outside the component, so we can safely use h1 and it only applies to this component. It’s real CSS, not a Javascript object that pretends to be CSS or a string literal that pretends to be CSS.

At the bottom is the component’s HTML. Use variables with {myVariable}. Compared to React’s JSX, Svelte allows you to use the correct HTML tags such as for, class instead of forHtml and className. See “Differencs In Attributes” in the React documentation for a list of all attributes that are not standard HTML.

Let’s rebuild React examples

To give you an idea of what Svelte looks like compared to React, let’s rebuild what’s listed on https://reactjs.org/.

A Simple Component

See the code snippet above.

A Stateful Component

Interactive demo



Seconds: {seconds}
App.svelte

React: 33 lines

Svelte: 6 lines

An Application

Interactive demo



TODO

App.svelte


    {#each items as item}
  • {item.text}
  • {/each}
TodoList.svelte

React: 66 lines

Svelte: 43 lines

A component Using External Plugins

Interactive demo




  


Input