trm42

Maybe there should be some kind of IoT security standards or maybe some Security Company testing and handling "Secure IoT device" rubber stamps to every tested and compliant device?

This is because every company that has been making "Things" for the last 5-100 years are now thinking about making IoT devices without understanding anything about Internet or Security. The Nissan Leaf or that toy maker Vtech cases are good examples of this.

A Quick starter for the rubber stamp list: 1. Authenticate every request 2. Use encryption in every phase (transport, passwords etc) 3. Really, handle basic Web security 4. Be really, really protective about your customers data in every way 5. Don't sell the data without consent from the customer

Urk, I take it you haven't used Lync outside of Windows? The Mac version is horrible mixture of Silverlight+HTML5+Standalone App in which none of the mentioned pieces can't handle the full functionality. On the other hand Skype and Hipchat just works (unless you get hit by the Skype bugs:p).

They have done awesome job but the Jolla Phone is old (and was low-end even when it was published compared to its price) and their tablet crowdsourcing project suffered quite badly as they lost some other funding for a moment and their device manufacturers sold the devices elsewhere as Android devices.

Basically Jolla has promised to refund the crowdsourcing funds within this year, but still it was big setback for the project. I've tested the tablet and it was surprisingly solid in H/W and S/W sense. Just hoping they'll survive and can get meaningful market share somehow. Kudos to them anyway.

And basically developers needed to remake (more or less) the apps from WP7.* to WP8. Nowadays they need to port apps from WP or from Desktop Windows to Windows Universal Apps, so what's the point if nobody's using those apps? :D

The UX design of the P* line and M600 was really something at the day. The last ones P1i and M600 started converting more and more of the UI to finger touch instead of stylus control. And it ran so smoothly on nowadays obsoleted hardware <3

I would like to have touch-phone with a full QWERTY keyboard. Just like the dev-only Nokia N950 ;-)

In hardware design sense it's really well engineered: https://en.wikipedia.org/wiki/Nokia_N950

According to rumors Nokia had lots of discussion with MS and Google about which platform they should take. Got the impression that the proposition from MS was somehow better and at least initially gave more room to move for Nokia. Later on got the impression that lots of things didn't went as was promised.

But, Nokia is still alive and the situation seems to be a lot rosier for them after selling the mobile phone business. They got good price and got really cheap loan from Microsoft as part of the deal. Of course in PR side Nokia didn't have to kick out the phone engineers. Microsoft is handling that still and getting the negative PR from that.

One has to remember that earlier Ericsson quit the phone business as well by selling that to Sony. Actually those phones got better after that :)

From the end-user perspective both Maemo and Meego phones felt really good but the Meego seemed to have a bit more innovative and more fluid UX. Liked both of them and would've gladly bought them if there would've been any promise of continuity.

