This isn’t a very well documented change, so I thought a simple post that Google may find for another confused engineer might Help. Apparently byebug is no longer being maintained so you simply need to update to “pry-byebug”
gem 'pry-byebug', platform: [:ruby_20]
PHP has historically been marred by its own ease of use. That is to say the flexibility and lack of restrictions upon using PHP have led to some historically sloppy code and a general misunderstanding that PHP cannot handle prime time application development. That’s largely been the focus of industry experts the last several years, particularly emphasized by the efforts of Facebook and HHVM.
Recent research by Zend showed 25% of Enterprise “users” (that is, engineers, architects, and developers) were concerned or challenged with PHP’s performance. This has historically been the tipping point for major software applications to balk at PHP in favor of Java or Ruby.
Now that the community has voted on the next major release of PHP being PHP7 the core components of said release are extremely exciting.
The most significant of which is a substantial dedication to performance improvements:
Thanks largely to the integration of phpng PHP7 will have major performance improvements. Up to 95% improvements according to some benchmarks!
Davey Shafik did a fantastic overview of the major changes worth reading and I encourage anyone to do so. There is also a formal write-up by Zend covering the5 things you must know about PHP7.
Ultimately, this is an exciting time to be part of the PHP community as there very well be a significant paradigm shift regarding the perception of legitimacy of PHP as an enterprise stack solution for web applications.
For a variety of reasons, it appears the default frontend_config.sh bash script does not work 100% of the time in the litwicki-lemp vagrant box. So, I’ve added a simple manual step-by-step of the bash script that works.
If anyone can figure out what I’ve done wrong in the bash script I’d be forever grateful!