CEO/Principal Consultant at INNOQ, he/him, software architect, RESTafarian, conference tourist. Works at innoq.com. Fediverse: @stilkov@innoq.social

Germany
Joined April 2007
Filter
Exclude
Time range
-
Near
Replying to @assaf
@assaf Do you really believe that is the reason? Anyway, I just find it sad that Twitter seems to be on the way to yet another closed system
2
I never had a laptop that came even remotely close to my new Macbook Air's battery life. Seriously impressive.
1
1
1
Very true: “If those services don’t trust me enough to give me an RSS feed, why should I trust them with my data?” adactio.com/journal/6291/
1
5
3
Replying to @KaiWaehner
@KaiWaehner @clemensv Not a single slide was used
1
Awesome presentation by @clemensv on Azure; bonus points for matching regional accent and 0 bullshit content
3
Analog equipment being put to good use by @clemensv (at @innoQ company event)
At @innoQ event: MapReduce, background request processing in Wicket, functional parallelism in Scala, & looking forward to guest @clemensv
1
Two-day @innoQ event on parallelism & concurrency, starting today with Tianhe-2/Xeon Phi, Concurrent Java, Jeopardy & Clojure reducers.
1
Replying to @rotnroll666
@rotnroll666 Had that one, replacing it with the new one for the battery life.
If true, this seems pretty much OK (new maxed-out MBA 11'')
2
1
Replying to @mikebild
@mikebild Das ist das falsche Medium hier. Lass uns das lassen. Lieber mal irgendwann persönlich.
1
@mikebild 5) Funktionierende Browser-Controls (Back, Forward, Refresh ohne Verrenkungen
1
Replying to @mikebild
@mikebild Und weicher: Bessere, weil klarere und zukunftssichere, frameworkunabhängige Architektur
3
Replying to @mikebild
@mikebild 6) Schnellere Ladezeiten 7) Crawler (Google)-Freundlichkeit 8) klares Vorgehensmodell + gute Testbarkeit
2
Replying to @mikebild
@mikebild 4) Klare Separation of Concerns zwischen Client und Server 5) reichhalte Komponentenbibliotheken in JS
2
Replying to @mikebild
@mikebild 1) Nutzung aus nicht JS-Clients 2) Nutzung auch bei defefektem/noch nicht geladenem JS 3) keine Duplizierung von Logik
1
Replying to @mikebild
@mikebild Steht denn dazu deiner Meinung nach gar nichts in unseren Artikeln?
Replying to @mikebild
@mikebild Häh? Ich habe doch nichts gegen Updates per Ajax? Das ist doch nicht der Punkt?
1
Replying to @mikebild
@mikebild “By rendering page content on the server and deferring all JavaScript execution until well after that content has been rendered”
1