trm42

AR works nicely for simple basic queries but everything more advanced should be done with custom queries. That helps a lot :)

Well anything is better than the old and original Mysql extension for PHP. If you Google "PHP MySQL tutorial", there's lots of tutorials teaching still about mysql_connect and mysql_query.

AR is controversial but it is approachable.

In addition, I figure, those old PHP tutorials (code like it's the 2003!) are giving bad example and beginners can't understand the difference or realize that mysql_query + bunch of procedural code per file * 10 can be bad thing.

I should've been a bit more clearer. Laravel taught him bunch of generic best practices (like deployment procedures, GIT, OOP, MVC, etc) and using Laravel Query Builder and/or Eloquent makes the DB code more sane compared to mysql_query.

Laravel isn't the only framework which could've done this but like AR, it's quite beginner friendly :)

I could've done that but that wouldn't have taught the same things. PDO is awesome but requires deeper level of understanding (for a beginner), which may increase the frustration and may end up returning back to the mysql_query and co.

It's easier point to framework that's already using PDO and and making sane defaults and solving bootstrapping problems. Once you've learned bunch of new concepts like ORM in one framework, it's easy to understand other ORs and be able to compare it to DMs.

My own experience with Laravel has been really positive. Actually I was thinking about creating something similar until I learned about Laravel, so it solved lots of existing annoyances regarding PHP coding for me.

Everybody needs to start somewhere and I believe that by nudging towards Laravel, my young friend'll learn more in the long run and in the meantime can concentrate on making services instead of writing home grown PDO helpers and custom routing libraries. They are problems that have been solved already multiple times.

Also, Symfony and Laravel communities are encouraging and teaching about the better ways of doing things so that'll help him in the long run.

In many small project it's more fun and more easier to use $favorite_framework instead of searching for reinvented wheel. There are cases when it's better to do more custom solutions but for many cases frameworks are just awesome

PHP 7 makes life a lot better for PHP devs in many ways but one awesome thing is it obsoletes bunch of out-of-date tutorials by finally removing the old Mysql extension \o/

http://php.net/manual/en/migration70.removed-exts-sapis.php

I actually met a young aspiring web developer who still learned DB-access with mysql_* functions. I urged him to switch to a sane framework like Laravel. Oh boy he was happy in a month and learned bunch of best practices quickly.

At least the Tolkien Estate has voiced disapproval for all of the Jackson stuff.

Personally I did watch the first part of the Jackson's Lotr and oh the horror. I wish I could erase my memories :/

For me, it was W2K. It has the stability of NT series better usability, drivers and it was quite fast. Windows XP made simple things a lot harder and slower :)

Maybe I'm a bit tired but read first "Patent US5443036 - Method of exorcising a cat". Well, either way it's funny ;)

It wouldn't provide extra information but it would be cleaner way to follow the network compared to reading dhcpd leases. You could have RPI (or other comp) working as the wifi AP or you have RPI between the WAN router and the actual Switch/Access point. This way RPIs slow IO wouldn't slow down your intranet.

Sounds plausible. Thanks for the info :)

Hehee, my dad ended up buying some demo/test machine from AST in 92 or so. The comp had quite high end specs for it's time. It actually ran really fine for long time because of switching to Linux. Stopped using it in 1998. Probably could still remember all the IO, DMA, IRQ settings for hardware ^___^

DOSemu was really joy to use for gaming even on Linux+486 + 10 Megs of ram. Oh those were the days :>

I would expect that RPI could route normal home lan traffic well enough unless there's some big IO limitations regarding ethernet+usb ethernet. Linux has been used for routing with a lot lower spec HW than RPI or RPI2.

Somehow I expected this talk about real network monitoring like using Ntop, Nagios, arpwatch etc. Just creating another dhcpd for the lan/wifi feels cumbersome just to get dhcp leases.

So how about using RPI as a network bridge between the router and the client hosts and then using Ntop, arpwatch etc. Then you can actually monitor the traffic in detail.

I have had two pouring incidents in the last ~20 years or so. They both happened within a week and in both times it was tea. Still laughing, especially for the second time ;D

At the time I was a student so probably had really, really bad sleep-deprivation (=really jumpy or something) from too much of anime and hobby coding. Oh those were the times :D