If you woke up tomorrow, and your internet looked like this, what would you do? Imagine all your favorite websites taking forever to load, while you get annoying notifications from your ISP suggesting you switch to one of their approved “Fast Lane” sites. Think about what we would lose: all the weird, alternative, interesting, and enlightening stuff that makes the Internet so much cooler than mainstream Cable TV. What if the only news sites you could reliably connect to were the ones that had deals with companies like Comcast and Verizon? On September 10th, just a few days before the FCC’s comment deadline, public interest organizations are issuing an open, international call for websites and internet users to unite for an “Internet Slowdown” to show the world what the web would be like if Team Cable gets their way and trashes net neutrality. Net neutrality is hard to explain, so our hope is that this action will help SHOW the world what’s really at stake if we lose the open Internet.If you’ve got a website, blog or tumblr, get the code to join the #InternetSlowdown here: https://battleforthenet.com/sept10th Everyone else, here’s a quick list of things you can do to help spread the word about the slowdown: http://tumblr.fightforthefuture.org/post/96020972118/be-a-part-of-the-great-internet-slowdown Get creative! Don’t let us tell you what to do. See you on the net September 10th!
via Battle For The Net.
IT must be easy, oh yeah. After years of courses and university and everything else, just because they were put together by the brightest educational minds you should be able in a second to program this new web application, integrate external web services, add a new GUI and adapt your friend’s broken Excel import, all while cleaning up grandma’s computer for the hundredth time. Even kids are to be taught programming, so it can’t be much in it right? How MANY times I heard this told in various ways “it can’t be so difficult”… Everybody has challenging jobs but as soon these involve computers everything should become a breeze, somehow. When did we get into this???
But I digress. So, first a bit of context: I thought it would be big time I followed my own thinking from a month ago (see “Proof of concept, with a concept”) and actually migrate the proof of concept code from “Ractive.js and vert.x integration over the event bus” to use Elasticsearch. Continue reading
Not long time ago I invited a work mate to join me at an Eclipse event. He declined, arguing he wouldn’t have time for stuff he’s not expecting to use. He had a point there, I had to concede. Continue reading
One problem I have when trying new technologies is actually seeing them in realistic situations – which translates to having a real use case for them. Think about this: when you build a “hello world” application you actually couldn’t be further away from the real world! I guess that’s why nobody calls it “hello real world” anyway… The whole experience you get from the proof of concept is just random installation trivia if you’re not using it to prove a point. That’s why it’s called “proof of concept” – it should have a concept, silly. Continue reading
There comes Epson with a new edition of their Moverio BT-200 – AR glasses, augmented reality that is. They look like a normal pair of dorky glasses like I see lots in the commuter train, on which tiny projectors display from the inside semi-transparent images.
Not huge new concept, even Garmin does the same for your front-shield window with their head-up projector. The Epson device however embeds gyroscopes and whatever else to properly track your reality, and augment it. No, I didn’t try it yet but I’d love to, and certainly NOT based on the dumb reviews I can read all over the net. Why dumb? Continue reading
When I first combined the Internet and programming it was the second half of the 90’s and all I knew was Java applets. Oh, there was also CGI but I somehow managed to skip over it. The approach was then quite natural: write small programs which will run in the browser and grab data from other programs – run in either other browsers or on the server. Or on other servers. I’m not saying the idea was easy and I only got that far before I moved on to other professional areas. Later when I came back to the web, things had settled differently: you had a servlet specification, a multitiered application to support them, big servers and everything was clear. Of course there was some bit of fight over technologies, gradual improvements here and there but the model was there already. Continue reading