Archiv für das Tag "Webdev"

CSS Grid Support - Hello Opera

Well, to be honest, I hadn't Opera on my watch list, so it slipped my attention for a while. But, Opera, too, already has CSS-grid support. :-)

CSS Grid Support - Safari now haz it, as well

Ja tschakka! Anfang des Monats Firefox, sehr kurz darauf Chrome, dann Opera, jetzt Safari -- es tut sich mächtig was in Sachen CSS-Grid.

Nachtrag: Das Update auf iOS 10.3 hat dem dem dortigen Safari ebenfalls CSS-Grid beigebracht:

CSS Grid Support - Chrome now haz it, too

Uh baby. Nur einen Tag nachdem Firefox einen in Sachen CSS-Grid Support vorlegte: Chrome konnte das natürlich nicht auf sich sitzen lassen, und so ist heute der CSS-Grid-Support im neuen Chrome 57 gelandet. Grid it while it's hot. :-)


CSS Grid Support - Firefox haz it

Das wohl spannendste derneueheissescheiss Feature für moderne Weblayouts ist gestern einen Schritt näher an die normalen Webnutzer rangerückt: Firefox unterstützt in der nun aktuellen Version 52.0 CSS-Grids! Und Chrome wird das auch noch im März hinter dem "Experimental" Flag hervorholen.

Darauf warte ich schon seit über einem Jahr, denn CSS-Grids machen so viele Problemchen, mit denen die werte (Frontend) Webentwicklung in Zeiten der Cholera Verunsicherung mobilen, also in Zeiten, in denen niemand mehr verlässlich sagen kann, welches Gerät mit welchen Eigenschaften denn nun gerade auf der ...


git pull tooligans

Jake Archibald ponders on Twitter about the state of web development

(make sure to read the whole thread)

— it seems that many developers are more obsessed about controlling the onslaught of complexity by creating and maintaining a plethora of tools, for pre- and post-compiling, minifying, deploying, testing, and automating every possible aspect of 'the workflow'.

Being a web developer seems to be more and more about mastering tools, not creating solutions that benefit the users. And how easy it is to get lost in this tool driven jungle, to ...

Writing Less Damned Code - Heydon Pickering @Beyond Tellerrand Conference, Berlin 2016

Vimeo direct slaponthebackofthehead

Concatenating, minifying, compressing, caching: all serviceable ways to improve the performance of web interfaces. But none are as effective as not coding something in the first place. Code that don't exist is infinitely performant and extremely easy to maintain and document. This talk will identify some examples of front-end code that are either not needed at all, make the interface worse just by being there, or can be replaced by something much, much simpler. Say hello to unprogressive non-enhancement.

Less is Less!

the C in CSS, it is not 'component'.

(my recent web dev timeline in a nutshell; everyone seems to have a strong opinion around that fact)

A Front End Developer is Aware - Chris Coyier

In a general sense, the front end developer is positioned in the middle of lots of other jobs. Everybody involved in a web team ends up talking with the front end developers. That makes sense. The front end developers create the actual thing people interact with. Everything comes together with the front end developer. Perhaps that's why it's such a fun job!

Progressive Web(rocker)App

Ha! It! Really! Works!

I have to admit I was a bit sceptical of the outcome after I tweaked and added things and bits of my website at the Indiewebcamp in Nuremberg, setting up a service worker and offline caching things, adding a manifest file … while in theory I understand what all of this was supposed to do, I felt a bit dumb for not completly grasping how to control the stuff.

So as so often when learning new tricks on the web, it started with copy/pasting a working solution and trying to adapt this to my ideas.

But ...

  • Seite 1 von 2
  • 1
  • 2
  • »

The design, the code, 1923 texts, the illustrations, and some photos are made by me.

Motorisiert durch WordPress