Must full page reloads be eliminated?
(That's the real defining characteristics of SPAs)
For 95% of businesses a PWA with occasional full page reloads will be fine.
But for 5% of (mostly large) businesses, a kick ass SPA will be necessary.
893 karma · joined September 24, 2016
Must full page reloads be eliminated?
(That's the real defining characteristics of SPAs)
For 95% of businesses a PWA with occasional full page reloads will be fine.
But for 5% of (mostly large) businesses, a kick ass SPA will be necessary.
Or maybe I'm just too old and need to get off my own lawn.
[1] https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
The OP is about MS. The title is about embracing. The parent comment mentioned extending it. I must be old and just couldn't pass up the historical hacker pop culture references. My apologies.
Don't sprain your wrists while shaking your pitch forks.
I always wonder about the interplay between a gravity well and dark energy specifically at the galactic boundary. If dark energy is in a sense "anti-gravity", would it not be stronger outside of a gravity well and weaker within? Would there be an interference pattern ( wave or valleys ) between dark-energy and gravity? Isn't a rotated wave just a spiral? Could the difference in rotational velocity at the edge be dark energy "pushing" the matter away to make up for gravity's weakness at the boundary?
[1] https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extingu...
In other news: McDonald's buys beef to make sure no one else can compete.
The West were the fore runners of industrialization and seen first hand the bad (old guard job loss, environmental impact, deadly accidents). Of course the price paid by the bad paved the way for the positive (economic supremacy).
The economic positive from technological progress is far more apparent from the outside (East) looking in. The (West) memory of the early years and negatives creeped into the culture. While the East mostly noticed the shiny shores of economic progress and relatively recently.
None of this is to say that the East is not having their own moment of the perils technological industrialization.
Perhaps the East's view of technology will become less idealised in the future.
JS and ajax we're supposed to save us.
Now instead of one slow page load. I get one slow page with a loading spinner, a login component with a loading spinner, a carousel with a loading spinner, latest news component with loading spinner. Content divs shifting and bouncing every which way as content loads.
It looks like some spilled a bucket of ajax-load.gif all over the damn page!
I'd prefer a blank page and the sudden appearance of the entire page.
The trick of the philosopher is an attempt at conveying meaning with a blunt instrument.
"To cross a river you need a boat. But when you reach the other side you don’t pick up the boat and carry it." ~ Alan Watts
NOW ZMA [1] has been my life saver for years. It never fails to make me enter "sleep mode". The same dose works now as has always worked. Do not take calcium supplements at the same time as ZMA.
When I read the stories of big city lifestyles I'm amazed so many people opt-in to it. Traffic, noise, concrete everywhere. Yuck - but to each their own.
I'll take my country life as a remote worker going on 8 years. Trees, forest, wildlife, fresh air, backyards. 5 minutes walk or 1 minute drive to a shop for groceries, hardware, lumber, restaurants, kid parks.
Everyone knows each other. Very tight knit community. Don't even get me started on cost of living differences. I'll never leave.
Remote work really levels the playing field and unlocks a lot of potential for rural and small towns. All happening at a time when the staple of resource extraction is declining but global connectivity is increasing. There may be a bright future for small towns yet.
Sure, if you're a Fortune 500 company, go ahead and hire a DBA, Cloud Architect, Backend Engineer, UI/UX Designer, Graphic Artist, Social Media Marketer, etc.
You'll have a few million $ in salary overhead. It may take longer to produce a final product.
BUT, it will probably be way better than a product that a full stack developer knocks out.
BUT, if you're a startup or SMB or lean department and have a 100k budget and a 6 week deadline a full stack developer is a huge asset to your company.
Obviously when you take the same project and give it to a highly specialized team of people with lots of time they produce superior results. Do we really need an article about it?
PS. Giving a 10 person team a 1,000 hour time budget would not be a huge deal. Try not laughing when a single Full Stack developer asks for 1,000 hours.
It's a pleasure to work with and a much needed tool in the frontend landscape. The more mindshare it gets the better for everyone.
I'll keep on rooting for it!
watch -n 10 composer dumpautoloaf --no-scripts &
Full disclosure: I did not verify this command would work wellEverything you already have will continue to work fine. All you have to do is include the autoloader somewhere in your code path.
An example assuming you already installed composer on the machine into your /bin or similar directory.
# add a new dependency:
composer require guzzlehttp/guzzle
# this dependency will now be in the vendor directory ls ./vendor
# update your apps entry point (ie: frontcontroller.php): // require composer's autoloader
require ('vendor/autoload.php');
# autoload will now find any dependencies you add via composer // create guzzle client
$client = new \GuzzleHttp\Client();
# another tip, if you already have a bunch of class files some where (ie: myapp/src/classes , myapp/src/models ) You can include class paths via composer.json "autoload": {
"classmap": ["classes/", "models/", "MyClass.php"]
}
You can now remove any hard-coded include or require statements.There is a lot more things you can do with it but this is the most basic example.
In short, give composer a try if you are already building apps in PHP.
`composer dump-autoload`
This will dump the autoloader and rebuild it. This is much much faster than an entire `composer install` run. For additional usage options try:
`composer help dump-autoload`
* Unrelated: HN can we please get better markdown?
I fear the usage of ORM are slowing the web and developers SQL knowledge is atrophying along with it. I miss the days of crushing a query from 0.4s to 0.0014s. I've see some pretty ludicrous SQL execution plans generated by ORMs.