The hardware of N95 was the pinnacle of Nokia engineering. They stuffed lots of new stuff there like A-GPS receiver, accelerometer, 3D-accelerated GPU, lots of flash storage, better camera etc but the Symbian UX was horrible (it was from the beginning but tech feature -driven engineers didn't understand that at all).

N95 had so much of features that nobody used them. They just were happy with all the stuff they never used. Been talking about the subject to lots of people who bought the phone then.

N95 was released the same year Apple demoed iPhone first time. N95 sold really well then. Nokia's old management has told afterwards they were so lulled by the success of N95 they were not worried about iPhone at all. They did N96 which was even more stuffed than N95 but with the same UX flaws.

One of the things Apple changed was how the software was perceived for phones.

Nokia (or the others) didn't update that much the firmwares for the old models. They just fixed the problems and added features to the new models. They were coming from simple phones that were not flashable in the beginning and they just wanted to sell more phones instead of supporting the old ones.

It's ironic how Apple is selling amazing amounts of phones with just few models and upgrading the software and features few times a year.

Yep that was one their problems. Bought an used Sony Ericsson P800 running UIQ and used it for years because it had ten times more ram than new Nokia Symbian phones in 2005-2007. Something like 10 MB vs 128. Of course the UIQ system was iPhone of the early 2000s but quite few noticed it and in Finland everybody were chanting Nokia Nokia Nokia.

EDIT: Forgot to say that few earlier Nokia models had accelerated GPU but the OS and the developers didn't use those, so they just stopped adding the GPUs later on ;D

It seems they are keeping Bada -> Tizen around just to have some leverage over Google. If some negoatiations are really tough with Google, they can say "hey, let's forget the whole thing and we'll start using Tizen instead of Android". They don't really want to do that but it's a good plan B.

Nowadays QT is doing well with LGPL + Commercial licensing. It's really good thing Nokia didn't hug it to death.

The management got too rosy picture of what Windows Phone 7 was (a quick hackish MVP, nothing more, like the first iPhone few years earlier) and they were really surprised when upgrade path to Windows Phone 8 was really hard.

Well it was build on top of normal Linux tool chain instead of Java, but it was really easy to use, responsive and had all the smart phone features of that day. Much better than Android 2.2 which was the hot thing then. Quite close to iPhone in terms of responsiveness and ease of use.

Nokia had long term plan which looked promising: They bought first Trolltech for QT and after that started doing Meego* (albeit too slowly) but the idea was to have one development platform for all their new and old phone platforms and QT fit the bill really nicely. But in the end the QT plan was really half-assed because getting it into Symbian took too long time and Meego was even slower project.

The first Meego phone N9 and it's unpublished sibling N950 (with the best qwerty hardware ever) were better phones than Android phones at that time, but when they released the N9 it was already known that Nokia will switch to Windows Phone and there was no point in buying N9 or developing apps for it.

They even had the QT + QT Quick setup working and showing lots of promise for writing javascript apps for different platforms. Sigh.

So if they've had the guts to execute the QT plan and Meego as a first priority projects + skipping Elop, the situation could be a lot different. Meego still feels more Linuxy than Android.

* Of course creating first Maemo on top of GTK and after that switching to QT sounded weird and with Meego there was other parties like Samsung and Intel meddling around so they lost lot of steam in that transition too.

Based on the screenshots, it's amazing how little the Mac System UX has changed between 1.0 -> 6 -> 7.1 (and to some extend even the newer versions, the latter UX changes were mostly theme-remake + little usage helpers).

Now it's good time to go and check out screenshots of Windows 1.0, 2.0, 3 and 3.1 to see how "ready" System 1.0 was compared to the Windows.

Other good thing to note is that the window manager of System was really good getting lots of windows to fit the puny 512x324 resolution. Something the Mac OS X is really bad at even with the 5k resolutions =(

Windows for Workgroups 3.11 had their Netbios network protocol support + drivers but you needed additional packages for TCP/IP. At that point most of the games used IPX protocol so you needed another DOS network stack like Novell's for gaming. If my memory serves my right, Duke Nukem 3D had Netbios support but all the other games (Doom, Descent, Warcraft 2 etc) used IPX.

Hopefully Facebook moves all sports-related status updates to that app, not interested in people's empty shouting where the ball, puck or fist went.

Ouch. Now the archive link says: 451 Unavailable For Legal Reasons

Wut? :O

Just finished my Raspberry Pi 2 -> Macintosh Plus DIY HW project: https://medium.com/@trm42/raspberry-pi-2-macintosh-plus-rasp...

^____^

Same here. The title could also be "This is how you detect Parkinson's decease OR KGB-agent" :)

If it comforts, I'm running my third pair of AKGs in 4 years. First 490, then 495 and now N60 NC. First got 490 warranty replaced with 495 and when they broke, bought N60 as I still prefer AKG sound quality over Boses and the NC got much better with this model.

In both 490 and 495 the problem wasn't the NC or audio or cabling but the cursed plastics. They just gave up on normal day-to-day use. I did use them really carefully and without any abuse :/

I'm using AKG's N60 NC's and they are much better regarding nearby high pitch speech than the older AKG models (495 and 490) but without music/white noise there may be some speech coming through.

Been using noise cancelling headphones for the last four years and they make working in a open office a lot better.

I just wish people wouldn't tap on the shoulder when I have headphones on. It's a sign of "I'm working on something, go away".

Btw. NC-headphones are not complete solution as they can pass nearby human speech through quite clearly.

That's why the music on top of NC is great but there's times when one doesn't want to listen music and then some white noise or waterfall sounds can be really, really useful.

Here has been discussion in another comments about overusing ARs for trying to achieve too complicated things that'll lead to DB performance problems. As stated elsewhere here, AR is good for CRUD operations but after that you should use Query Builder or plain SQL to achieve the more complicated cases.

If you're into videos, then Laracasts is awesome :)

Laravel at least has Query Builder: http://laravel.com/docs/5.1/queries

As an interesting side note: Laravel's AR ORM (=Eloquent) is built on top of the Query Builder so you can leverage Query Builder with AR if you know what you're doing. Can also lead to big problems if you don't realize the possibilities and the caveats.

At least he was aware of it but preferred to keep it in the browser side.

He had already started building something based on old PHP tutorials, what could be more useful if he has some small site to build:

A. Tell there's a nicer and easier way to do it in PHP with well thought framework B. Tell server JS is so awesome (and all the cool kids are using:), you just need to start completely from the beginning

Introducing things gradually can help a lot and lessen the frustration. Nowadays he's really into Vue and React but still likes to handle backends with Laravel :)

Also learning is one of those things that helps if the learning stuff isn't too far away from the skills you already have. Introducing too much at the same time makes learning more frustrating - especially if you want to get something finished instead of trying to multiple ways of doing the same thing.

Really good point! Most of us veterans assume that because we have learned things the hard way and from bottom up, everybody else should learn like that.

"Make them suffer like us and they will learn the holy truth" ;D