cmjqol

> My employer offers FaunaDB with a pay-per-request pricing model.

Tried FaunaDB few month ago the latency was beyond 200ms for a simple a read , and beyond 600ms for an insert.

Would not recommend it at this point.

>likely continuing for another ~15 years

It's not that simple, I doubt the boomers working at Google now are the one creating problems and preventing the company from moving forward.

When you see how much stuff they did for ahead of their time ( Big Table , Piper etc...) and now the same tech is being ported to the cloud.

My point here is to say that it's a mentality issue rather than an age issue. If the companies you are working did not invest to transform you and to make you adequate toward current society , you are going to slow down your company otherwise you'll be just fine.

>I’m also tired of all of this inexact labeling of “generations”

The age group are identified page 3.

I personally consider this labelling accurate , but as you mentioned it "boomers" are okay to label others but not to be labelled themselves.

Is there any plan to make this a partner product ?

It's limited to 10 Concurrent Build for obvious reason, making it impossible for startup who want to create CI services on top of this product due to limitation.

>reading reviews to figure out which listings are noise with fake reviews and which ones are for real

I thought I was the only guy looking for patterns in Reviews and grammatical style to eliminate fake reviews.

Amazon has an insane amount of traffic making it the ideal choice for Chinese electronics makers who have lived or studied to america. They understand western marketing and psychology and it's fairly easy for them to manufacture clones of something that works really well in those countries at lower cost. The products are often flooded with 5 stars rating , mostly incoherent.

I don't get what problem is this solving compared to :

AWS SES , SendGrid , JetMail etc... and the hundreds of others provider in this domain.

I always assumed Web Scraping wasn't something particularly challenging because of how many libraries existed for this purpose.

This article made me realize I assumed wrong.

> not actually make them on your OWN fork? Clickbait, gross.

Yup. Something like :

> You have bugs in your codebase of 1M+ line, you want to fix them ? Buy my proprietary software for 30$/Month per user , which was built 100% on open source tech obviously.

Getting traffic using linting issues from a large codebase to promote a proprietary software , Outrageous.

Serveverless is not lambda. If you think so , you are mistaken , it's like saying Cloud == EC2 .

> You can even throw an entire expressjs application into a lambda function

This is the first general misconception with serverless.

Serverless is not lambda . If you think serverless == lambda, it's like saying cloud == ec2 . You're missing the point of it.

Like others comments , Kudos to the authors.

I'm an SPA Lover ( Angular , Vue ) , but still most of the points raised here a coherent from a back end perspective.

That said , a lot of the arguments are basically summed up as :

"I don't like Front End Dev. because it's not as mature as Back End".

I will not lie on this point , JS is a fast evolving ecosystem that sometimes has issues to stabilize. Hence , there is a lot of marketing and self promotion mixed with frameworks sometimes ( Growth Hacking ) pushing for unnecessary tech that dies a few days after they have leaved the Github Trending page.

For beginners , when a framework reach a certain threshold ( Github Stars most of the time) they feel like they should hurry and use the framework to stay relevant while most of the time they don't need to and the tech is just fluff.

My point here is very simple, you are ROR or Django or ASP.NET dev and you love what you do ? As long as you find jobs keep doing this , don't bother with Full Stack Fluff.

Now that said , I can only encourage the author to do the Angular or Vue tutorial to discover something different. Rails is great ( it's empowering a lot of website Github , Airbnb etc... ) but SPA are different and when used properly it's hard to go back , the experience is delightful.

Most importantly we are getting closer to the serverless era where backend will be completly different from what it is compared as now, and SPA and SSR will likely be the standard in the future.

That was one the clearest guideline description I've ever readen in my life.

Obviously I'm not surprise this was written by an Engineer , it's very clear about what to do and what not.

Usually trainings and guidelines made from Designer are useless to developer , they talk about emotion , colors , moods etc... Which is key for marketing and UX but does not help a developer improve it's skill in UI .

>It uses similar paradigms to flutter

But it's common these days to confuse reader to make self promotion for their tech/services

A huge amount article's on Medium are similar to this one, they stay at the surface and don't really bring anything new to table.

> I've noticed this spirit of "learn everything" all over the React and JavaScript community, and I don't think it's a good thing.

I strongly disagree there. The only way for an engineer to make good decisions as to what tools / framework to pick from is to know and understand as much tech as possible.

It is fundamental for an engineer to do this job of tech-watching in order to not become religious and blinded by the tool it's currently using.

React is good , but it has it's own issues. If you don't do the effort of learning other tech ( Angular , Vue ) you have absolutely no idea what those issues are, and you will just learn how to work with them ( Atomized ecosystem , Heavy Boilerpate ) and basically accept them as a normal thing.

They aren't.

Learning other tech makes you more encline to try new things and to criticize the tool you are working with and how to improve them.

Flutter has it's own issues.

First , flutter uses an architecture similar to a game and uses it's own rendering pipeline and Layout system, meaning integrating with anything that exists is extremely challenging ( Chartings , Lottie etc... ) you'll be often waiting behind the Flutter team to implement the feature inside the engine.

On top of that the SDK supports for Darts right now are non-existent, maybe it'll change in the future , but Firebase + GCloud is pretty much all you'll get in terms of SDK as of now.