Unironically, this is one of the simpler setups for a multi-node WP setup I have seen, and I have set up prod WP many times. Anyone with associate level knowledge of AWS can do this. There is a reason there are entire companies (pantheon) dedicated to hosting Wordpress for you: doing it with speed, resiliency and redundancy is hard.
I recently purchased a new 13" pro, upgraded to the top processor. I installed Bootcamp and played hours of The Witcher 3 (on low settings, of course, but still). There were no overheating issues. Fan was going full blast the whole time, but it kept up just fine. Hopefully my little anecdote instills a little confidence. The new 13" is as close to a perfect machine to me as I have ever owned. It's compact, portable, light but a completely full powered functional 100% dev workhorse (with a great keyboard AND a physical escape key to boot). I couldn't be happier. Kudos to Apple for this one.
It also only makes sense if you know nothing about economics in general.
Lowering the price while maintaining existing margins just opens the door to more consumers available to purchase the product and overall increases shareholder value due to more sales.
It’s not mostly right however. It’s right for your run of the mill public or private universities, but as evidenced by this poster and countless others, there is a unique value proposition to going to a University: a learning environment unlike elsewhere in the world, with like minded people. I challenge you to try and apply this articles critiques to Harvard, Stanford, Duke, Chapel Hill, MIT, Georgia Tech, UT, etc. The environment, like minded individuals, resources at your disposal, and support structures in place can not be replicated in the virtual world with today or tomorrow’s technology. Maybe next 2-3 decades technology if advancements in 3D and holographic technology continue, but there’s signs that’s slowing down and it’s mostly polishing what’s available today rather than any true breakthroughs.
Throwing generalized insults is easy. Projection is a hell of a drug. I don't think it's constrained to cities. I hold to no ideology. I said the _worse_ of them are usually big blue cities.
It's always the big liberal cities, with majority democratic councils, and a legacy of democratic mayors and govenors with the worse police departments: Chicago, Atlanta, D.C., NYC, Baltimore, LA, etc. But somehow the "redneck trumpers in flyover states" get blamed for everything. It's really hilarious at this point. In my city of Charlotte, with the Keith Scott shooting, it was: 9 democratic council members to 1 republican, democratic mayor, democratic governor, black police chief, and a black police officer that did the shooting, but somehow it was institutional racism.
There is a policing problem in this country. Period. Color of your skin be damned. If people started from there, things might have been a little different at this point.
I am sure this will get flagged, but it really needs to be said at this point. Hopefully some of you see the truth. I sure see it, and I am a middle eastern immigrant.
Or quality, or getting what you actually paid for, or not supporting a wanna-be trillionare technocrat that would rather satisfy his fantasy to colonize mars than treat his warehouse workers humanely or help his neighbors here on earth in general.
Are you sure you have lived in the country? It doesn't make you a pariah, it makes you the target of lots of pamphlets to come to their Church. There are plenty of people who don't go to Church in the country.
And get this, there's bars too!!! With real alcohol!
Just a word of caution as someone who has went from D.C. to small town: It can also be not so good if you come with your previous political beliefs. Big coastal city politics are _very_ unpopular in smaller towns (not here to discuss the merits, just stating the reality). You won't make very many friends. Smaller towns don't have the same issues big cities do, so naturally it will require a different approach and way of thinking.
I am not sure why people think Amazon is such a dominate force on the commerce front, especially with respects to Walarmt. It isn't even close between the two. I am more worried about the cloud technology space being down to basically two choices now.
React is 8 years old. It's went through 3 major shifts: From react.CreateClass({}) style, to Class-based components, to now Hooks. In between, it's always embraced and tried to allow the community to adopt a more functional way of programming (Honestly, my personal take is embracing the classical-OO style is what made a lot of this "churny" feeling).
But honestly, that's not really that much in 8 years. I think what we are observing is the sheer popularity of React, and how much content is out there, that it feels like every week someone is picking up from some point in the timeline, and it all gets resurfaced and refreshed in people's minds. But those of us who have been here from the beginning would probably say all the improvements have been positive.
Really what has changed rapidly, especially in the past 2-3 years, is the underlying web technologies. I am finding that hard to keep up with.
> To make the same product in 1997 would be difficult if not impossible without very deep pockets.
And likely 10-100x the quality and reliability, and without needing to sell every bit of your personal information. Has anyone stopped to ask, maybe we just don't need all of this software?
Efficient for what? What are we solving for? Rushing out buggy, complex, unmaintainable, undocumented software? Sure. We are certainly more efficient at that. Hardly anyone takes the time to understand anything anymore, thoroughly, and detail it for others. It feels like all surface-level stuff.
This is the lazy answer I know, but I wanted to at least answer your genuine curiosity: There is ample research available online on the subject that explains it in depth and far better than I ever could. However, I will leave you with a few quotes that help at least paint the picture.
From the Golang FAQ:
> Generics are convenient but they come at a cost in complexity in the type system and run-time. We haven’t yet found a design that gives value proportionate to the complexity
Quote from Russ Cox:
> The generic dilemma is this: do you want slow programmers, slow compilers and bloated binaries, or slow execution times?
Finally, one of the reasons the C++ or Java approach has never been palatable to Go core devs is summarized from this Rob Pike quote from his famous "Less is Exponentially More" blog post:
> If C++ and Java are about type hierarchies and the taxonomy of types, Go is about composition
So therefore it really is also a matter of finding a generics approach that lives up to that spirit as well. Contracts I think are approaching that.
All that said, user defined generics (since technically speaking, Go has many generic capabilities today already) are coming to Go, they just aren't being rushed. I think we will be happy with the generics implementation in Go within the next year.
Generics, I would certainly be ecstatic for if it was done in a way that is novel and feels Go-like, so not Java or C# or C++'s implementations. This has certainly been the stance of the Go team since the beginning of time. It has never been "anti-generics" it's always been "we've studied all the generics implementations out there, and didn't feel like any one of them were good enough, so rather than shoehorn them in, we are being patient." This approach needs to be celebrated more.
Exceptions, OTOH, I hope never see the light of day in Go. Curse them.